Pricing
That is the whole bill, drawn from a prepaid wallet as you use it. There is no subscription, no seat or per-app fee, and no charge per message or API call.
How Billing Works
3 meters, paid from one wallet.
We meter network bytes in and out, CPU time and stored data. Each app gets a monthly free allowance on each; above it, usage is charged to your wallet within about a minute. If the wallet is empty, usage stops.
Free Tier
Each has its own monthly allowance, sized for a casual 4-player game. No card required.
Data Out
5GB
per app, per month
State, replication and fan-out delivered to your clients, measured at the network interface.
Data In
5GB
per app, per month
What your clients send. Separate from the data-out allowance.
Compute
20CPU-hrs
per app, per month
One pool for GraphQL resolvers, automations and compute modules.
Storage
1GB-month
per app, held for the month
Durable data held over time. 1 GB kept all month, or 2 GB kept for half of it.
The allowance is a hard limit. When an app uses one up, its traffic is refused until the month resets or you fund a wallet. Free apps are soft-capped at about 1 MB/s; funding a wallet lifts the cap. Allowances reset monthly and do not roll over. Compute modules also get 1 GB of writes per app per month; beyond it, writes are charged by the byte, not by the row.
Rate Card
| Dimension | Free each month | Price |
|---|---|---|
| Network | ||
| Data outDelivered to your clients | 5 GB per app | from$0.19per GB |
| Data inSent by your clients | 5 GB per app | $0.02per GB |
| Compute | ||
| CPU timeResolvers, automations and compute modules | 20 CPU-hours per app, pooled | $0.20per CPU-hour |
| Storage | ||
| Stored dataDurable data held over time | 1 GB-month per app | $0.20per GB-month |
| Stored input logsReplay logging only; includes voice and video unless you leave them out, kept 7 days | None | $0.10per GB-month |
| Module writesCharged by the byte; rows are not counted | 1 GB per app | $0.25per GB |
| Optional reserved capacity | ||
| Reserved realtime throughputA floor, not a ceiling, charged in addition to metered usage | — | $3.00per MB/s per month |
Data out is priced in volume bands, per app, per calendar month. Each GB is charged at the band the month’s total has reached; the free 5 GB counts toward the first.
A 120 TB month: 995 GB × $0.19 + 9,000 GB × $0.18 + 90,000 GB × $0.16 + 20,000 GB × $0.14 = $19,009.05, an average of 15.8¢ a GB.
Counts are never priced. Messages, API operations, notifications and module-written rows cost only the bytes and CPU they use.
Charged as it happens. Each meter’s monthly total is rounded up to the cent once and drawn from your wallet as it crosses each cent, within about a minute. Your account itemises it by the hour.
Decimal units, wire bytes. 1 GB = 1,000,000,000 bytes, as carriers bill. Bytes are measured on the wire, after compression.
Stored input logs are recorded bytes. Replay logging is off until you turn it on for an app, which needs a wallet balance covering 7 days of that app’s recent traffic. It records every message the Service accepts from your clients, including keep-alives, voice and video; when an app carries voice or video, they usually dominate, and you can leave them out of an app’s recording and keep everything else. An idle player records about 50–110 bytes a second, plus a third of their actor state’s size a second because the SDKs resend state every 3 seconds. Each message is counted at its record size (a fixed header plus the message, before compression and replication) and billed for the 7 days it is kept, so 1 GB recorded is 168 GB-hours: 0.23 GB-month. Turning logging off stops recording within about 15 seconds; what was recorded stays billed until it ages out. The API returns each record’s size.
Player-Authored Compute
When players run their own compute modules, the player’s wallet pays. Each player with a wallet gets a 250,000 compute-unit trial per app per month, then pays the same CPU, data-out and storage rates as above, plus any markup you set. Amounts under a cent carry forward. Managed players have no wallet and no trial, so their usage bills your organization at the rates above.
Coming: pay your players' way. Organizations will be able to cover player costs from their own wallet, for everyone or on your terms. Until then, a player’s wallet pays only for player-authored modules, and only in apps where you enable player compute. Everything else on this page bills your organization.
What It Looks Like
Full-mesh data out is N × (N−1) × f × b, where N is players, f is updates per second and b is bytes per update. For 4 players that is 12 × f × b.
10 updates a second, 40 bytes each. About 17 MB of data out per hour of play.
15 updates a second, 60 bytes each. About 39 MB of data out per hour of play.
20 updates a second, 100 bytes each, played twice as much. About 86 MB an hour, just over the allowance.
A live game with a community: 60 GB out, 8 GB in, 30 CPU-hours of resolvers and automations, 5 GB kept in the database all month.
Full mesh, one free app, data out only. The calculator below adds the other meters.
Illustrative only. Real figures depend on tick rate, snapshot and delta sizes, compression and server-side compute. Each example is one free app; an organization has 3.
Estimate Your Bill
Simple takes the 4 meters from your usage page. Advanced derives them from the world you describe: actors, cadence, payload and spatial reach.
This is an estimate. The advanced model counts the actors within replication distance at your density and thins delivery by your decay setting. Real worlds cluster and spread, and interest management may deliver fewer updates. It ignores compression, which only lowers the bill, and leaves out compute paid from players’ wallets.
The Details
There is one rate card, and every organization pays it. The live copy is on Studio’s pricing page and in your account; if this page lags, the live card applies. A rate change applies from the time it is published, except that an app that has already used a meter this month keeps that meter’s rates, bands and free allowance until the month ends.
The Free Tier and Billing Basis, part of the Rate Card under the API Terms of Service, sets out how bytes are counted and what happens at the limit. Reserved throughput is self-serve from your account. No rate is negotiated, and an enterprise agreement does not change the card.
Enterprise
Private environments and custom SLAs are priced by agreement. Tell us what you are building.
Talk to UsDevelopers
Build on the shared environment and fund a wallet only when you outgrow the free tier. No card required.
Get API Access