Lakehouse tables on MicroSaaS.app
DuckLake catalogue with Parquet data files. Memory floor: 128 MB (measured floor rounded up to the next multiple of 32 MB). Status: Validated
What was measured?
- At 128 MB it passed create, a 1M-row insert, aggregation, update, delete and a 700k-row spill, plus two forced-stop cycles with no data loss.Source: product test notes, probe date 2026-10-28, measured on the production microVM runtime. Method
- At 112 MB it booted but panicked on the spill query; at 104 MB it panicked on the aggregation.Source: product test notes, probe date 2026-10-28, measured on the production microVM runtime. Method
| Engine | DuckLake on DuckDB |
|---|---|
| Category | Database |
| Memory floor | 128 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?
Single writer. Below 128 MB the VM panics under larger queries.
- Single writer only.
- Arbitrary SQL can expose files and secrets unless the server is locked down.
A memory floor is not a sizing recommendation.
Where would it be used?
What else is in database?
Last updated