The whole signal path,
in one room.
From a tap in Douala to an HLS segment in the living room. How the platform is wired, how every repository runs, and how a change reaches production without breaking the stream.
- client apps
- 5
- runtime services
- 3
- storage buckets
- 3
- databases
- 2
One request, five stops. The full map lets you follow every other flow.
Three ways into the system.
Written for the people who run it. New engineers, reviewers, and anyone who needs to answer “what actually happens when…”.
Set it up
Every repository, the right Node version, the test Firebase project, and the environment file that makes it run — without ever copying a production secret.
Prerequisites and local setup →02See the shape
Three clients, one gateway, two APIs, an ephemeral encoder and a streaming server. Read the system in plain language, then switch to the service-by-service view.
Open the architecture →03Ship a change
Test is the integration branch; main is production. Deploy the worker image before the API, keep one API replica, and know exactly what to roll back.
Build and deploy →For the people who watch. And the people who keep it on air.
Every diagram has two modes. Explained uses the language of the product: what you tap, what happens next, why a title is not there yet. Technical names the repositories, ports, protocols and key files. Both are zoomable, pannable, full-screen and exportable.
The same is true of the Mermaid version: an auto-laid-out second opinion that opens the same detail cards when you click a block.
Start with the product view.
Click any block for a plain-language card. Scroll with Ctrl / ⌘, or use the controls to zoom, fit, go full screen and export.
How GreyScreen works
A guided view of what happens between the moment you open GreyScreen and the moment the video plays. Click any block to read what it does.