Use Cases
The strongest fit is single-player, idle, incremental, and async games that need save integrity across devices, production-safe environments, and a clear operator story.
Where it fits
Keep long-running progression reliable across browser refreshes, reinstall flows, and cross-device resumes without rebuilding backend save plumbing.
Best for frequent state changes that still tolerate async sync rather than real-time multiplayer state.
Ship cloud saves for premium or narrative-heavy games that need staging discipline and a production-safe way to inspect operator-facing issues.
Useful when save integrity matters more than social systems or leaderboards.
Hold the same save contract across web wrappers, native shells, and future engine SDKs instead of rebuilding save logic per client stack.
The runtime API stays stable while public SDKs expand around it.
Give operators enough visibility to trace save activity, regenerate environment keys, and follow privileged actions without exposing broad lookup to public game clients.
Built for trusted operator workflows, not for public client-side save discovery.
Non-goals
Real-time multiplayer, public player discovery, leaderboards, and event systems stay outside the current product boundary. That restraint is part of the value, not a missing slide in the pitch.
Evaluate fit