Supabase
Postgres can be healthy while Supavisor is on fire
Most Supabase incidents are pooler incidents. DBExplore scans both ports, tracks plan ceilings, and treats the pooler as the front door it is.
What goes wrong
Too many connections, wrong port
The direct-connection ceiling is far tighter than the pooled one. Most connection incidents hit the direct limit while the pooled one sits idle.
Transaction-mode surprises
Transaction pooling breaks prepared statements, and the API path's statement timeout fails queries that would succeed on a direct connection.
Paused projects, aging XIDs
Free-tier auto-pause leaves transaction ID age advancing with no operator in the loop.
What DBExplore does about it
Pooler telemetry
Wait time, server connections, active and waiting clients, and fragmentation next to per-plan ceilings.
Dual-port awareness
Direct and pooled connections tracked separately so you know which ceiling you are about to hit.
Realtime and storage
Realtime concurrency and backpressure, storage egress, and replica lag on multi-node projects.
Supabase-specific detection rules
Pooler saturation, plan-limit proximity, and wraparound risk, with project keys masked in every captured query.
Supabase: questions we get first
Which versions?
Every PostgreSQL major version Supabase currently offers, matching what is pinned at project creation.
Do you need the service role key?
No. A read-only monitoring role is enough. Project keys found in query text are masked before capture.
What leaves the database?
Metrics, catalog metadata, execution plans, and query text with literals scrubbed on the agent before it is sent. Parameter capture is off by default. Row data never leaves.
Can DBExplore change anything without approval?
Not by default. Every tenant starts at approve. Disruptive actions always need two approvers, and every mutating action passes a fail-closed policy gate first.
Run DBExplore on your Supabase.
We onboard teams in small batches. Tell us about your fleet and we will reach out when a seat opens. One email, no drip campaign.