Live Streaming - BitByte3 Support

Live Overview

Run live events on Cloudflare Live. Create multiple live channels, feature one channel across discovery surfaces, and keep upcoming, live, replay pending, and replay available states on the same public event URL.

Cloudflare Live + Ably

One live service path for ingest, playback, chat, and replay.

Cloudflare Live handles ingest, playback, and replay packaging

BitByte3 keeps entitlement and signing logic server-side

Ably powers realtime chat without trusting clients to publish directly

Web, mobile, TV, and admin stay on one live operating model

Ingest Modes

Choose an ingest mode on each live channel that fits the broadcaster setup: RTMPS, SRT, or WebRTC through Cloudflare Live.

Mode	Best for	Operator note
RTMPS	OBS, vMix, Wirecast, hardware encoders, and studio workflows.	Use as the default when a traditional encoder controls the feed.
SRT	Contribution links and unstable network conditions.	Choose SRT when you need a more resilient ingest path than RTMPS.
WebRTC	Low-latency browser or app broadcasting.	Grant camera, microphone, or screen-share permission to broadcasters when required.

Delivery & Playback

Serve active live playback from Cloudflare live playback metadata instead of the standard VOD stack. Apply access checks before returning playback state, then route viewers into web, mobile, TV, or admin preview playback with the same entitlement model.

Keep one live URL across event states

Keep the public live page stable as the event changes. Viewers move from upcoming messaging to live playback, then into replay on the same route when the recording is ready.

Replay Lifecycle

Treat replay as part of the same live-event workflow. Keep the event page active, wait for recording or processing to finish, then publish replay once a playable asset is ready.

1Schedule and promote the eventCreate the live channel → choose ingest mode → set timezone-aware dates → feature the event where needed.
2Go liveStart ingest on Cloudflare Live; BitByte3 applies event access rules to viewers during the broadcast.
3Move into replay pendingWhen replay is enabled, keep the event visible while the replay asset is processed or assigned.
4Publish replayOnce the replay asset is ready, confirm the same public live URL renders the replay experience.

Live Chat

Enable live chat with Ably for realtime fan-out while the backend controls message acceptance, moderation, and event access alignment.

Viewer chat

Let authenticated viewers on web and mobile receive history, subscribe with a short-lived token, and send messages when the event allows it.

Admin monitor

Open the admin preview player to follow a read-only live chat stream without publishing into the event chat.

Keep chat moderation server-side

Do not publish directly into Ably from clients in the first release. Route messages through the backend to validate the user, event access, rate limits, banned words, mutes, and duplication rules before fan-out.

Live Security

Run secure live operations with server-side access checks, signed playback, replay state, and chat token issuance so subscriptions, PPV events, and public events each follow the right path.

Control	Why it matters
Entitlement checks	Evaluate Free, SVOD, and PPV events before playback starts.
Signed playback	Issue signed or provider-protected playback URLs to reduce raw playback leakage for paid events.
Replay control	Publish replay only after the event asset is verified and linked to the correct title or live channel.
Token-based chat auth	Issue Ably tokens per event and tie them to an authenticated viewer or operator context.

Talk to BitByte3 about implementation

Run live events and replays