Real-time infrastructure for multiplayer apps

openRTCto connect

The simple real-time stack. Managed signaling, peer-to-peer data paths, and one avenue-first SDK — without the backend headache.

P2Pdirect when possibleQUIC
1 SDKbrowser to nativeOPENRTC
3 routesQUIC · WebRTC · MoQTRANSPORT
0 serversfor your app data pathEDGE
P2Pdirect when possibleQUIC
1 SDKbrowser to nativeOPENRTC
3 routesQUIC · WebRTC · MoQTRANSPORT
0 serversfor your app data pathEDGE

Try OpenRTC in your browser

Enable JavaScript for interactive demos. Open a second tab or invite a peer to try collaboration.

Capabilities

Everything you need.
Nothing you don't.

01

QUIC-native transport

QUIC direct paths provide encrypted peer connections with automatic NAT traversal and relay fallback when a direct path is unavailable.

02

SDK in minutes

Install openrtc and use one avenue-first client API across browser, Tauri, and standalone Rust applications.

03

Real-time collaboration

Rooms, presence, and protected channels for cursors, documents, files, and games — without standing up your own sync server.

04

Trust by default

Admission grants and protected channels scope which peers and app protocols are trusted. Transport encryption stays on the wire.

Two shapes for live video.

Build a room when people talk together. Build a broadcast when an audience watches one source.

01 / Everyone can speak

Video rooms

Bring a small group into one room. Each participant can publish a camera and microphone to the other admitted peers.

Real room demoTry the video room
02 / One source, many viewers

Live broadcasts

Send one live source to a relay for the audience to watch. The app-owned issuer and MoQ/SFU path has a small local proof; managed hosting remains a developer preview.

Developer previewRead the broadcast guide
Process

Three steps.
Live peers.

client.ts
1import { OpenRTC } from "openrtc";
2 
3const apiKey = import.meta.env.VITE_OPENRTC_API_KEY;
4const rtc = OpenRTC({ apiKey });
Ready
Transports

One SDK.
Every route.

OpenRTC unifies QUIC, WebRTC, and MoQ behind one lifecycle-aware client API. Pick the right path for each workload without switching providers.

Route matrixNegotiating

Live coordination

Start small. Grow when you need to.

Real simultaneous connections and coordination message units, shared across your apps. No per-minute connection charge. Your application supplies user identity.

Hobby

Personal, noncommercial projects

$5 / month

  • 100 concurrent connections
  • 100,000 coordination message units / month
  • 1 app

Hard limits. No overages or additional usage charges.

Builder

Commercial projects

$29 / month

  • 1,000 concurrent connections
  • 1,000,000 coordination message units / month
  • 3 apps

Optional overages: $0.05 per extra peak connection per cycle + $50 per million message units.

Pro

Commercial projects

$79 / month

  • 4,000 concurrent connections
  • 5,000,000 coordination message units / month
  • 10 apps

Optional overages: $0.04 per extra peak connection per cycle + $40 per million message units.

Scale

Commercial projects

$299 / month

  • 20,000 concurrent connections
  • 20,000,000 coordination message units / month
  • 10 apps

Optional overages: $0.03 per extra peak connection per cycle + $30 per million message units.

Rooms, spaces and user-scoped peers share one client and coordination allowance. A client counts once across its peer scopes. Commercial overages are off by default. Set one additional-spending cap to enable them. The coordination-attempt offer counts eligible access attempts, accepted joins and renewals, publications and recipient copies in the shared message allowance; direct peer traffic is outside it. Existing terms keep their rules. Technical limits apply. Prices exclude taxes. Billing shows current availability.

Ready to build
something live?

Explore live coordination from $5 per month for personal projects. Choose a commercial plan when your app is ready for more.

Monthly plans · Optional capped overages