STREAM

PROGRAM 01 Browser-first multistreaming

READY FOR INPUT

Stream once from OBS.
Reach your watch page and relays.

Send one broadcast from OBS to Stream. Share your own browser watch page, then optionally relay that same live signal to YouTube, Twitch, X, Kick, or Telegram.

Start with DiscordStart with GitHubWatch Sean live

Discord or GitHub creates the same kind of account. Connect both later for a backup sign-in route.

  • CHANNELS01
  • LIVE FEEDS01
  • BROWSER VIEWERS25
  • RELAYS AT ONCE03

ROUTING 02 From source to screen

From OBS to a public watch page.
Relay out on demand.

Your public page is the main program output. Provider relays are optional auxiliary outputs, not a requirement for going live.

  1. 01

    Create one channel

    Choose its name and public /watch/your-channel address. Stream issues one ingest token.

    PATCH
  2. 02

    Connect OBS

    Select WHIP in OBS, paste the server URL and token, then start one live broadcast.

    INPUT
  3. 03

    Share or relay

    Send viewers to your watch page. Configure and enable all five supported providers at the same time.

    OUTPUT

METERING 03 Prepaid only

Buy hours.
Run the signal.

No monthly fee. No commitment. Buy any whole number from 1 to 1,000 hours in one checkout. Credits never expire.

CH ARelay

Time sent to enabled streaming destinations.

CAD $1.50per enabled destination-hour
CH BViewers

Combined time watched by browsers on your watch page.

CAD $0.75per aggregate browser viewer-hour

Relay accounting example

Two destinations for one wall hour consume two relay hours.

Relay usage follows the enabled destinations in the confirmed relay configuration. A degraded or retrying destination continues counting until you stop the relay or change its configuration.

FORMAT 04 Current production scope

A focused live service.

Clear limits keep operation predictable while Stream remains in early access.

01

One channel, one broadcast

One public watch page and one incoming OBS broadcast at a time.

PROGRAM
25

25 concurrent browser viewers

Viewer usage is the sum of each browser's connected viewing time.

AUDIENCE
05

Five enabled destinations

Send to YouTube, Twitch, X, Kick, and Telegram at once. Paused destinations can stay configured.

AUX
00

No recording

Stream transports live media. It does not create or store a replay.

ARCHIVE

NETWORK 05 Connection privacy

Your source address stays off the destination feed.

Viewers and configured streaming destinations do not receive the network address of the computer running OBS from Stream.

Cloudflare handles connections needed to ingest and deliver the broadcast, so Cloudflare receives the technical connection details those sessions require. This separation protects the source address from viewers and destinations, but it does not make a broadcast anonymous.

TAKE 06 Open the control room

Put your first signal on air.

Sign in, create a channel, buy only the hours you need, and connect OBS.

Continue with DiscordContinue with GitHubWatch Sean on live.codebam.ca