Bytestream has three ways a creator’s picture reaches viewers. Each one runs on different services, and they cost very different amounts as the audience grows.
Prices on this page were read from each provider’s pricing page or API on 2026-09-23. Per-hour data figures are estimates at 720p (roughly 1 GB per viewer per hour). Check the providers before making a decision on them.

The three paths

1

Browser live

The host asks /api/studio?action=room-token for a pass to their own room, live-<clerk id>, and publishes camera and mic to LiveKit. /api/creators asks LiveKit which rooms are live and puts each one on the host’s own channel, or on the N00bstream when they have none yet. Viewers get a hidden, watch-only pass from /api/studio?action=viewer-token. See api/_lib/rooms.ts and src/player/RoomPlayer.web.tsx.
2

Stream-key live

OBS pushes RTMP or SRT to MediaMTX, whose auth and ready hooks (api/live.ts) check the key and flip live_inputs.connected. The box serves the HLS itself, so viewer bandwidth comes out of the box’s included traffic. Nothing is transcoded.
3

Upload

The browser puts the file straight into R2. Mux encodes it once, the encoded MP4 is copied back to R2, and the Mux asset is deleted. Viewers play the file from R2, which charges nothing for downloads.

What each service costs

Mux Live costs $0.03125 per minute of input. Bytestream does not use it: live goes through MediaMTX or LiveKit. Keep it that way unless the per-minute cost is acceptable.

What it costs to stream

Going live has its own cost, separate from the people watching. It depends on how the creator streams.
Sources, read 2026-09-23: Hetzner, “We only bill for outgoing traffic. Incoming and internal traffic is free.” LiveKit’s pricing page lists participant-minutes, downstream data transfer, track egress at $0.001 a minute (60 minutes included on Build) and ingress at $0.02 a minute for video. Two things it does not state: whether the host counts toward participant-minutes (assumed yes here) and whether the host’s upload is billed (it lists downstream only, so assumed no). Recording browser lives is not built yet; the figure is what the planned per-track recording would cost.
In short: streaming itself is nearly free either way. What costs money is viewers on LiveKit Cloud (about $0.16 each per hour) and, if it is ever built, OBS into a room on Cloud ($1.20 an hour). Self-hosting LiveKit removes both per-minute charges.

What an hour costs

Comes out of the box’s 22 TB a month, about 20,000 viewer-hours. Past that, about €0.001 per viewer-hour. The practical limit is the box’s network port, not money: a small VPS serves a few hundred concurrent viewers (estimate, not measured).
Every person in the room counts, the host included. On Build, 5,000 minutes is about 80 solo hours, or about 8 hours with 10 viewers. Build’s behaviour at the limit without a card on file is not confirmed; check the Usage page in the LiveKit dashboard.
About $0.015 per GB per month of storage. Watching them costs nothing.

When to switch: the plan

Browser lives start on LiveKit Cloud and move to a room server of our own once the audience makes that cheaper. Measured in viewer-hours a month.
A viewer-hour is one person watching a live stream for one hour. It is not the streamer’s hours and not people watching uploaded videos. Each viewer is sent their own copy of the live picture, and that data is what the room server bills for, so cost follows viewers × hours. One live watched by 36 people for an hour is 36 viewer-hours; 20 such lives in a month is 720.
  • The streamer’s own time is a separate, small cost on LiveKit Cloud: about $0.03 per hour live, whatever the audience. It is left out below.
  • Uploaded videos and replays are files served from R2, where downloads are free. Watching them costs next to nothing and is not in this chart.
The lines cross at about 730 viewer-hours a month: below it LiveKit Cloud is cheaper, above it the self-hosted box is, and the gap keeps widening. At 1,500 viewer-hours Cloud is about $218 a month against $116; at 10,000 it is about $1,565.
How the lines are drawn: 720p at 1.1 GB per viewer-hour. LiveKit Cloud Build runs out of its 50 GB first, at about 45 viewer-hours; Ship’s $50 covers 250 GB (about 227 viewer-hours), then $0.12/GB, plus $0.0005/min past its 150,000 minutes. Self-hosted is one Hetzner CCX23 (4 dedicated vCPU) at €101.49, $116.34 at the ECB rate of 1.1463 on 2026-09-22, with 22 TB of traffic included. Only people watching browser lives are counted; the host’s own minutes on Cloud are left out.
The crossover is about money only. A single box has a ceiling on how many people can watch at the same time (LiveKit’s own benchmark put a 16-core server at about 3,000; a 4-core box is well below that, not yet measured), sits in one region, and is ours to run. Load-test it with simulated viewers before switching, and add boxes when the peak audience outgrows one.

Per viewer-hour, above the free tiers

For calculations: what one more viewer watching for one hour costs once the free allowances are used up. Data per hour depends on bitrate: The host counts too on LiveKit Cloud: add 60 participant-minutes ($0.03) per hour of each live, whatever the audience.
Worked example, 720p: 100 viewers for a 1-hour browser live on LiveKit Cloud Ship costs about 100 × $0.16 + $0.03 = $16. The same hour through the Hetzner box, as a stream-key live, costs about 100 × €0.0013 = €0.13 once its included traffic is used, and nothing before that.

As the audience grows

While costs matter, send creators to the stream-key path: it runs on a box you already pay for and its viewers are nearly free. The browser path is the one that bills per minute until the room server is self-hosted.

Where the settings live