Container registry on MicroSaaS.app
Disposable OCI registry. Memory floor: 96 MB (measured floor rounded up to the next multiple of 32 MB). Status: Validated
What was measured?
- Three consecutive rounds at 88 MB each pushed and pulled a small image and a 50 MB layered image, ran four concurrent pulls and garbage collection, and kept all data across three forced stops; 80 MB kernel-panicked during the 50 MB push and 64 MB at boot.Source: product test notes, probe date 2026-10-28, measured on the production microVM runtime. Method
| Engine | Zot |
|---|---|
| Category | Tooling |
| Memory floor | 96 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?
Pushes and pulls of images, including a 50 MB layer.
- Needs the glibc loader in the image because the Zot binary is dynamic.
- The gateway answers 502 or 503 for a few seconds after a restart.
A memory floor is not a sizing recommendation.
Where would it be used?
What else is in tooling?
Last updated