Game Backend Pricing Models Compared (2026): Usage, Tiered & Self-Hosted

Compare 2026 game backend pricing models: pay-as-you-go PlayFab meters, fixed Crux tiers, resource-based Heroic Cloud, Photon CCU plans, and self-hosted Nakama. Learn which inputs actually determine the bill.

Written and reviewed by Supercraft Engineering Last verified: August 20, 2026

Choosing a game backend isn’t just about features-it’s about cost predictability and scalability. Backend platforms commonly use usage‑based (pay per meter, API call, or storage), tiered monthly (fixed fee with included limits), resource‑based managed (you select compute and database capacity), or self‑hosted pricing (you pay for infrastructure and operations). This article breaks down each model with examples from PlayFab, Metaplay, Crux, Nakama, and Beamable.

Quick answer: choose pay-as-you-go when traffic is unpredictable and you need a low fixed commitment; choose fixed tiers when predictable budgeting matters; choose self-hosting only when you are prepared to own reliability, upgrades, security, and on-call work. For a scenario using MAU, peak CCU, regions, and feature mix, use the game backend pricing calculator.

Important: MAU alone does not produce a comparable vendor bill. PlayFab has service meters and separate Multiplayer Server charges; Heroic Cloud prices Nakama by resource configuration rather than a fixed CCU tier.

Rule of thumb: Usage‑based fits unpredictable traffic; tiered monthly simplifies budgeting; self‑hosted offers lowest long‑term cost but highest operational overhead.

Usage‑Based and Resource‑Based Pricing

Platform	How It Works	Cost Drivers
PlayFab	Free to Start (up to 10 titles and 1,000 lifetime players per title), then PAYG with no monthly minimum, or Standard ($99/mo) and Premium ($1,999/mo) plans with included meters.	Service meters, title mode, storage, data egress, and separate Multiplayer Server compute/egress.
Beamable	Subscription and usage pricing varies by the current Beamable plan and deployment model.	Plan allowance, API/service usage, storage, and deployment requirements.
Heroic Cloud (Nakama)	Hosted Nakama priced from Nakama CPU and database CPU configuration; there are no DAU/MAU/CCU limits.	Nakama resources, database resources, optional Satori, support, and operational requirements.

Pros: Scales directly with player count; you only pay for what you use. Cons: Hard to predict monthly bills; can become expensive at high scale.

Tiered Monthly Pricing (Fixed Fee)

Platform	How It Works	Typical Price Range
Metaplay	Monthly subscription (Free, Pro, Enterprise) with included DAU, storage, and LiveOps features.	€995–1,985/mo for Pro; Enterprise custom.
Crux	Monthly tiers with included API calls, player documents, and server slots; overages billed at fixed rates.	Free (10,000 MAU) / $10 / $79 per mo; custom enterprise.
Photon (optional)	Public Cloud has development and launch plans plus fixed CCU packages; Premium Cloud is usage-based.	Peak CCU across regions, included traffic, traffic overage, and cloud tier.

Pros: Predictable costs; easier budgeting; often includes priority support. Cons: Can be expensive at low usage; may require upgrading tiers as you grow.

Self‑Hosted (Infrastructure Cost Only)

Platform	How It Works	Cost Drivers
Nakama Open Source	Free software; you provision servers, databases, load balancers, and pay for cloud/hosting bills.	VM/container costs, bandwidth, storage, DevOps engineer time.
Metaplay Enterprise	Self‑hosted option: you run Metaplay on your own infrastructure, paying license fee + infra.	License fee (discounted DAU rate) + cloud/hardware costs.
Beamable Private Cloud	Dedicated single‑tenant deployment; you pay subscription + infrastructure.	Monthly subscription + AWS/Azure/GCP bills.

Pros: Ultimate control, data locality, potentially lower long‑term cost at scale. Cons: High operational burden, upfront time investment, hidden costs of engineering hours.

Comparing Total Cost of Ownership (TCO)

A defensible comparison needs more than MAU. Record peak CCU, request and write volume, storage, egress, regions, game-server compute, support, and the engineering time required to operate the system. Two games with the same 10,000 MAU can have radically different bills.

Scenario	What to include	Common mistake
Managed metered service	Plan fee, service meters, storage, egress, support, and game-server compute.	Treating MAU as the whole bill.
Managed fixed tier	Tier price, included limits, throttling/upgrade behavior, and any excluded products.	Assuming a tier includes realtime servers or traffic by default.
Self-hosted	Compute, database, backups, traffic, monitoring, security, upgrades, and on-call labor.	Comparing only the VM invoice with a managed platform.

Use the cost calculator for a transparent scenario model, then verify the result against the vendor estimator before committing.

Choosing the Right Model for Your Studio

Indie / Small Team

Prioritize low fixed costs and simplicity. Crux’s published tiers are easy to budget; PlayFab’s Free to Start path is subject to title and lifetime-player limits, while live titles use the current meter/plan model. Avoid self‑hosting unless you have strong DevOps skills.

Growth‑Stage / VC‑Backed

You need scalability and professional support. Compare the actual meter/resource shape against your workload, then include support and game-server costs rather than comparing headline plan fees alone.

Enterprise / Large Studio

Control, compliance, and cost efficiency matter. Self‑hosted Nakama or private cloud deployments (Beamable Private Cloud, Metaplay Enterprise) let you own the stack while leveraging vendor expertise.

Negotiation tip: Most backend vendors offer custom enterprise pricing. If your game shows traction, ask for discounted rates or committed‑use contracts. Always model costs based on projected DAU, API call volume, and storage needs before signing.

Related in This Hub

Check each platform’s latest pricing: PlayFab, Metaplay, Crux, Beamable, and Heroic Labs.

Sources

Technical, pricing, and product claims were checked against these primary sources on the verification date above.