Satori deployments

LiveOps changes (player events, experiments, segments, and messages) shouldn’t require a code deploy and a release cycle. Satori is a managed LiveOps platform where everything is configured through the console, so producers and product managers can iterate on engagement strategies independently of your engineering team.

Unlike Nakama, you don’t manage infrastructure tiers or trigger deploys. Heroic Labs handles scaling, availability, and updates.

Creating a deployment #

When creating a Satori deployment, you choose:

  1. Deployment type as either development or production. This can’t be changed later.
  2. Deployment zone for the region (for example, US East). Choose a zone close to your players.
  3. Instance name as a unique name (may contain dashes, for example mygame-satori-prod). This can’t be changed after creation, as it forms part of the internal naming scheme of the dedicated deployment stack, including DNS records.

Development vs. production #

Development instances are intended for testing and prototyping. Don’t use a development instance to evaluate Satori’s performance under load or run pre-launch validation.

Production instances are built for live player traffic:

  • Managed scaling. Heroic Labs monitors and adjusts resources based on player activity. You don’t need to anticipate traffic spikes.
  • High availability and resilience. Both Satori and its database run in HA mode. Built for continuous uptime with redundancy.
  • Data backup. Production data is backed up in real-time and retained for 30 days. Development instances have daily backups retained for 7 days with no real-time backup.
  • SLA. Production deployments are covered by a standard SLA. An enhanced SLA with stronger uptime guarantees is also available.
  • Optimization for live operations. Faster background processing and tuning designed for LiveOps workloads at scale.
Standard and enhanced SLA options are available for production deployments. Contact sales@heroiclabs.com for details.

Configuration and management #

All Satori configuration (events, experiments, segments, messages) is managed through the Satori console, not the Heroic Cloud dashboard. This is by design: LiveOps changes should be fast and independent of your engineering release cycle.

The Heroic Cloud dashboard manages the deployment itself (creation, scaling, permissions, audit). The Satori console manages the LiveOps content running on that deployment.

Connecting your game client #

Each deployment gets a unique hostname in the format {instance-name}.{zone}.heroiclabs.com on port 443 (TLS encrypted). You also get an authentication key:

  • API key is used by game clients and server-side services to authenticate with Satori. Anyone with this key can send events and read LiveOps configuration on behalf of a player. Treat it as a shared secret. You can create multiple keys under Settings > API Keys in the Satori console, for example one per SDK or event source, so you can revoke a compromised key without affecting other integrations.

The API key is a sensitive credential. Leaking it means anyone can send events to your deployment or read its LiveOps configuration. For this reason, access to it is gated behind the Secrets permission. Only users and service users with this permission can view or copy it. See Access control.

SDK code snippets are available for Unity, JavaScript, Godot, Java, Dart, and Swift. For full client SDK guides, API references, and connection examples, see the Satori documentation.

Audit #

Actions performed on the Satori deployment (creation, updates, deletion) are logged in the organization-level audit log under the Satori Deployment category. See Audit log.

Billing #

Satori usage is measured across three dimensions: player count, events, and datalake storage. Each is measured at intervals throughout the day, with the highest value recorded during a given day used to calculate that day’s charge. Daily usage accumulates and is invoiced at the end of the month. See Billing for billing details.

See also #