Estimate your bill
Drag to your monthly peak concurrent players. Each CCU is priced at its band's rate, like income tax — and crashes are never the meter.
The CCU ladder
One meter, graduated bands. Volume discounts are baked in — the more you scale, the less each CCU costs.
A launch spike costs money, not data — on any tier. Paid plans have no row budget; free includes 1.68M rows per fixed 30-day window, and going past it neither stops ingestion nor starts billing — billing follows your peak CCU alone.
A hosted MCP server — connect Claude or Cursor with a key you mint. €20/mo per studio, or $22/mo if your account bills in USD — which it does once you have a CCU subscription, since the CCU ladder is priced in USD.
Managed stack traces are readable out of the box; upload symbols from CI so native frames resolve as that work ships.
Export your raw data anytime. EU residency, no lock-in, no hostage analytics.
QUESTIONS, ANSWERED.
Your highest concurrent player count in one billing period, measured in UTC, computed from session heartbeats. You're billed on that single number — not seats, not events, not crashes. The quantity you are invoiced for is the highest concurrent player count over your subscription's own monthly billing period, which runs from its anniversary date rather than from the 1st of the calendar month. Before you have a subscription the dashboard shows the peak over the UTC calendar month so far instead. Either way the window is measured in UTC, not in your local time.