AccelByte vs Crux (2026): Public Cloud Pricing, Scope & Fit
AccelByte Public Cloud is free under 30 PCCU, then priced by daily peak concurrency. Compare AGS with Crux's $0/$10/$79 BaaS, matchmaking and identity.
September 2026 snapshot: AccelByte is no longer accurately described as “enterprise sales only.” AGS Public Cloud is self-serve, starts free, includes 30 PCCU at no charge, and then bills by daily Peak Concurrent Users (PCCU). AccelByte also publishes paid support tiers and separate pricing for Extend/custom backend logic. Crux uses a different commercial model: public BaaS tiers at $0 / $10 / $79 per month with MAU/API/resource limits.
If you are comparing AccelByte vs Crux, the biggest mistake is to compare one headline price. AccelByte Gaming Services (AGS) is a much broader game-platform stack, while Crux is a narrower managed BaaS. They also meter different workload dimensions.
AccelByte vs Crux at a glance
| Decision | AccelByte Gaming Services | Crux |
|---|---|---|
| Entry model | Public Cloud: start free; first 30 PCCU included, then usage-priced | Dev $0, Launch $10/month, Scale $79/month, then Custom |
| Primary billing unit | Daily Peak Concurrent Users (PCCU), plus separately metered products such as Extend / Multiplayer Servers where used | Plan limits across MAU, API calls, request rate, storage and backend resources |
| Deployment choices | Managed Public Cloud; dedicated Private Cloud for teams needing isolation/control | Managed multi-tenant BaaS; separate capacity-gated Runtime closed alpha |
| Identity | Cross-platform account linking across Steam, Xbox, PlayStation and other identity providers; roles/sanctions/admin controls | Email/guest, Google/GitHub/Discord OAuth, native Steam ticket verification; smaller account/admin surface |
| Multiplayer | Parties, presence, sessions, P2P, configurable/SBMM matchmaking, guilds/clans, chat, dedicated-server hosting | Friends/social, exact game_mode + region matcher, server registry; no equivalent party/guild/chat stack |
| Commerce | Store/catalog, wallet/payments, inventory and broader online-game systems | Economy currencies/inventory primitives; no generalized cross-platform commerce/receipt layer |
| Custom backend logic | Extend runs game-specific backend services alongside AGS | Custom logic lives in your own services/game servers; Crux exposes managed APIs rather than an arbitrary code runtime |
| Support | Community free; published Standard and Professional paid support tiers; enterprise options | Plan-defined support on Crux pricing; substantially smaller operational/support program |
AccelByte pricing is public now
The old version of this comparison said AccelByte pricing was opaque and required an enterprise sales engagement. That is no longer true for AGS Public Cloud.
AccelByte's current pricing page describes:
- 90 days of no-credit-card development access;
- a continuing free tier while the game stays at or below 30 PCCU;
- usage pricing based on the maximum concurrent players connected to and interacting with AGS APIs each day;
- package-dependent PCCU rates that decrease at larger concurrency bands;
- separate metering/trials for AccelByte Multiplayer Servers (AMS) and Extend; and
- paid support starting at $1,000/title/month for Standard and $5,500/title/month for Professional.
AccelByte's published Public Cloud entry is therefore not an enterprise annual minimum. Its economics depend on peak daily concurrency and which AGS package/services you use.
Do not compare PCCU directly with MAU
Crux and AccelByte meter different shapes. A game can have a large MAU count and modest PCCU, or a smaller audience concentrated into sharp concurrency peaks.
For AccelByte, model:
daily PCCU × package rate
+ AMS game-server compute/networking (if used)
+ Extend VM/log/egress usage (if used)
+ paid support tier (if purchased)For Crux, model whether the game fits inside the plan's MAU, API-call, request-rate, document/storage, leaderboard/config and other quotas.
A “500,000 MAU” Crux plan and a “500 PCCU” AccelByte workload are not comparable units. Use your measured DAU/concurrency curve instead of applying a fixed MAU→PCCU percentage.
Where AccelByte is materially stronger
Cross-platform identity and account operations
AGS has a mature identity/access layer with account linking for platform identity providers such as Steam, Xbox and PlayStation, plus authorization roles, sanctions and compliance/admin workflows. Crux's identity layer is intentionally smaller.
Multiplayer session stack
AccelByte's current multiplayer surface includes parties/presence, sessions, P2P hosting, configurable matchmaking, chat, guilds/clans and AccelByte Multiplayer Servers. Its matchmaking supports team-, skill- and role-based rules and can be extended through a gRPC plugin.
Crux's matcher is much narrower: exact game_mode + region queue pairing. It is not a drop-in replacement for AccelByte's rulesets, parties, backfill, session templates or SBMM.
Game-specific backend code without running the platform yourself
AccelByte Extend lets teams deploy custom backend services alongside AGS. AccelByte currently publishes Extend usage at $0.198/VM-hour, with separate log-ingestion and egress pricing after trial allowances.
Crux does not expose a comparable arbitrary-code execution environment. If your backend requires custom services tightly integrated with the platform, that difference matters more than the base BaaS price.
Dedicated game-server hosting
AccelByte Multiplayer Servers (AMS) is a production game-server hosting/orchestration product integrated with AGS sessions and matchmaking. Crux Runtime is not comparable today: it remains a capacity-gated closed alpha with a narrow Godot/Linux/EU/ephemeral-session contract.
Where Crux can be the simpler fit
You only need the smaller BaaS surface
If your game already owns party/session logic, game-specific matchmaking policy, commerce and server hosting elsewhere, you may not need the breadth of AGS. Crux can be used as the smaller persistence/auth/config/leaderboard/economy layer behind systems you already operate.
You prefer fixed plan envelopes over PCCU metering
Crux's standard BaaS pricing is a monthly plan rather than a daily PCCU curve. That can be easier to reason about for some workloads, but only if the game fits the plan's other quotas. “Flat price” does not mean unlimited usage.
You want a small API contract
AccelByte deliberately exposes a large platform. Crux deliberately exposes fewer systems. Fewer systems can mean less integration and operational surface when they cover the actual game; it can also mean building or buying missing systems elsewhere.
Public Cloud vs Private Cloud changes the comparison
AccelByte now explicitly gives teams two operating models:
- Public Cloud: shared fully managed environment, self-serve start, usage-based pricing.
- Private Cloud: dedicated isolated environment for greater control/compliance, sold separately.
AccelByte's documentation says it operates and maintains both deployment models. The old “AccelByte means your platform engineers operate the backend” framing is therefore wrong. You may still need platform/backend engineers because the product surface is broad and extensible, but not because Public Cloud makes you run AGS infrastructure.
Support is a separate budget line
Do not compare only API usage. AccelByte currently publishes:
- Community: free;
- Standard: $1,000/title/month; and
- Professional: $5,500/title/month, with faster support, account/solutions resources and launch planning.
Enterprise is custom. A production studio that needs a dedicated launch/support relationship should include this in the comparison instead of assuming either vendor's cheapest tier represents its real operating model.
A practical decision table
| If this is a first-order requirement... | Start by evaluating... |
|---|---|
| Cross-platform console identity/account linking and mature sanctions/admin workflows | AccelByte |
| Parties, guilds/clans, chat, configurable SBMM/backfill/session templates | AccelByte |
| Managed dedicated-server orchestration integrated with matchmaking | AccelByte AMS or another production orchestrator |
| Custom backend services hosted beside the platform | AccelByte Extend |
| Managed auth/data/leaderboards/config/economy primitives with a smaller contract | Crux is worth validating |
| Fixed public monthly BaaS tiers are operationally preferable to PCCU billing | Crux, after checking every quota |
Test the migration boundary, not the logo
If you are considering moving either direction, inventory the systems that actually hold state or define behavior:
- account/platform identity links;
- player documents/progression;
- inventory, wallet and commerce entitlements;
- friends, parties, guilds and sanctions;
- matchmaking rules, rating and backfill state;
- game-session/server allocation;
- live config/content and operator workflows; and
- custom services/events/webhooks.
A migration is cheap only when the destination actually owns the same responsibilities. Moving from a broad AGS deployment to Crux can reduce platform surface, but anything outside Crux's narrower contract must move somewhere else too.
Bottom line
AccelByte is no longer an “enterprise-only, opaque-price” backend. Its Public Cloud now creates a credible self-serve path from prototype through production, with usage-based PCCU pricing and a permanent small free allowance. Its advantage over Crux is breadth: cross-platform identity, richer multiplayer/session systems, commerce, custom Extend services and production server hosting.
Crux remains the smaller managed BaaS. Its advantage is a narrower contract and very low public plan prices when that narrower contract is enough. Choose based on the systems your game actually needs, not team size, AAA labels or unsupported annual-minimum guesses.
Related comparisons
Sources
Technical, pricing, and product claims were checked against these primary sources on the verification date above.