Metaplay

Deterministic re-execution with checksum validation

Client and server execute the same game logic independently. The server validates client actions by re-executing them deterministically and comparing checksums, catching cheats without round-trip latency.

Same C# compiles to Unity client and .NET server

Write game logic once in C# and compile it for both the Unity client (via IL2CPP) and the .NET server. No separate server codebase to maintain or keep in sync.

Single integrated platform (actor model)

All features (player state, configs, analytics, matchmaking) run inside a single actor-model server. No service mesh, API gateways, or cross-service coordination needed.

Full source: server, client SDK, and dashboard

Complete source code access to the server runtime, Unity SDK, and LiveOps dashboard. Modify, debug, and extend any component without waiting on vendor support.

Spreadsheets → typed C# objects → OTA binary delivery

Game designers edit spreadsheets that compile into strongly-typed C# config objects. Configs are validated at build time and delivered over-the-air as optimized binary archives.

Vue.js source available, designed to be extended

The LiveOps dashboard is built with Vue.js and ships with full source code. Teams can add custom pages, player management tools, and game-specific workflows directly.

Managed cloud + self-hosted on your AWS

Start with Metaplay-managed cloud hosting for fast onboarding. When ready, move to self-hosted deployment on your own AWS account with full infrastructure control via Helm charts.

Stateful actor model; ~1,000 CCU per vCPU

Player state lives in-memory as actors, eliminating database round-trips for reads. This yields high density (~1,000 CCU per vCPU) and predictable per-player resource costs.

dotnet run starts full server locally

Run the complete backend on your development machine with a single dotnet command. Debug server logic with breakpoints, test configs, and iterate without deploying to the cloud.