Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Render has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 5 scoped observations for Render. The baseline covers maximum build duration, pre-deploy duration, maximum HTTP response duration, free web service allowance, free database allowance. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| maximum build durationOnly one build is active for a service at a time. | 120 minutes | Build pipeline | RenderAug 22, 2026 |
| pre-deploy durationPre-deploy runs after build and before the new service version starts. | 30 minutes | Eligible services | RenderAug 22, 2026 |
| maximum HTTP response durationClient, proxy, and application timeouts can still be shorter. | Up to 100 minutes | Web services | RenderAug 22, 2026 |
| 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 |
| free database allowanceBackups and connection pooling are not included on the free database. | 1 GB; expires after 30 days with 14-day grace | Free Postgres | RenderAug 22, 2026 |
Tracked constraints and impact
Build, deploy, free-instance, response, workflow, cron, and storage limits. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
Render Build Timeout
Render Build Timeout, verified against Render's official documentation with scope, implementation impact, caveats, and a direct check.
Render Pre-Deploy Command Timeout
Render Pre-Deploy Command Timeout, verified against Render's official documentation with scope, implementation impact, caveats, and a direct check.
Render HTTP Response Duration
Render HTTP Response Duration, verified against Render's official documentation with scope, implementation impact, caveats, and a direct check.
Render Free Instance Limits
Render Free Instance Limits, verified against Render's official documentation with scope, implementation impact, caveats, and a direct check.
Render Free Postgres Limits
Render Free Postgres Limits, verified against Render's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current Render baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Build disk, build timeout, pre-deploy, and concurrency
HTTP response, workflow task, and cron duration
Spin-down, monthly hours, ephemeral filesystem, and free Postgres constraints