Nakama Pricing 2026: OSS vs Heroic Cloud Costs

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	Resource-based: Nakama + database capacity; active deployment usage billed daily and invoiced monthly	Game code, data model, integration, capacity decisions, optional add-ons/support	Teams that want managed Nakama and dedicated resources
Satori on Heroic Cloud	Starts at $600/month + event-based ingestion pricing	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, so the software-license line is genuinely $0. The production bill is the system around it: Nakama compute, PostgreSQL, ingress/load balancing, TLS, backups and object storage, logs/metrics, secrets, deployment automation, network egress, redundancy, and the engineers who test recovery and answer incidents.

Cost bucket	What to model	Why it moves
Application compute	Nakama nodes, CPU/RAM, environments, regions	Concurrency, realtime features, custom runtime code, redundancy
Database	PostgreSQL compute/storage, replicas, backups, I/O	Write volume, retention, HA and recovery targets
Edge + observability	Load balancer/ingress, TLS, egress, logs, metrics, alerts	Traffic shape, telemetry retention and region count
Operations	Deployments, upgrades, security work, restore tests, incidents/on-call	Your automation maturity and reliability target

Use a TCO equation instead of a made-up per-player number: monthly infrastructure + loaded platform-engineering time + expected incident/on-call cost + any redundancy/region premium. If you cannot put a number on the engineering term, comparing self-hosting with a managed invoice is not yet an apples-to-apples comparison.

Heroic Cloud pricing

Heroic Labs' public calculator sizes Nakama CPU and database CPU. The managed Nakama plan includes Nakama Enterprise, dedicated resources, a dedicated managed database, CI for server modules, backups, monitoring, scaling, load balancing, TLS, and log aggregation. Heroic Labs explicitly states that these plans do not meter DAU, MAU, or CCU; the core cost follows allocated deployment capacity instead.

The billing documentation adds an important detail to the marketing calculator: charges accrue daily for active deployments and are invoiced monthly. Support plans are recurring charges, and optional add-ons can include log exporting, metric exporting, enterprise SSO, database replicas, and profiling. That means “resource-based, not player-metered” is accurate; “one fixed monthly number regardless of deployment choices” is not.

At verification time, Studio Basic support is $2,000/month, Studio Standard is $6,000/month, and Studio Premium is quoted. Smaller burstable development options are also advertised. Treat support, Satori, and optional operational add-ons as separate purchasing decisions instead of assuming every Heroic Cloud deployment bundles 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.