Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Neon has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 4 scoped observations for Neon. The baseline covers compute max_connections, pooled concurrent clients, included monthly transfer, local file cache. 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 |
|---|---|---|---|
| compute max_connectionsSmaller computes expose lower direct PostgreSQL connection capacity. | Compute-size dependent, up to 4,000 | Per compute | NeonAug 22, 2026 |
| pooled concurrent clientsPooler clients are not the same as backend PostgreSQL sessions. | Up to 10,000 | Neon connection pooler | NeonAug 22, 2026 |
| included monthly transferNeon documents compute suspension when the free transfer allowance is exceeded. | 5 GB per month | Free | NeonAug 22, 2026 |
| local file cacheThe cache is tied to compute memory rather than persistent database storage. | 75% of compute RAM | Neon computes | NeonAug 22, 2026 |
Tracked constraints and impact
Serverless Postgres direct connections, pooler clients, transfer, and cache 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.
Neon Direct Connection Limits
Neon Direct Connection Limits, verified against Neon's official documentation with scope, implementation impact, caveats, and a direct check.
Neon Pooled Connection Limits
Neon Pooled Connection Limits, verified against Neon's official documentation with scope, implementation impact, caveats, and a direct check.
Neon Free Plan Network Transfer
Neon Free Plan Network Transfer, verified against Neon's official documentation with scope, implementation impact, caveats, and a direct check.
Neon Local File Cache Allocation
Neon Local File Cache Allocation, verified against Neon'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 Neon baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Direct connections, pooled clients, and compute cache
Free-plan included transfer and suspension behavior