Pricing
Live coordination from $5 per month. Real simultaneous connections, coordination message units and optional capped overages.
Use rooms, spaces, user-scoped peers and live subscriptions with one shared allowance of simultaneous hosted clients and coordination messages. A hosted client is an active SDK root or explicit live session, not each physical peer connection. Joining several rooms, spaces or user scopes on one root does not multiply its connection count. Your app controls its room, space and device policies; protocol and request safeguards still apply.
Monthly plans
| Plan | Monthly price | Concurrent connections | Distinct MAU (hard stop) | Coordination message units | Apps |
|---|---|---|---|---|---|
| Hobby (noncommercial) | $5 | 100 | 100 | 100,000 | 1 |
| Builder | $29 | 1,000 | 1,000 | 1,000,000 | 3 |
| Pro | $79 | 4,000 | 4,000 | 5,000,000 | 10 |
| Scale | $299 | 20,000 | 20,000 | 20,000,000 | 10 |
Hobby is for personal, noncommercial projects. Builder, Pro and Scale support commercial use. Prices exclude applicable taxes. Checkout shows availability and the terms you are accepting. Distinct monthly active users hard-stop at the included concurrent connection allowance; there is no MAU overage price.
Optional overages
Hobby stops at its included limits. Commercial plans start with overages off and $0 additional spending. To go beyond the included usage, enable overages and set one billing-cycle cap covering both connections and coordination message units. Distinct monthly active users are not an overage dimension and never raise that cap. The subscription and applicable taxes are separate from this cap.
| Plan | Extra peak connection per cycle | Extra 1 million coordination message units |
|---|---|---|
| Builder | $0.05 | $50 |
| Pro | $0.04 | $40 |
| Scale | $0.03 | $30 |
Usage is charged proportionally; there are no million-unit packs to buy. Higher tiers include more usage and lower overage rates. For example, 2,000 peak connections and 1.5 million units total $104 on Builder or $79 on Pro. Compare the whole bill for your usage; an upgrade is not always cheaper. Automatic in-cycle upgrades and proration are not offered in this first release.
Included developer control calls
Google-backed developer control calls (credential issue/refresh for account administration and ordinary control) share one included pool per billing term on the current offer. Inside the pool, those calls do not debit coordination message units. Past the pool, commercial plans debit 25 hosted units per call against the shared unit meter; Hobby refuses further ordinary control calls. Bounded safety controls (delete app, revoke, stop spending, billing recovery) keep separate reserves and are not billed. End-client credential and launch traffic uses a separate unbilled technical fuse of 100 calls per included client and never debits the developer control pool or hosted units.
| Plan | Included developer control calls / term |
|---|---|
| Hobby | 10,000 |
| Builder | 75,000 |
| Pro | 100,000 |
| Scale | 200,000 |
How usage is counted
- Connections: the highest number of simultaneously connected sessions across your apps in the billing cycle. An SDK root counts once across its rooms, spaces, user scope and ticket avenues; a live session counts once across its subscriptions. An offline device inventory row and a physical peer edge are not additional hosted clients. Separate roots, tabs or runtime sessions count separately. Reconnects do not add up over the month, and connection time is not billed per minute.
- Distinct monthly active users: unique authenticated end-user principals admitted during the purchased term, counted once per account. The allowance equals the plan's included concurrent connection cap (for example Hobby 100). New distinct users beyond that allowance are denied at Auth/admission. Reconnects for an already-admitted principal do not consume additional MAU. Connection overages do not raise the MAU hard stop, and OpenRTC does not sell a MAU overage price in this release.
- Coordination message units: under the coordination-attempt offer, each eligible authenticated access attempt, accepted join or renewal, publication and recipient copy uses coordination message units as described below. Google- backed developer control calls first consume the included control-call pool above; only overage control calls on commercial plans debit hosted units (25 each). A fresh service retry counts again; the result or acknowledgement of the same admitted attempt does not.
- Publications and data: each publication and attempted recipient copy uses units rounded up in 4 KiB increments based on the largest encoded frame in that publication. Each admitted hosted response page is rounded by its own encoded size and uses at least one unit, including an empty page. Ten eligible attempts use 10 units; a publication of up to 4 KiB with 20 admitted recipient copies uses 21 units.
- Direct peer traffic: does not consume coordination message units. Authentication protocol, pings, acknowledgements and bounded safety controls are not billed. Default peer fallback uses public n0 Iroh relays or a developer-supplied (BYO) relay configuration; those paths are outside the subscription. OpenRTC-paid relayed-GB is a separate optional overage product, bounded by an account byte cap, disabled by default, and not included in any plan allowance. It is not sold in this release.
These rules apply when the coordination-attempt offer is explicitly offered and selected. Checkout shows availability and the terms you are accepting. Existing accepted terms retain their counting rules and finite request, rate and billing-term allowances; reconnecting does not refill those allowances.
Account connection capacity is separate from the supported size of one avenue. Direct room and space collaboration admits at most 50 members. Snapshot and page bounds may show up to 100 roster rows; that is not the admit limit. The owned-device roster has a 500-device bound per app-scoped principal, and ticket meshes admit 2–8 participants including the issuer. Signed grants, topology and rollout rules can impose lower limits; a larger account plan does not raise them. Your app chooses its product limits within those supported bounds.
Message size, delivery rate and subscription limits also apply. See the live coordination guide for the API and technical limits. Connection capacity does not imply unlimited messages.
Billing and spending controls
Subscriptions renew monthly. Additional usage is collected as it accrues and must remain within your selected cap. When overages are off, the cap is reached, or payment is required, activity that would create additional charges is denied. Reducing a cap does not erase charges already incurred. Usage and connection allowances are shared across the account rather than multiplied by app count.
Your accepted prices and allowances remain attached to your purchased term. See the Terms of Service for monthly renewal changes. Existing capacity and prepaid coordination subscriptions keep their accepted terms for cancel and downgrade only; new purchases and capacity upgrades are closed. Historical live terms also remain unchanged. New purchases use the current live offer only.
Open Billing to view your subscription and manage additional spending.