Introduction
Heroic Cloud is a fully managed platform for deploying and operating game backends at scale. It handles infrastructure, tooling, and observability so your studio can focus on building multiplayer and live-service games instead of managing servers.
Heroic Cloud removes the need to provision, configure, and maintain backend infrastructure yourself. It provides dedicated servers, databases, load balancers, monitoring, backups, and scaling as a managed service. Billing is usage-based, scaling is on demand, and optional SLAs and support plans are available.
Core products #
Heroic Cloud hosts three products from Heroic Labs. Together they cover the backend and LiveOps needs of a multiplayer or live-service game.
- Nakama is a dedicated game backend. Features include social login, storage, chat, multiplayer, matchmaking, leaderboards, tournaments, parties, purchase validations, and in-app notifications. Use it with Hiro to add metagame systems to your title. See Nakama deployments.
- Satori is a LiveOps platform for player engagement and retention. Features include event capture, messaging, live events, A/B testing, segmentation engine, analytics, player profiles, and integration support. See Satori deployments.
What “fully managed” means #
When you create a deployment, Heroic Cloud provisions the entire stack: DNS, load balancers with SSL/TLS, Nakama server nodes, a PostgreSQL database, and a management layer for logs, metrics, backups, and scaling. All production infrastructure runs on dedicated hardware that isn’t shared with other customers.
You own your data at all times. Heroic Labs doesn’t mine, analyze, or monetize customer data. See Privacy and compliance for details.

How resources in Heroic Cloud are organized #
- Organization is the top-level entity representing your studio. All titles, users, teams, billing, and permissions live under it. An organization can have multiple owners, and users can belong to multiple organizations.
- Title is a container for one game’s resources. All your Nakama instances, Satori instances, and builders for a single game live inside one title.
- Teams group users and assign shared permissions at the organization, title, or resource level. See Access control.
Observability and operations #
Every deployment includes built-in graphs, logs, audit trails, and data export at no additional cost. For studios running their own observability stack, paid add-ons provide continuous log shipping, Prometheus-compatible metric endpoints, and more. See Operations overview.
Who uses Heroic Cloud #
Heroic Cloud serves several roles within a game studio:
- Game developers building and deploying custom Nakama server-side logic in Go, TypeScript, or Lua using Builders.
- DevOps and infrastructure engineers managing deployments, scaling, and CI/CD pipelines.
- Producers and product managers using Satori for LiveOps, analytics, and experimentation.
- Studio leads managing teams and permissions and billing and support plans.
Larger and custom deployments #
For studios with requirements beyond the standard Heroic Cloud offering—such as dedicated infrastructure, custom network configurations, or specific compliance needs—Heroic Labs offers a Private Cloud option. Private Cloud deployments are scoped and configured in close collaboration with the Heroic Labs team.
See Private Cloud for more information, or contact sales@heroiclabs.com to discuss your requirements.
Related concepts #
- Architectural philosophy for details on the deployment stack.
- Scaling for resource tiers and costs.
- Organizations for the ownership model.
- Titles and resources for working with game titles.
