Quick answer
Render documents free web service allowance as 750 hours/month; spins down after 15 idle minutes. The filesystem is ephemeral and spin-up latency follows idle suspension.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| free web service allowanceThe filesystem is ephemeral and spin-up latency follows idle suspension. | 750 hours/month; spins down after 15 idle minutes | Free web services | RenderAug 22, 2026 |
Why does this limit matter?
An always-on expectation can exhaust monthly hours or produce cold-start delays after idle periods.
This value is scoped to Free web services; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Review monthly hours, idle traffic, startup time, and persistence requirements.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Free resources are for evaluation and have additional feature restrictions.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related