Satori vs Firebase

Firebase is a general-purpose app platform. Satori is a platform built specifically for live games.

At a very high level

Firebase also includes authentication, storage, crash reporting and a database. Satori has none of them. Nakama does, and it integrates with Satori directly.
Satori supports game-specific features that Firebase has no equivalent of: live events, event leaderboards, tournaments and economies.
Firebase isn’t just one product. Storage is Cloud Storage, Firestore is a separate Google Cloud service, and Remote Config lives in the Cloud console. Satori is one product, all-inclusive.
Remote Config is metered per fetch request. Satori’s remote configuration is unlimited on every plan. See what the pricing change means for studios.

Feature	Satori	Firebase
Remote configuration	Satori Unlimited feature flags and variants, included at any volume.	Firebase Billed per fetch request, discouraging high volume traffic.
Config schema	Satori Studio-defined schema per flag, so a flag can carry a full reward or shop configuration.	Firebase Key/value parameters and JSON strings.
Player segmentation	Satori Audiences recompute every 10 minutes by default, and membership updates on the player’s next event or property update. Segments can also be imported from your existing analytics platform and targeted directly.	Firebase Analytics audiences built from Google Analytics data, with 24–48 hour enrolment latency.
Live events	Satori First-class: calendar view, scheduling, opt-in enrolment, sticky membership, and flag overrides per event.	Firebase No concept of a live event.
Experiments	Satori Sequential phases, participant caps, admission deadlines, and mid-run enrolment locking.	Firebase A/B Testing via Remote Config. Results refresh daily.
Per-player visibility	Satori Behaviour stream per identity: events, properties, audiences, experiment enrolment, and active flags.	Firebase No view of what an individual player received.
Player messaging	Satori In-game inbox, push and email, templated and multi-language, tied to live event timing. Multi-step journeys for per-player personalization.	Firebase FCM push. No in-game inbox, no journeys.
Analytics	Satori Retention D1–D30, funnels, and RoAS by cohort and variant, filterable by experiment.	Firebase Google Analytics for Firebase.
Data export	Satori BigQuery, Snowflake and Databricks. Raw events retained.	Firebase BigQuery.
Config portability	Satori Import and export configuration, and sync between Satori instances.	Firebase Console and Admin SDK. No first-class environment sync.

Where the difference shows up

No usage limits on configuration

Firebase Remote Config is billed per fetch request. Satori includes remote configuration on every plan, at any volume.

Unlimited feature flags and variants, so running more of them does not change the bill.
A studio-defined schema per flag, so one flag carries a full reward or shop configuration rather than a key/value pair.
A flat base fee, then priced by events, the one thing you control. Nothing else is metered.

Live events are a first-class object

Firebase has no concept of a live event. In Satori, live events are scheduled, configured, and measured directly.

Calendar view, scheduling, opt-in enrolment, sticky membership, and flag overrides per event.
Event leaderboards and scheduled tournaments.
Player messaging tied to live event timing, through an in-game inbox as well as push and email.

Per-player visibility

Firebase gives you no view of what any one player got. Every Satori identity has a behaviour stream showing exactly what they received.

Captured events and current properties for that identity.
Which audiences they are in and which experiments they are enrolled in.
The flags in effect for them right now.

Different scopes, by design

Satori is not a Firebase replacement. It replaces the layer you operate a live game with, and nothing else.

What Firebase does that Satori doesn’t

Satori doesn’t try to be any of these.

Authentication
Storage and a realtime database
Crash reporting
Hosting

Where a studio needs them, Nakama covers user accounts, storage, chat, matchmaking and server-authoritative logic, and Hiro covers economies, inventories, progression, and more.

What Firebase has no answer for

No Firebase equivalent exists to compare against.

Event leaderboards and scheduled tournaments
Live event calendars and scheduling
Economy and reward tuning
Player journeys
Anything tying config changes to a game’s operational calendar

See Satori in your game

Talk to the team

Walk through live events, audiences, experiments and analytics with the engineers who build them.

Schedule a demo call