Bitrate documentation
How Bitrate is built, run and released.
Architecture decisions, application guides and operating runbooks for the people who contribute to Bitrate and keep it running.
Getting started
3 pagesFrom a clean machine to a running monorepo.
- IntroductionWhat lives where
- ArchitectureHow the apps fit together
- Setuppnpm, Docker, Task
Architecture
69Every decision with its context and consequences.
0069GSAP is the animation library for every web surface0068The operator API as its own process, contract and host0067Playback sessions — a token per play, a ~10-second cap and real-time pacing0066Bitrate is music-only; spoken word belongs to separate products0065One stored audio format — CMAF AAC, 10-second fragments, HTTP Range only
Applications
13API, web player, artists portal, admin, mobile and desktop.
OpenPackages
5Contracts, converter, ui-react and the CLI tools.
OpenBrand
11Principles, tokens, motion and voice.
OpenInfrastructure
7Deploys, backups and observability.
OpenGuides
5Contributing, environment, seeding and testing.
OpenPlans
2Implementation plans for work in progress.
OpenSpecs
9Feature specifications written before they become decisions.
OpenStrategy
10Who Bitrate serves first and how the roadmap follows from it.
Open