How VivoStream works
Every live stream on VivoStream follows the same path: you send it in, the platform delivers it to your viewers' players, and protects it on the way. This page walks that path once, so the rest of the docs fall into place.
The path of a stream
| Stage | What happens |
|---|---|
| 1. Ingest | Your encoder sends the live stream to VivoStream. |
| 2. Deliver | VivoStream carries the stream to your viewers, routed to the closest available server. |
| 3. Play | The VivoStream player plays it in the browser, with ultra-low latency. |
| 4. Protect | Playback tokens decide who may watch. |
1. Ingest
Everything starts with a stream. Each stream has a stream name like XXXXX-YYYYY and a unique ID (see Key concepts). You send video to the stream with one of these protocols:
| Protocol | Typical source |
|---|---|
| RTMP / RTMPS | OBS, Streamlabs, vMix, Wirecast, ffmpeg, hardware encoders |
| SRT | Encoders on unstable or long-distance networks |
Copy the exact ingest URL and stream name for your stream from the Dashboard or the API; don't build it by hand.
2. Deliver and 3. Play
Viewers watch your stream in the VivoStream player, a browser player with no plugins. It plays over MOQ (Media over QUIC) where the browser and network support it, and falls back to a WebSocket-based transport where they don't. You embed it on your page with an iframe.
4. Protect
- Playback tokens let only viewers with a valid token watch.
- Encrypted ingest (RTMPS or SRT) protects the way in.
Where the tools fit
Both work on the same account and the same streams.
| Tool | Best for |
|---|---|
| VivoStream Dashboard | Creating and managing streams, copying ingest settings and player code, API keys, users |
| REST API | Automation: creating streams and tokens from your own backend |
New to VivoStream? Start in the Dashboard.