Local-first saves
Write local state immediately, then sync remotely when the game reaches a safe moment.
PersistlyFeatures
Reliable cloud saves need a complete save path.
Persistly combines SDKs, runtime limits, conflict-safe sync, stage/prod keys, restore history, and dashboard visibility into one focused save system.
Built around the moments where saves fail.
Local-first behavior, safe sync, and operator visibility stay connected.
Named slots
Use autosave, manual slots, checkpoints, or character names without exposing raw runtime IDs.
Explicit conflicts
Versioned cloud writes return conflict states instead of silently overwriting progress.
Stage and production
Separate test and live runtime keys are created with every dashboard project.
Auth Bridge
Use Firebase, Supabase, or Auth0 sign-in with Persistly cloud saves. Persistly verifies provider tokens and returns normal account session credentials for save sync.
Shared account data
Store account-wide settings, unlock flags, bundles, or shared inventory alongside named slots.
Usage visibility
Track requests, storage, recent saves, accounts, warnings, and billing capacity from the dashboard.
Save flow
Save locally first. Sync safely later.
Progress should survive refreshes and short offline windows before the network is ready. Persistly keeps the fast local path separate from cloud acceptance.
local cachesafe sync momentsrestore history
Runtime discipline
Bounded behavior for public game clients.
Runtime keys stay scoped to save sync. SDKs receive structured responses for conflicts, validation errors, rate limits, and retryable failures.
runtime keysstructured errorspayload limits
Authentication
Use your existing player sign-in with cloud saves.
Auth Bridge lets games keep Firebase, Supabase, or Auth0 login while Persistly verifies provider tokens and returns normal account session credentials for save sync.
FirebaseSupabaseAuth0
Operations
A dashboard for real support work.
Projects, stage/prod environments, runtime keys, usage, billing, and recent save activity stay visible without exposing player payloads.
project setupusage limitsrecent activity
Auth Bridge
Keep your player login. Add Persistly save sessions.
Firebase Auth, Supabase Auth, and Auth0 can issue player identity while Persistly handles account-backed cloud saves, slots, conflict-safe sync, and restore history.
Existing Login
Bring the identity system your game already uses.
Your game signs the player in with Firebase, Supabase, or Auth0, then exchanges that provider token for a Persistly account session.
Firebase AuthSupabase AuthAuth0
Token Boundary
Provider tokens stay out of normal save calls.
Persistly verifies the provider token once for sign-in. Save, load, and sync calls use the returned Persistly account session instead.
No client secretsAccount sessionSave sync
Release Path
Test on Stage before live players depend on it.
Free workspaces can test Auth Bridge with stage keys. Production Auth Bridge is available on paid plans for live game traffic.
Stage testingProduction plansDashboard config
SDKs
One model across JavaScript, Unity, and Godot.
Each ready SDK track exposes named slots, local-first saves, explicit sync, and conflict-aware behavior.
ReadyJavaScript SDK
First-release track for PersistlyGameSaves, named slots, local cache, autosave, and explicit conflict handling.
ReadyUnity SDKFirst-release engine track with PersistlyGameSaves, named slots, sample integration, and runtime contract alignment.
ReadyGodot SDKFirst-release engine track with addon-based PersistlyGameSaves, named slots, sample integration, and conflict states.
Start with one named save.
Validate the save path with stage keys, then move the same integration to production.