Changelog

DataChannels reliability and ordering (ordered, maxRetransmits, maxPacketLifeTime)

Publishers can choose ordering and retry settings for each named DataChannel. Every subscriber mirrors the published channel's policy in its API request and browser configuration. Use separate named channels for different policies.

• ordered (default true) controls in-order delivery. When false, a delayed message does not block later messages.
• Set ordered: false and omit both retry fields for reliable, unordered delivery.
• Set at most one of maxRetransmits and maxPacketLifeTime. Omit both for reliable delivery; maxRetransmits: 0 explicitly requests no retransmissions.
• maxPacketLifeTime limits transport attempts, not end-to-end message age.
• Set the same delivery policy on local and remote /datachannels/new calls and each createDataChannel() call. Channel IDs remain endpoint-specific; waitForAck and canReply remain subscription-specific.
• Docs: DataChannels, Connection API

DataChannels return-to-publisher (canReply)

DataChannels now support opt-in reverse traffic from one subscriber back to the publisher on the same channel. When a subscriber pulls a remote DataChannel with canReply: true (or is granted it later via datachannels/update), the SFU admits that subscriber's messages to the publisher only.

• Opt-in per subscriber; defaults to false, so existing publisher-to-subscriber fan-out is unchanged.
• Reverse traffic is not fanned out to other subscribers.
• Exclusive: at most one subscriber holds canReply per publisher DataChannel; a new grant replaces the previous holder.
• Grant or revoke without re-pulling via PUT .../datachannels/update.
• Docs: DataChannels, Limits, timeouts and quotas

DataChannels subscriber acknowledgment gate (waitForAck)

DataChannels now support an opt-in subscriber acknowledgment gate. When a subscriber pulls a remote DataChannel with waitForAck: true, the SFU holds delivery to that subscriber until it sends its first message (the acknowledgment). This avoids losing the first messages before the subscriber is ready to handle them.

• Opt-in per subscriber; defaults to false, so existing behavior is unchanged.
• The acknowledgment is consumed by the SFU and is not forwarded, so the channel stays unidirectional.
• Send the acknowledgment within 30 seconds of creating the remote DataChannel.
• Docs: DataChannels, Limits, timeouts and quotas

WebSocket adapter video (JPEG) support

Updated Media Transport Adapters (WebSocket adapter) to support video egress as JPEG frames in addition to audio.

• Stream audio and video between WebRTC tracks and WebSocket endpoints
• Video egress-only as JPEG at approximately 1 FPS for snapshots, thumbnails, and computer vision pipelines
• Clarified media formats for PCM audio and JPEG video over Protocol Buffers
• Updated docs: Adapters, WebSocket adapter

Media Transport Adapters (WebSocket) open beta

Open beta for Media Transport Adapters (WebSocket adapter) to bridge audio between WebRTC and WebSocket.

• Ingest (WebSocket → WebRTC) and Stream (WebRTC → WebSocket)
• Opus for WebRTC tracks; PCM over WebSocket via Protocol Buffers

Docs: Adapters, WebSocket adapter

TURN service is generally available (GA)

Cloudflare Realtime TURN service is generally available and helps address common challenges with real-time communication. For more information, refer to the blog post or TURN documentation.

Orange Meets availability

Orange Meets, Cloudflare's internal video conferencing app, is open source and available for use from Github.

Cloudflare Realtime open beta

Cloudflare Realtime is in open beta and available from the Cloudflare Dashboard.

Cloudflare Realtime closed beta

Cloudflare Realtime is available as a closed beta for users who request an invitation. Refer to the blog post for more information.