Review the dependency graph before enabling idle pause

By the Lizard team · October 15, 2026

Lizard (lizard.build) announced automatic idle pause and request-triggered resume for deployed apps and databases on October 15. After no requests for a configurable period—10 minutes by default—the whole project pauses in its current state: frontend, backend, Managed Postgres and Managed Redis. The next request triggers resume. The announced typical range is 0.5–1 second; it is not an SLA or a guarantee of total response time.

Active compute is billed while the project runs. The announcement says paused projects pay only for storage; retained data therefore still matters to cost. This describes resource usage, not a promise of a zero total bill. Current account terms remain relevant.

Dependency map

Draw the path from frontend to backend to Managed Postgres, then add Managed Redis if it holds cache or queue data. The announcement describes these components pausing together. That makes the project boundary worth reviewing.

1. Identify every dependency inside and outside the project.
2. Ask how readiness is established when components resume.
3. Review database connection-pool recovery and request deadlines without assuming existing connections survive.

Next step: complete this review for one existing project and resolve unknowns before changing its settings. No workload tests were performed for this article.

October 15 announcement · Relevant documentation · Current usage billing

Explore Lizard