Limits

Persistly uses hard runtime limits from day one.

These limits keep the product focused, simplify capacity planning, and prevent the save-sync layer from degrading into generic blob storage.

Hard Caps

These limits are part of the public contract.

Data payload256 KB to 2 MB by plan

SlotInfo payload16 KB to 128 KB by plan

Workspace storage1 GB to 500 GB by plan

Restore history24h to 90 days by plan

Conflict modelOptimistic concurrency

Runtime authBearer runtime key

Plan Limits

Request, storage, restore-history, and payload limits scale by workspace plan.

Plan	Requests	Rate	Storage	Restore history	Payload
Free	100k/month	60 prod/min, 20 stage/min	1 GB	24h	256 KB slot data, 16 KB slotInfo
Starter	1M/month	300 prod/min, 60 stage/min	25 GB	7 days	512 KB slot data, 32 KB slotInfo
Growth	5M/month	1,200 prod/min, 120 stage/min	100 GB	30 days	1 MB slot data, 64 KB slotInfo
Pro	20M/month	3,000 prod/min, 300 stage/min	500 GB	90 days	2 MB slot data, 128 KB slotInfo

Safe Exceed Behavior

Latest saves are prioritized over restore history.

Persistly warns as workspaces approach quota, throttles repeated traffic above the plan rate, and sacrifices normal restore-history snapshots before breaking accepted latest-save updates where possible. Protected or checkpoint-style history is retained longer than normal autosave history.