One channel
Each account can create one named channel and one public watch URL.
01 Focused live infrastructure
One feed.
A cleaner path live.
Send OBS to Cloudflare Realtime over WHIP. Publish a focused Codebam watch page, then relay the same channel to YouTube, Twitch, and X.
Discord or GitHub identifies your dashboard account. Link both providers from the dashboard for backup access.
02 Signal path
Small surface.
Explicit route.
Codebam Edge coordinates the channel and watch experience. Cloudflare Realtime carries the WebRTC media connection.
-
01
CONTROL
Issue ingest credentials
Create one channel in the dashboard. Copy its WHIP URL and one-time ingest token into OBS.
-
02
MEDIA
Publish through Realtime
OBS establishes a WHIP publishing session with Cloudflare Realtime. Codebam reports whether the channel is live.
-
03
OUTPUT
Choose the outputs
Share the Codebam watch URL. Start every enabled YouTube, Twitch, and X relay together from the dashboard.
03 Network boundary
Stated plainly.
Your source network address is not shared with viewers or configured streaming providers.
Cloudflare necessarily handles publisher and viewer connections to provide Realtime, so Cloudflare receives the connection information those sessions require. This design separates your source connection from viewers and relay providers; it is not a claim of network anonymity.
04 Plan scope
Narrow on purpose.
Current product surface is intentionally small. Expect rough edges and changes while the workflow is proven.
Three relay paths
Save one destination each for YouTube, Twitch, and X. Every enabled path runs simultaneously with independent health.
Exact-period quotas
CA$19 includes 50 relay-hours and 100 aggregate viewer-hours per Stripe billing period, with hard cutoffs.
05 Start a channel
OBS ready?
Sign in, create the channel, and take the issued credentials to your encoder.