Aeion BaaS Pricing — Game Backend Without the CCU Tax
No per-CCU (concurrent users) charge like PlayFab. No per-message Realtime fee like Firebase. No per-minute voice charge like Vivox. One flat plan — $49/mo, unlimited users, unlimited CCU/MAU, everything included: Glicko-2 matchmaking, currency/inventory economy, realtime, push, live-ops, and cloud functions. 14-day free trial.
Why "No Per-CCU Fee" Matters
Most game-backend platforms charge by concurrent users — the more popular your game gets, the more it costs you to keep it running. PlayFab + Firebase + Photon all do this.
Function Execution Math
Cloud functions in Aeion BaaS run in a node:vm sandbox today (not the hardened isolation a production-security review would want — see the module's tech-specs for the current state) and are included in the flat $49/mo plan, up to 10M executions/month.
Voice Chat Cost Reality
Voice chat is the biggest hidden cost of game backends. Vivox + Agora dominate the hosted-voice market.
Pricing FAQ
Yes. Aeion's plan is flat. The platform doesn't have per-CCU billing infrastructure; charging for it would require building infrastructure that adds cost without value.
Those are YOUR infrastructure costs. Aeion runs against your Postgres + Redis (or managed equivalents). At high CCU, you'll need dedicated Postgres + Redis clusters; that's ~$2-10K/month in cloud costs regardless of which BaaS you use. It's the infrastructure underneath, not the BaaS plan.
No permanent free tier — every account starts with a 14-day free trial with full feature access, then $49/mo flat, unlimited users.
Talk to us about a custom capacity arrangement. The $49/mo plan doesn't change — capacity beyond the included amounts is negotiated separately, same as air-gapped deployment.
Your Postgres infrastructure. Aeion's collections live there. For high-CCU games, plan a dedicated database with read replicas + Postgres tuning.
Yes — 20% off annual plans.
Yes via dual-running. Set up Aeion + parallel-mirror the writes from PlayFab during a transition window; flip the read source per-feature; deprecate PlayFab when 100% coverage achieved. Plan ~3-6 sprints depending on feature usage.