Jerry Franklin
A music production educator teaching an audience of two million how to make records. What follows is the infrastructure behind the teaching, run as compositions rather than as a stack of subscriptions.
This is a case study, not a product. What is described below is one person's deployment — it is not a tier, it is not sold as a unit, and no plan is required to run any of it. Every composition named here is on the menu.
Audio first, then everything on top of it.
The audio foundation stands up once. Production, streaming and collaboration are added above it as the work needs them, which is what makes this a stack rather than three separate installations.
The catalog is unreachable.
These compositions are listed from the live catalog and the service is not answering right now. Nothing is wrong with the deployment this page describes.
Three ways in, depending on the work.
- Producing
- The Music Production Studio composition is the complete audio workstation, and it stands up first.
- Streaming
- The Live Streaming Setup carries capture, encoding and the monitoring to know it stayed up.
- Collaborating
- The Artist Collaboration Hub is the one to start from when more than one person touches the project.
All three are on the menu, and the Builder is where a composition gets changed before it is deployed.
Why this shape.
- Built for the workflow
- Assembled around how a record actually gets made, from first take to distribution, rather than around a product catalogue.
- Teachable
- Every composition is a file someone can read. That is what makes it possible to teach rather than only to demonstrate.
- Shared
- Collaboration was designed in rather than bolted on, because more than one person touches almost every project.