Supavisor
github.com
- Free plan
- Open source
- Linux
- API
- Self-hosted
What Supavisor is
Supavisor is an Apache-2.0-licensed, cloud-native connection pooler for PostgreSQL. A cluster can proxy millions of client connections into a stateful pool of native PostgreSQL connections. It supports multi-tenant connections across multiple PostgreSQL instances or clusters, as well as single-tenant use as a PgBouncer replacement. Pool modes include transaction, session and native. Client credentials can be checked against tenant user records or an authentication query. Supavisor describes tenant-level throughput visibility, a Prometheus metrics endpoint and a management API with OpenAPI at `/api/openapi` plus Swagger UI at `/swaggerui`. Its cluster behavior can restart tenant pools when clients reconnect after a node failure, and rolling and blue-green deployments are supported. The project is not intended for serverless environments and does not depend on Kubernetes. Installation starts with a PostgreSQL database for tenant data and includes a Docker Compose command for PostgreSQL 14. The free plan is self-hosted and open source.
Who it suits
It suits teams operating PostgreSQL deployments that need pooled client connections, including multi-tenant setups. Self-hosted deployment is available through Supabase Dashboard, CLI or MCP.
Good to know, and what to watch
- Proxies millions of client connections
- Supports multi-tenant and single-tenant modes
- Offers three pool modes
- Provides Prometheus metrics
- Supports rolling and blue-green deployments
- Not intended for serverless environments
- Supports PostgreSQL only
- Requires a PostgreSQL tenant-data database
Plans
Every plan and priceEnterprise
Free
Open-source Supavisor
Pro
Free plan
The verdict
Supavisor provides PostgreSQL pooling with multi-tenant support, observability and deployment controls. Its free, self-hosted Apache-2.0 plan is suitable for teams prepared to operate the service outside serverless environments.
What the maker publishes
- Authentication
- Client credentials can be verified using tenant user records or an authentication query. source
- Availability
- The README describes cluster behavior that can restart tenant pools when clients reconnect after a node goes down. source
- Benchmark result
- The published local benchmark recorded 189.23 transactions per second for Supavisor versus 195.96 for PgBouncer under the shown test. source
- Configuration documentation
- Environment-variable documentation lists pool settings, clustering, Phoenix API-server settings, logging and JWT-related security variables. source
- Connection-limit behavior
- Clients exceeding the configured client limit receive a PostgreSQL 'Max client connections reached' error. source
- Connection scale
- The project says a cluster can proxy millions of Postgres client connections into a stateful pool of native Postgres connections. source
- Container distribution
- A public GitHub Container Registry image is available, with linux/amd64 and linux/arm64 images shown for version 2.9.13. source
- Deployment limit
- The README says Supavisor is not intended to run in a serverless environment and does not depend on Kubernetes. source
- Deployments
- The README says Supavisor supports rolling and blue-green deployment strategies. source
- Deployment strategies
- The project documents rolling and blue-green deployment support. source
- Documentation depth
- The documentation site covers installation, setup, authentication, tenants, users, pool modes, metrics, logs, PgBouncer migration and Prisma. source
- Encryption
- Supabase states that customer data is encrypted at rest with AES-256 and in transit with TLS. source
- Founded
- 2020 source
- Funding news
- Supabase announced an $80 million Series B in May 2022, bringing reported total funding to $116 million at that time. source
- High availability
- Cluster nodes monitor tenant pools and reconnecting clients can start replacement pools after a node failure. source
- Hosted pooler role
- Supabase provides Supavisor as its shared, multi-tenant pooler and exposes transaction and session connection strings. source
- Independent technical description
- A PostgreSQL conference presentation identifies Supavisor as an Elixir-based, Apache-2.0, cloud-native pooler started at Supabase in 2023. source
- Infrastructure as code
- Pulumi and Terraform support are listed for configuring Supavisor clusters and tenant databases. source
- Installation
- The installation guide starts by setting up a PostgreSQL database for Supavisor tenant data and provides a Docker Compose command for PostgreSQL 14. source
- Licence
- The repository is distributed under the Apache-2.0 licence. source
- License and security reporting
- The repository is Apache-2.0 licensed and directs vulnerability reports to Supabase's HackerOne program. source
- Limit: pooler trade-offs
- The same independent comparison warns that poolers can add latency, complicate authentication and create more troubleshooting paths. source
- Limit: setup complexity
- A PostgreSQL conference comparison described Supavisor setup as difficult to understand from the operator's perspective. source
- Maker company size
- LinkedIn lists Supabase as a privately held company with 201–500 employees and a 2020 founding year. source
Checked against the maker's pages on 21 Oct 2026.