What exists today
Runtime API, dashboard, docs, JavaScript SDK, and playable Unity and Godot sample integrations.
Account auth readyOpen dashboard
Pricing
Start small, then pay only when your game needs more save-sync capacity.
Persistly prices each workspace by runtime save-sync capacity, project count, and request volume, not by MAU. A game with many quiet players should not pay the same as a game syncing every few seconds.
What stays narrow
Persistly is still a save-sync product first. It is not selling multiplayer systems or generic backend sprawl.
How teams scale
Operator auth, billing, SDKs, and future restore/history work sit on top of the same runtime contract.
Current SDK picture
- JavaScript SDK: Reference implementation
- Unity SDK: Playable sample included
- Godot SDK: Runtime SDK track
Free
$0
Best for prototypes, local testing, and tiny games that need real save sync behavior.
- 1 project
- 100k runtime requests/month
- 60 runtime requests/min
- Stage + prod environments
- Public docs and SDK examples
Starter
$19/mo
Best fit for shipped indie games that need disciplined save sync without extra backend work.
- 3 projects
- 1M runtime requests/month
- 300 runtime requests/min
- Stage + prod environments
- Runtime keys with test/live separation
- Dashboard billing portal
Growth
$49/mo
For games with real traction and higher sync volume across active players and devices.
- 10 projects
- 5M runtime requests/month
- 1,200 runtime requests/min
- All Starter features
- Operational guidance for active games
Pro
$149/mo
For studios and serious live games that need higher request ceilings and priority support.
- 25 projects
- 20M runtime requests/month
- 3,000 runtime requests/min
- All Growth features
- Custom onboarding path
Billing
Checkout and invoices are handled through Persistly billing so the product can stay focused on save sync.
Yearly billing gets a 20% discount compared with paying month-to-month.
Plans apply to the whole Persistly workspace/account, not to a single project.
Invoices, payment methods, and billing details are handled through the Persistly billing portal.
Tier Intent
Each plan is meant to map to a stage of operational maturity.
Teams validating cloud saves, staging discipline, and production-safe sync without wanting a general-purpose backend platform.
More request budget, stronger operator workflows, and support for games that have moved from integration to active operations.
The place for restore history, premium auth tooling, and the heavier operational controls that belong to mature live games.
Next step