Supabase Database Connections Limit

Quick Answer

Connect through the Supavisor pooler (port 6543) instead of direct (5432)

The Limit

What is this limit?

The maximum number of simultaneous direct database connections. Free projects allow 60; Pro projects allow 200. Connection pooling (Supavisor) is strongly recommended for production apps.

Why this limit exists

Every connection consumes PostgreSQL worker processes and memory; hard caps protect instance stability on shared infrastructure and keep the pool healthy.

What happens when this limit is exceeded

• New connections fail with 'FATAL: remaining connection slots are reserved for non-replication superuser connections'
• The pooler reports that no more connections are allowed
• Serverless or edge functions that open a connection per request exhaust the pool quickly

How to check or raise this limit

1. Check Dashboard - Database - Connection pooling for the pooler URI
2. Run SELECT count(*) FROM pg_stat_activity to see live connections
3. Raise the cap by upgrading your plan (Free 60 to Pro 200)
4. Configure Supavisor transaction pooling settings in the dashboard

Code Examples

SELECT usename, state, count(*)
FROM pg_stat_activity
GROUP BY usename, state
ORDER BY count(*) DESC;

Framework-Specific Notes

DATABASE_URL="postgresql://postgres.<ref>:<password>@aws-0-<region>.pooler.supabase.com:6543/postgres"

You Might Also Like

Recommended Tools

Recommendations are editorial — DB Error Reference takes no payment or affiliate fees for tool listings.

Official Sources

This page is based on the official Supabase documentation linked below and adds practical guidance on top.

• Supabase Database connection limitsofficial