Skip to main content

Real-Time Voice Bridge Protocol

One voice protocol. Any application.

RTVBP connects the peer that owns a live call to the application that listens, speaks, and controls it—using typed operations and events alongside real-time audio.

Try it outRead the docs
Voice peerApplication peer

Why RTVBP

The payload is the invariant.​

Build real-time voice systems without coupling business logic to a single media path or hand-maintained protocol client.

Typed by design

Operations, events, roles, envelopes, SDK surfaces, and reference docs all derive from one executable specification.

Transport independent

Keep the same call-control payloads while choosing WebSocket audio, WebRTC media, or a future binding.

Proven on the wire

Frozen fixtures and cross-SDK conformance tests protect deployed babelforce.v1 behavior byte for byte.

Choose your path

Start at your integration boundary.​

TypeScript SDK

Connect from Node or a real browser.

Generated role contracts, AudioWorklet, WebSocket, and native WebRTC.

Open quickstart Go SDK

Build a voice or application peer in Go.

Generated role contracts, typed peers, WebSocket, and WebRTC.

Open quickstart Rust SDK

Build the same protocol surface in Rust.

Tokio runtime, generated catalog APIs, and transport parity.

Open quickstart Wire protocol

Implement RTVBP directly from the contract.

Profiles, envelopes, media framing, and generated reference.

Open quickstart

Open protocol, active steward

Built from production voice infrastructure.​

RTVBP is stewarded by babelforce. The deployed protocol remains frozen where compatibility matters, while new SDKs, transports, and conformance proofs evolve in the open.

Explore the project on GitHub
babelforcebabelforceVoice, built for change.