Realtime

Live channels and rooms, held open at the edge.

WebSocket channels backed by a Cloudflare Durable Object, plus managed RealtimeKit tokens for video and voice. Presence, live updates, multiplayer, and chat from one connection — the broadcast loop and the socket set are someone else's problem.

fan-out

Publish once, everyone hears it

A single Durable Object owns each channel — it holds the live socket set and runs the broadcast loop. Send one message and it reaches every subscriber in order, with no queue to wire up and no fan-out logic of your own.

  • Edge-resident sockets, low round-trip latency
  • Ordered delivery to every listener on a channel

presence & rooms

Know who is in the room

The same object that broadcasts also tracks who is connected, emitting join and leave events for free. When a session needs faces and voices, mint a scoped RealtimeKit token and drop into a managed video or voice room beside your data channels.

  • Live roster with join / leave deltas
  • Server-minted RealtimeKit tokens for media

pricing

Fluid pricing

Realtime is bucketed; once the monthly grant is spent, usage auto-buys from fluid credit so a live session never drops. Two numbers to know on free:

published messages

500K / month on free

concurrent sockets

50 on free

Open a WebSocket, name a channel, and start receiving. Every channel is backed by a single Cloudflare Durable Object that owns the socket set and the broadcast loop, so a message published once lands on every subscriber in order. Channels are created on first use and need no provisioning step of their own.

Related

WebSocket, Durable Object, Channels, Publish, Subscribe

For more information, ask your agent.