Nakama Pricing 2026: Self-Hosted vs Heroic Cloud Costs + Alternatives

Nakama is not “free versus paid.” It is three different buying decisions: use the open-source server and operate it yourself, pay Heroic Labs to operate Nakama on Heroic Cloud, or choose a managed backend with a different extension and pricing model. The right comparison includes the database, backups, deployments, upgrades, observability, and whoever answers the alert at 2am.

Nakama pricing at a glance

Option	Software/platform price	You still own	Best fit
Nakama OSS	$0 license	Compute, PostgreSQL, backups, upgrades, scaling, monitoring, incidents	Teams that need source access and have platform capacity
Nakama on Heroic Cloud	Interactive quote based on Nakama CPU + database CPU	Game code, data model, integration, capacity decisions	Teams that want managed Nakama and dedicated resources
Satori on Heroic Cloud	Starts at $600/month	Event design, audience rules, experiment design	Teams adding managed LiveOps
Crux	$0 / $10 / $79 monthly tiers	Game-specific logic and dedicated game-server compute	Teams wanting a managed, fixed-scope backend without operating Nakama

What does self-hosted Nakama really cost?

The Nakama executable and source are available under the Apache 2.0 license. A production installation still needs PostgreSQL, a load balancer or ingress, TLS, backups, logs, metrics, secrets, deployment automation, and a tested recovery path. A single-node development stack is not the same product as a redundant live service.

Scenario	Illustrative infrastructure	Engineering cost
Prototype / small closed test	$20-$100/month	Initial setup and occasional maintenance
Small production title	$100-$500/month	Backups, updates, monitoring, incident response
Growing title with redundancy	$500-$3,000+/month	Capacity planning, failover, upgrades, on-call rotation

These are planning ranges for ordinary cloud infrastructure, not Heroic Labs quotes. Player behavior, realtime traffic, regions, high availability, telemetry retention, and support expectations can move them substantially. One platform-engineering day per month can cost more than the servers.

Heroic Cloud pricing

Heroic Labs' public calculator sizes Nakama CPU and database CPU. Its managed plans include Nakama Enterprise, dedicated resources, a dedicated managed database, continuous integration for server modules, backups, monitoring, scaling, load balancing, TLS, and log aggregation. The official page states there are no DAU, MAU, or CCU limits; cost follows provisioned resources rather than player counters.

The page also lists smaller burstable development options and paid support packages. At verification time, Studio Basic support was $2,000 and Studio Standard was $6,000; premium support is quoted. Treat support and Satori as separate purchasing decisions instead of assuming every Heroic Cloud deployment includes them.

Is Satori included with Nakama?

No. Satori is Heroic Labs' LiveOps product for events, audiences, feature flags, and experiments. The public pricing page lists managed Satori from $600/month. You can use Nakama without Satori, or add another analytics/experimentation stack. Include that line item only if you actually need those capabilities.

Self-hosted Nakama vs Heroic Cloud

Decision	Self-hosted Nakama	Heroic Cloud
Source and extensions	Full OSS control; Go, TypeScript, or Lua runtime modules	Nakama extension model with managed deployment tooling
Database operations	Your team owns PostgreSQL and recovery	Dedicated managed database, backups, monitoring
Scaling and incidents	Your team	Heroic Labs operates the platform; support/SLA level depends on package
Cost driver	Infrastructure plus labor	Provisioned Nakama and database resources
Exit path	You already own deployment and data	Nakama-compatible architecture reduces application lock-in, but operations move back to you

Nakama alternatives

A Nakama alternative is not automatically a cheaper Nakama. It usually changes who owns server-side code, realtime multiplayer, LiveOps, and operations.

• PlayFab: broader Microsoft game-services and LiveOps surface, with Foundation Mode for eligible Xbox titles and metered paid modes.
• Crux: managed player auth, documents, stats, achievements, leaderboards, economy, social, matchmaking, live config, and server registry. Game-specific logic stays in your game server or services.
• Custom backend: maximum freedom and maximum operational ownership.

When to choose each

Choose self-hosted Nakama when

• backend runtime customization is part of the product;
• data locality or private-cloud deployment is mandatory;
• the team already operates PostgreSQL and production services;
• owning upgrades and incidents is an acceptable trade.

Choose Heroic Cloud when

• you want Nakama's APIs and extension model without operating the cluster;
• dedicated resources, managed database, backups, logs, and scaling justify the price;
• resource-based pricing fits better than MAU/CCU metering.

Choose a fixed-scope managed alternative when

• your requirements are standard backend primitives rather than custom in-backend logic;
• you want a published flat price at indie scale;
• you prefer game logic to run in authoritative game servers you control.

Bottom line

Nakama OSS costs $0 to license, not $0 to run. Heroic Cloud buys back the operational work and prices the dedicated resources that do it. Satori is a separate LiveOps cost. Compare the annual platform invoice with the annual engineering ownership—not with a one-node Docker Compose bill.

For a hands-on exit plan, read migrating from Nakama to Crux. For the broader platform decision, use self-hosted vs managed backend.