What StreamHub is and how to get the most from it: concepts, step-by-step guides and tours of every feature.
A self-hosted media server over LiveKit: multi-tenant apps, every ingest path, WebRTC + HLS playback, recording to your own S3, and a REST API — all behind one domain you control.
Per-minute SaaS pricing, data residency and lock-in are the three reasons teams move streaming in-house. Here is what you gain — and what you take on — by running it yourself.
A single reverse proxy, one core container that serves the API, dashboard, HLS and SDK, and a hidden SFU underneath. A tour of the request routing and the pieces that make it feel like one product.
One server, many isolated apps. How StreamHub uses apps, tenants, per-app SQLite and room prefixes to keep customers and workloads cleanly separated.
Sub-second WebRTC or buffered HLS? The trade-off between latency, scale and reach — and how StreamHub gives you both from the same live stream.
Every app records to its own S3 bucket with its own credentials. How the recording-to-VOD pipeline works and why the storage boundary is per app.