Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Supabase has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 2 scoped observations for Supabase. The baseline covers Database max connections, Connection pooler max clients. 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 |
|---|---|---|---|
| Database max connectionsSupabase labels database max connections as recommended values that can be customized; pooler client limits are separate. | 60 | Nano (Free) and Micro compute | SupabaseAug 22, 2026 |
| Connection pooler max clientsClient connections to the pooler are distinct from backend connections to PostgreSQL. | 200 | Nano (Free) and Micro compute | SupabaseAug 22, 2026 |
Tracked constraints and impact
Managed Postgres compute, direct connections, and pooler client 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.
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 Supabase baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Postgres connections and pooler clients