Key-value store on MicroSaaS.app
Per-service JSON KV over HTTPS with expiring keys. Memory floor: 64 MB (measured floor rounded up to the next multiple of 32 MB). Status: Validated
What was measured?
- At 64 MB it passed the API walk (38 of 38 checks), 704 small writes and 16 concurrent 200 KB writes and reads.Source: product test notes, probe date 2026-10-28, measured on the production microVM runtime. Method
- Crash safety: 3,535 of 3,535 acknowledged writes were present after 10 forced stops.Source: product test notes, probe date 2026-10-28, measured on the production microVM runtime. Method
| Engine | redb (Rust) |
|---|---|
| Category | Database |
| Memory floor | 64 MB |
| Status | Validated |
How long does it live?
Stateful services have a time to live of at least 1 hour, set in whole-hour steps; the default is 1 hour. The maximum depends on the plan: 4 hours on Free, 24 hours on Developer and up to 30 days on Pro. At expiry the service and its data are deleted and cannot be recovered.
What are the limits?
Crash-tested: 3,535 of 3,535 acknowledged writes survived 10 forced stops.
- One volume per service; per-customer JSON key-value API only.
A memory floor is not a sizing recommendation.
Where would it be used?
What else is in database?
Last updated