Metaplay vs Nakama: Which Game Backend Fits Your Studio?

Metaplay vs Nakama at a glance

Metaplay and Nakama address different halves of the same problem. Nakama, from Heroic Labs, is an Apache-2.0 multiplayer server you self-host for free and extend in Go, Lua, or TypeScript. It covers real-time sessions, matchmaking, chat, and social graphs. Metaplay is a source-available platform founded in 2019 by people with backgrounds in the game and software industries, where your game logic is written once in C# and runs on both the Unity client and the .NET server, with LiveOps, economy, and player management included. Nakama provides infrastructure control and a multiplayer core with no licence fee. Metaplay provides server-authoritative logic plus LiveOps as one system for Unity live-service games, without integrating separate products.

Category	Metaplay	Nakama (Heroic Labs)
Architecture	Server-authoritative; shared C# client/server logic	Multiplayer server you extend; relayed or authoritative matches
Engine fit	Unity-first (C#); other engines via API only	Unity, Unreal, Godot, Defold, and more
Multiplayer	Async-friendly Multiplayer Entities; async MMR matchmaker	Real-time core: relayed/authoritative matches, parties, presence, chat
LiveOps	Included: A/B tests, remote config, live events, segments	Separate product (Satori)
Economy	Included, server-authoritative	Separate toolkit (Hiro); IAP validation in Nakama core
Self-host	Via Private Cloud, your AWS account (commercial licence)	Yes, free (Apache-2.0), any cloud
Managed hosting	Metaplay Cloud (managed by Metaplay, AWS)	Heroic Cloud, Heroic infrastructure
Pricing	€1,985/mo + €2.95 per 1,000 DAU/day (details)	Free self-hosted; Heroic Cloud from ~$600/mo (USD, CPU-based)
Licence	Commercial, source-available	Apache-2.0 (OSI open-source)

Overview: a multiplayer server vs an integrated platform

Nakama is an open-source game server from Heroic Labs, licensed under Apache-2.0 and first released in 2017. It concentrates on real-time multiplayer plumbing: authentication, matchmaking, leaderboards, chat, social graphs, and a server runtime you write in Go, Lua, or TypeScript.

For LiveOps and game economy, Heroic Labs sells two adjacent products: Satori for experiments and segmentation, Hiro for progression and economy. Heroic Labs reports a community of more than 500,000 developers, and Nakama has been load-tested to 2 million concurrent connections.

Metaplay is a commercial platform founded in 2019 by people with backgrounds in the game and software industries. It ships as full source code and runs by default on Metaplay Cloud, a fully managed service Metaplay operates on AWS, with self-hosting in your own AWS account available via the Private Cloud plan.

The defining choice is shared logic: you write gameplay once in C#, and the same code compiles into the Unity client and the .NET server, with the server holding authority over all state. LiveOps, economy, and player management come as part of the platform rather than as separate purchases. Studios building on Metaplay include Metacore, Trailmix, and Lessmore.

Both give you the source, so you can self-host or fork. They differ in shape. Nakama is a modular server you bolt features onto. Metaplay is one integrated system where the client and server share a single source of truth, and most of the trade-offs below follow from that.

Architecture: configurable authority vs shared C# logic

Aspect	Metaplay	Nakama
Core language	C# (.NET)	Go
Custom logic	Direct C# modification	Server runtime: Go, Lua, TypeScript
Client SDKs	Unity (C#); others via API	Unity, Unreal, Godot, Defold, C++, JS, Swift, more
State authority	Server-authoritative	Configurable (relayed or authoritative)
Client/server sync	Automatic via shared logic	Manual; separate client and server code
Data storage	Managed (Aurora MySQL on Metaplay Cloud)	CockroachDB (PostgreSQL for dev)

Nakama is written in Go and built around real-time multiplayer. The server handles authentication, storage, matchmaking, and sessions, and you extend it through the server runtime in Go, Lua, or TypeScript. Multiplayer comes in relayed and authoritative modes. Relayed forwards messages between clients with no server-side game state. Authoritative runs your match handler on the server at a configurable tick rate, with lifecycle hooks for init, join, loop, and terminate. Persistence is Postgres-wire-compatible: PostgreSQL for development, with CockroachDB the officially supported production database.

Metaplay takes a different route. Your gameplay logic compiles into both the Unity client and the .NET server. When a player acts, the action runs locally first so the UI responds immediately, then the server replays the same deterministic code, validates the result, and persists it. If the two diverge, the server wins and resyncs the client. The server recomputes everything rather than trusting what the client reports, so client-state tampering is constrained at the architecture level.

This model assumes Unity and C#. Games on other engines can talk to a Metaplay backend over its API, but they don't get the shared-logic benefit: no single codebase, no automatic sync. Nakama covers more engines, with first-party SDKs for Unity, Unreal, Godot, Defold, and several others. Shared logic also imposes a constraint on the Unity teams that adopt it: a slice of game code has to stay deterministic across two runtimes.

AI and developer tooling: build-time agents vs in-game ML

"AI" means two different things in this market. One is tooling that helps your team build: coding assistants, MCP servers, codegen. The other is ML that runs inside your live game: churn prediction, spend forecasting, GenAI analytics. Metaplay's AI investment is in the first. Heroic Labs' is in the second, mostly through Satori.

Dimension	Metaplay	Nakama / Heroic Labs
Build-time AI tooling	Metaplay Agent (public preview) installs SDK skills for Claude Code, Cursor, and similar; plus Docs and Portal MCP servers and the MetaplayGPT chatbot	LLM-optimised Markdown docs for coding assistants; no official AI assistant, codegen, or MCP server (a community Nakama MCP server exists but is third-party)
In-game AI / ML	None built in; matchmaking, segmentation, and A/B testing are rules- and config-based; analytics stream to your warehouse	Satori's Databricks integration runs ML for churn, LTV, and engagement, writing scores back for segmentation; Satori also advertises GenAI features for querying datasets and summarising feedback

Metaplay's build-time tooling centres on the Metaplay Agent, currently a public preview, which installs SDK skills so a coding agent works like a Metaplay developer, with the Docs and Portal MCP servers exposing documentation, SDK source, and live infrastructure to those tools. Because you hold the source, the agent operates against the code itself rather than a black box.

Heroic Labs comes at AI from the live-game side. Satori's official Databricks integration is an in-product capability: churn, LTV, and engagement models that feed segmentation and experiment targeting. It runs through Databricks rather than as a turnkey feature, and Nakama's own build-time AI tooling is limited. Metaplay's AI work is build-time tooling that speeds up engineering; Heroic Labs' is ML-driven LiveOps analytics that runs on a Databricks pipeline.

Multiplayer: real-time core vs server-authoritative entities

Feature	Metaplay	Nakama
Relayed (client) multiplayer	Via integration	Built-in
Authoritative multiplayer	Built-in (C#)	Built-in (Go/Lua/TS)
Matchmaking	Async MMR matchmaker	Pool-based, with query syntax
Parties	Via integration	Built-in
Presence	Via integration	Built-in
Real-time chat	Via integration	Built-in
Voice	Via integration	Via integration

Nakama was designed from the start as a real-time multiplayer server, and presence, parties, and chat are part of the core product rather than add-ons. Its matchmaker pools players against custom criteria with a query syntax, supports match listing for lobbies, and a single node can run thousands of concurrent matches. Low-latency real-time sessions, parties, and in-game chat are built in.

Metaplay's multiplayer is built on Multiplayer Entities: custom server-side entity types (battles, matches, rooms) that message-pass across a distributed cluster, paired with an async MMR matchmaker that uses buckets for skill- and progression-based matching. It fits asynchronous and server-authoritative gameplay: turn-based battles, raids, leaderboards-driven competition. It does not include a synchronous real-time matchmaker or a physics netcode layer for FPS-style hit detection, and there is no built-in chat; Metaplay games integrate a third-party service for that. Real-time relay and built-in chat are part of Nakama's core and not part of Metaplay's.

LiveOps: included vs a separate Satori subscription

Feature	Metaplay	Nakama + Satori
A/B testing	Experiments	Satori Experiments
Remote config	Game Configs (OTA)	Satori Feature Flags
Live events	LiveOps Events	Satori Live Events
Player segmentation	Player Segments	Satori Audiences
Messaging / push	Mail, broadcasts, FCM push	Satori Messages (OneSignal/APNS/FCM)
Dashboard	Included, source-customisable	Satori Dashboard (separate)

Nakama on its own has storage and leaderboards but not LiveOps. Experiments, feature flags, live events, and player segmentation live in Satori, a separate product with its own dashboard, licence, and pricing that integrates with Nakama. Satori can run against a backend that isn't Nakama; it is also a second system to wire up and pay for.

Metaplay treats LiveOps as part of the platform. A/B testing, over-the-air Game Config updates, live events, and player segmentation ship in every paid tier and are managed from the same LiveOps Dashboard as the rest of your game, and because you hold the dashboard source (Vue.js/TypeScript), you can extend it with game-specific pages. There's no separate LiveOps SKU to add later.

Economy, social, and engine support

For economy and progression, the two platforms split the same way as LiveOps. Nakama validates in-app purchases for Apple, Google, and Huawei in its core, while currencies, inventory, achievements, energy, and teams come from Hiro, a separate toolkit with broad client support (Unity, Unreal, Godot, and more).

Metaplay's economy is server-authoritative and built into the platform: currencies and inventory live in the player model, every transaction is validated server-side through player actions, and the client shows the result. The economy is authoritative by default rather than dependent on the client implementation.

Feature	Metaplay	Nakama / Heroic Labs
Virtual currency & inventory	Built-in, server-authoritative	Hiro Economy/Inventory (separate toolkit)
IAP validation	Google, Apple, Steam	Nakama core: Apple, Google, Huawei
Achievements & progression	MetaRewards + player stats	Hiro Achievements
Friends & guilds/clans	Guild framework	Friends + Groups
Leaderboards & tournaments	Leagues (sharded leaderboards)	Leaderboards + Tournaments
Engine support	Unity (shared logic); others API-only	Unity, Unreal, Godot, Defold, and more

On social and engine breadth, Nakama covers more ground. Its friends, groups, leaderboards, and tournaments are engine-agnostic, and the SDK list is long. Metaplay covers the same social feature set through its Guild framework and Leagues-based leaderboards, with the shared-logic benefit applying on Unity. Nakama provides first-class Unreal, Godot, and Defold support; Metaplay's shared logic applies to Unity teams.

Deployment: managed Metaplay Cloud or self-host vs Nakama self-hosting and Heroic Cloud

Aspect	Metaplay	Nakama
Self-hosted	Via Private Cloud, commercial licence	Yes, free (Apache-2.0)
Where it runs	Metaplay Cloud (managed by Metaplay, AWS) by default; self-host in your AWS account (Terraform/Helm, EKS/RDS/S3/CloudFront) via Private Cloud	Any cloud or private infrastructure
Managed option	Metaplay Cloud, managed by Metaplay on AWS	Heroic Cloud (Heroic infrastructure, GCP or AWS)
Database	Managed (Aurora MySQL)	CockroachDB (PostgreSQL for dev)
Docker	Supported	Supported

Nakama's Apache-2.0 licence lets you self-host for free, on any cloud or your own metal, paying only for infrastructure and DevOps time rather than software. Heroic Labs recommends CockroachDB for production. If you'd rather not run it yourself, Heroic Cloud hosts Nakama (and Satori) on Heroic's own infrastructure with managed database, CI/CD, backups, auto-scaling, and load balancing.

Metaplay ships source code in every paid tier and runs by default on Metaplay Cloud, where Metaplay provisions and operates your environments on its own AWS infrastructure. For studios that need to run it themselves, the Private Cloud plan self-hosts into your AWS account using Terraform modules and Helm charts: you own the EKS cluster, RDS database, and CloudFront distribution.

Either way the deployment targets AWS, not GCP or Azure. A commercial licence is required either way.

Pricing: per-day DAU licence vs CPU-based Heroic Cloud

The two pricing models aren't directly comparable. Metaplay bills a flat platform fee plus a per-day DAU licence in euros. Heroic Cloud bills for CPU capacity in US dollars. One scales with how many players you have, the other with how much compute you provision. The figures below are in different currencies, so a dollar number and a euro number aren't like-for-like.

Nakama and Heroic Labs pricing

Component	Cost
Nakama (self-hosted)	Free (Apache-2.0)
Heroic Cloud	From ~$600/month (USD, CPU-based; priced via calculator)
Satori	From $600/month (USD)
Hiro	Contact Heroic Labs

Heroic Cloud is priced by the CPU you provision for Nakama instances and their database, configured through a calculator on the Heroic Labs site, with a practical entry point around $600/month. It includes the Nakama Enterprise licence (which unlocks multi-server clustering), dedicated hardware, managed database, CI/CD, backups, metrics, auto-scaling, and load balancing, with no DAU, MAU, or CCU caps. If you also need Satori for LiveOps, that's a separate subscription from $600/month.

Support is sold in tiers: Basic at $2,000/month (weekday email, 24-hour response), Standard at $6,000/month (24/7, 8-hour response, 99.5% uptime SLA), and Premium at custom pricing (private Slack, 1-hour response, 99.9% SLA). Source: Heroic Labs pricing.

Metaplay pricing

Tier	Price	Includes
Free	€0/month	Local development, full SDK
Starter	€195/month	1 mini environment, cap 5 DAU
Pre-Launch	€995/month	2 small environments, cap 100 DAU
Production	€1,985/month + €2.95 per 1,000 DAU/day	Staging + production; first 5,000 DAU/day included
Private Cloud	Custom (€2 per 1,000 DAU)	Self-hosted, for very large scale

Every paid Metaplay tier includes the full platform: LiveOps, economy, analytics, and player management are not separate line items. On the Production licence fee, the €2.95 per 1,000 DAU is a daily charge, applied each day and summed across the month, with the first 5,000 DAU/day free.

At a sustained 100,000 DAU every day in a 30-day month, the daily billable is 95,000 DAU → 95,000 ÷ 1,000 × €2.95 = €280.25/day → ×30 = €8,407.50/month in licence fees, plus the €1,985 base = €10,392.50/month total. (At 50,000 DAU it works out to about €5,967.50/month; at 500,000 DAU, roughly €45,792.50/month.) See Metaplay pricing for the live worked example.

Put that €10,392.50/month in context: it is roughly the fully loaded cost of a single experienced backend engineer. The alternative to a managed platform is building and operating these systems yourself, which means staffing a full backend and DevOps team for the life of the game. Among the options here, Metaplay is the only one that delivers a source-available backend as a managed service, so a studio gets server-authoritative logic, LiveOps, and economy without assembling that team and without lock-in. Metaplay's own analysis puts an in-house backend build at around $21M over a typical multi-year build: The true cost of building your own backend.

Cost comparison

Scenario	Metaplay	Nakama (Heroic Cloud)
Self-hosted	Commercial licence required	Free (Apache-2.0)
Minimal managed	€195/month (Starter)	From ~$600/month (USD)
LiveOps included?	Yes, in every tier	No; add Satori from $600/month (USD)
At 100,000 DAU/day	€10,392.50/month (details)	Depends on provisioned CPU

Self-hosting Nakama carries no licence cost; you pay only for your own infrastructure and the DevOps time to run it. For managed hosting the picture is model-dependent: Heroic Cloud scales with the CPU you provision, while Metaplay scales with DAU regardless of how much compute the workload needs.

The units differ (dollars per CPU versus euros per DAU), and adding Satori roughly doubles the Heroic Cloud entry cost for LiveOps parity. Modelling both against projected players and concurrency produces a figure specific to a given game rather than a single headline number.

Where each platform fits

If you need...	Consider
Open-source with no licence fees	Nakama (self-hosted)
Real-time relay, parties, and built-in chat	Nakama
Unreal, Godot, or Defold support	Nakama
Modular components you assemble	Nakama + Satori + Hiro
ML-driven LiveOps analytics (Databricks)	Satori
Unity with shared client/server logic	Metaplay
Server-authoritative economy by default	Metaplay
LiveOps included without a second subscription	Metaplay
Predictable DAU-based pricing	Metaplay
Build-time AI tooling (agents, MCP)	Metaplay

In summary: Nakama fits games that are real-time-first or multi-engine, and teams that want infrastructure control with no licence fee. Metaplay fits Unity live-service games that need a server-authoritative economy and integrated LiveOps, and keeps the client and server in lockstep through shared logic. Many teams could ship on either; the distinguishing factors are engine, whether real-time chat is core, and whether the stack is assembled from components or adopted as one integrated system.

Migrating between Metaplay and Nakama

Moving to Metaplay from Nakama. Nakama's data models for users, storage, and leaderboards map onto Metaplay equivalents. Server runtime code written in Go, Lua, or TypeScript has to be ported to C#, which is the bulk of the work. If you're using Satori, its experiments and live events can be rebuilt in Metaplay's built-in experiments and live events. Unity SDK migration is limited in scope since both platforms support Unity.

Moving to Nakama from Metaplay. Because Metaplay gives you full source, you can reference exact data structures while migrating. Economy and progression logic will likely need Hiro, since Nakama's core doesn't include them. The bigger lift is architectural: Metaplay's shared client/server codebase has to be split into Nakama's separate client and server code, so plan for restructuring rather than a straight port.

FAQ

Is Nakama free for commercial use?

Yes. Nakama is licensed under Apache-2.0, so you can self-host it for free for commercial games: you pay only for your own infrastructure and DevOps time, not for the software. The paid pieces are Heroic Cloud (managed hosting, which includes the Nakama Enterprise licence for multi-server clustering) and the adjacent Satori and Hiro products.

How much does Heroic Cloud cost?

Heroic Cloud is priced by CPU capacity in US dollars, configured through a calculator on the Heroic Labs site, with a practical starting point around $600/month for a small Nakama instance plus database. It includes the Nakama Enterprise licence, managed database, CI/CD, backups, auto-scaling, and load balancing, with no DAU, MAU, or CCU caps. LiveOps via Satori is a separate subscription from $600/month, and support tiers run $2,000/month (Basic) to $6,000/month (Standard) to custom (Premium).

How much does Metaplay cost at 100,000 DAU?

Metaplay's Production tier is €1,985/month plus a licence fee of €2.95 per 1,000 DAU charged daily, with the first 5,000 DAU/day free. At a sustained 100,000 DAU across a 30-day month, that's 95,000 billable DAU/day → €280.25/day → €8,407.50/month, plus the €1,985 base = €10,392.50/month. See the pricing page for the live worked example.

Can Nakama scale to millions of players?

Yes. Heroic Labs has load-tested Nakama to 2 million concurrent connections, and its enterprise clustering uses CRDTs and peer-to-peer gossip with CockroachDB for geo-distributed storage. The multiplayer core was built for real-time scale.

Can I use Nakama for LiveOps without Satori?

Nakama's core gives you storage and leaderboards, but not A/B testing, experiments, feature flags, or player segmentation. For real LiveOps you'll add Satori (or another LiveOps tool). By contrast, Metaplay includes LiveOps in every paid tier with no separate product.

Does Metaplay support Unreal?

Not as a first-class engine. Metaplay's shared client/server logic requires Unity and C#. Unreal games can connect to a Metaplay backend over its API, but they don't get the shared-logic benefit: a single codebase and automatic sync. Nakama provides a first-party Unreal SDK.

Which has better real-time multiplayer?

Nakama was built specifically for real-time multiplayer, with relayed and authoritative match handling, presence, parties, and built-in chat. Metaplay's multiplayer is server-authoritative and async-friendly via Multiplayer Entities, which suits turn-based and economy-driven games; it has no real-time relay or built-in chat and integrates a third party for chat.

Can I switch platforms later?

Both give you source access or self-hosting, so migration is possible, but architectural differences (shared C# logic vs separate client/server code, integrated vs modular) make it non-trivial. The engineering effort depends on how far the two architectures diverge for your game.

See Metaplay for your game

Want to see whether Metaplay's shared-logic architecture and built-in LiveOps fit your project? Get a demo and we'll walk through your game with you. You can also dig into the pricing details, or compare other backends in our guides to Metaplay vs PlayFab and Metaplay vs Beamable.