Existing prepaid coordination subscriptions

Account-pooled coordination plans, hosted message counting and prepaid additions.

This guide applies when Billing shows a messages and connections plan. Availability and your accepted terms appear in the Developer Portal. Existing capacity plans keep their purchased terms; this guide does not change an existing subscription.

For the new live offer with optional usage-based overages, see Pricing. This prepaid offer is separate.

One shared allowance

Choose a monthly plan for peak simultaneous connections and hosted messages. All included apps share both allowances. Rooms, spaces, users, devices and tickets are ways to organize your app, rather than separate usage charges. Technical inventory and room topology limits still apply.

Sandbox is one evaluation per developer account, subject to availability. It expires after 14 days and does not refill each month or after cancelling a paid plan. When evaluations are unavailable, you can still choose a paid plan; creating an account or opening Checkout grants no service allowance.

What is a concurrent connection?

One connection is one live runtime subscribed to one user scope, room, space or ticket avenue. A runtime in a user scope and two rooms occupies three slots. Two tabs subscribed to the same room occupy two slots. Multiple peer links inside one avenue do not each occupy another slot. Leaving an avenue releases its slot; a replacement of the same runtime does not briefly double its slot.

Slots are pooled across your account. Billing shows current and peak occupancy. The price is based on the number of simultaneous slots purchased, with no per-minute line item. A connection can remain open for the purchased term. Normal lease and credential maintenance is included within technical work limits. Per purchased slot, this offer includes 1,000 credential attempts, 100 fresh admissions, and 300 management/API operations per term. The account also allows twice its message allowance plus 1,000 authenticated frame attempts per slot. These are safety limits, with no additional charge; reconnecting does not reset them. Reconnect storms and repeated control requests remain bounded.

How hosted messages count

A hosted publication and each actual recipient socket enqueue count separately. Each serialized payload is rounded up independently to 4 KiB units, including UTF-8 bytes. Independent messages in a batch retain their own rounding.

• A 2 KiB publication delivered to three recipient sockets uses four units: one publication and three enqueues.
• A 6 KiB publication delivered to three recipient sockets uses eight units: two units for the publication and two for each enqueue.
• A publication accepted while its recipient is offline counts its publication units. Delivery units count only if enqueued before expiry; unused delivery reservations are released.

Billing distinguishes recorded units from pending reservations. A socket enqueue does not guarantee that an app received or processed a message. Duplicate requests retain their original identity and do not charge the same accepted publication or delivery twice. Rejected publications do not consume hosted message units. Protocol maintenance uses included technical work limits.

Direct peer-to-peer application data, media and file payloads do not consume hosted coordination message units. Establishing their connections still needs coordination slots and hosted signaling. Managed relay and hosted fanout are not included in this plan.

Optional prepaid additions

Paid plans can opt in to additions with an account spending ceiling. You review and pay for a fixed pack before it increases the allowance:

The message rate is $100 per million units, sold in fixed packs. Packs expire with the current term, do not carry over and do not renew automatically. Their price does not decrease when purchased late in the term. Starting payment requires enough time to complete it before expiry. A payment that cannot be applied receives the existing refund/reconciliation handling; check its retained receipt in Billing.

The spending ceiling includes paid and pending additions for the term; subscription fees are separate. Self-service capacity is limited to 1,000,000 total message units and 1,000 concurrent slots per term. Contact us for larger capacity. Additional message or connection packs do not raise app counts, technical inventory limits or room topology limits.

Rooms and technical limits

Reliable automatic rooms support up to eight members using peer mesh. Explicit peer mesh supports up to 16; latest-state sparse rooms support up to 50. An allowance of 50 or more connection slots does not imply that every topology supports a single room of that size. View technical inventory limits and recorded peaks in each app's Usage tab.

Hosted room authority/fanout, managed attestation, hosted token minting, managed broadcast, hosted application storage, TURN and MoQ are not included. Buying message or connection packs does not enable them. Your app retains its own identity provider and application authorization.

Billing and changes

Subscriptions and additions are paid in advance. Usage stops growing when an applicable allowance or technical limit is reached. Buying an available pack can increase its corresponding allowance; it does not reset usage or the term. Account billing remains accessible after a term ends.

Accepted prices and allowances stay fixed through the paid term. A different coordination pricing policy takes effect at renewal, including its safety limits. A change from a capacity plan to a messages-and-connections plan takes effect at renewal with the required acceptance. Cancellation does not create another evaluation.

There is no per-minute, per-room or per-device usage line item on this plan. Your total depends on the subscription and any packs you choose. Compare your expected hosted signaling and peak occupancy; a cheaper total than a different provider's per-minute plan depends on that workload and its included services.