Supavisor

Free plan Open source APILinuxSelf-hosted

What Supavisor is

Supavisor is a scalable, cloud-native connection pooler for PostgreSQL. It can proxy millions of client connections into a stateful pool of native Postgres connections. The project supports multi-tenant connections across multiple Postgres instances or clusters, or single-tenant use as a PgBouncer replacement. Transaction, session, and native pool modes are available. Credentials can be checked against tenant user records or an authentication query. Tenant-level throughput visibility and a Prometheus metrics endpoint support monitoring. Management endpoints include an OpenAPI specification at `/api/openapi` and Swagger UI at `/swaggerui`. Supavisor describes restarting tenant pools when clients reconnect after a node failure and supports rolling and blue-green deployments. It is Apache-2.0 licensed and self-hosted under the free plan. Installation begins with a PostgreSQL database for tenant data and includes a Docker Compose command for PostgreSQL 14. It is not intended for serverless environments.

Who it suits

Supavisor suits teams running PostgreSQL deployments that need pooled, multi-tenant connections and operational metrics. It is designed for self-hosted or managed cluster environments rather than serverless deployments.

What it does well

Proxies millions of client connections
Supports multi-tenant and single-tenant use
Provides transaction, session, and native modes
Includes Prometheus metrics endpoint
Apache-2.0 licensed and self-hosted

What to know first

Not intended for serverless environments
Installation requires a PostgreSQL tenant database
Supports PostgreSQL rather than multiple databases

Limits

The listed free plan is self-hosted and Apache-2.0 licensed. Supavisor is not intended for serverless environments.

Plans

Plan	Billed and limits	Price
Open-source Supavisor	Apache-2.0 licensed; self-hosted deployment	Free
Free	$0 / month · Unlimited API requests · 50,000 monthly active users · 500 MB database · 5 GB egress · 1 GB file storage · 2 active projects · projects pause after 1 week inactivity	Free
Pro	From $25 / month · 100,000 monthly active users · 8 GB disk per project · 250 GB egress · 100 GB file storage · daily backups stored 7 days · 7-day log retention	$25 a month
Team	From $599 / month · SOC 2 and ISO 27001 · project-scoped and read-only access · HIPAA available as paid add-on · SSO · priority email support and SLAs · 14-day backups · 28-day logs	$599 a month
Enterprise	Custom · Technical account management · uptime SLAs · AWS PrivateLink · 24×7×365 premium support · private Slack channel · custom security questionnaires	On request

As github.com lists them, read 4 Oct 2026. The maker's own page has the final word.

Getting started

Open the Supavisor project website
Set up a PostgreSQL database for Supavisor tenant data
Use the installation guide's Docker Compose command for PostgreSQL 14
Choose a deployment route: Supabase Dashboard, CLI, or MCP

Verdict

Supavisor offers open-source PostgreSQL pooling with multiple modes, tenant management, and deployment strategies. Its self-hosted installation and non-serverless design require infrastructure management from the adopting team.

Questions

Is Supavisor free?

The listed Open-source Supavisor plan costs nothing and is self-hosted under the Apache-2.0 license.

Which database does it support?

The supported database listed is PostgreSQL.

What pool modes are available?

Supavisor supports transaction, session, and native pool modes.

Can it serve multiple tenants?

Yes. It supports multi-tenant connections to multiple Postgres instances or clusters, as well as single-tenant use.

Does it support serverless deployment?

No. The project says Supavisor is not intended to run in a serverless environment.

How can it be deployed?

Listed deployment methods are Supabase Dashboard, CLI, and MCP. The project also supports rolling and blue-green deployment strategies.

Facts from Supavisor's own pages

Authentication: Client credentials can be verified using tenant user records or an authentication query. · supabase.github.io, 4 Oct 2026
Availability: The README describes cluster behavior that can restart tenant pools when clients reconnect after a node goes down. · github.com, 4 Oct 2026
Benchmark result: The published local benchmark recorded 189.23 transactions per second for Supavisor versus 195.96 for PgBouncer under the shown test. · github.com, 21 Oct 2026
Configuration documentation: Environment-variable documentation lists pool settings, clustering, Phoenix API-server settings, logging and JWT-related security variables. · supabase.github.io, 21 Oct 2026
Connection-limit behavior: Clients exceeding the configured client limit receive a PostgreSQL 'Max client connections reached' error. · supabase.github.io, 21 Oct 2026
Connection scale: The project says a cluster can proxy millions of Postgres client connections into a stateful pool of native Postgres connections. · github.com, 4 Oct 2026
Container distribution: A public GitHub Container Registry image is available, with linux/amd64 and linux/arm64 images shown for version 2.9.13. · github.com, 21 Oct 2026
Deployment limit: The README says Supavisor is not intended to run in a serverless environment and does not depend on Kubernetes. · github.com, 4 Oct 2026
Deployments: The README says Supavisor supports rolling and blue-green deployment strategies. · github.com, 4 Oct 2026
Deployment strategies: The project documents rolling and blue-green deployment support. · github.com, 21 Oct 2026
Documentation depth: The documentation site covers installation, setup, authentication, tenants, users, pool modes, metrics, logs, PgBouncer migration and Prisma. · supabase.github.io, 21 Oct 2026
Encryption: Supabase states that customer data is encrypted at rest with AES-256 and in transit with TLS. · supabase.com, 21 Oct 2026
Founded: 2020 · github.com, 28 Sept 2026
Funding news: Supabase announced an $80 million Series B in May 2022, bringing reported total funding to $116 million at that time. · prnewswire.com, 21 Oct 2026
High availability: Cluster nodes monitor tenant pools and reconnecting clients can start replacement pools after a node failure. · github.com, 21 Oct 2026
Hosted pooler role: Supabase provides Supavisor as its shared, multi-tenant pooler and exposes transaction and session connection strings. · supabase.com, 21 Oct 2026
Independent technical description: A PostgreSQL conference presentation identifies Supavisor as an Elixir-based, Apache-2.0, cloud-native pooler started at Supabase in 2023. · postgresql.eu, 21 Oct 2026
Infrastructure as code: Pulumi and Terraform support are listed for configuring Supavisor clusters and tenant databases. · github.com, 21 Oct 2026
Installation: The installation guide starts by setting up a PostgreSQL database for Supavisor tenant data and provides a Docker Compose command for PostgreSQL 14. · supabase.github.io, 4 Oct 2026
Licence: The repository is distributed under the Apache-2.0 licence. · github.com, 21 Oct 2026
License and security reporting: The repository is Apache-2.0 licensed and directs vulnerability reports to Supabase's HackerOne program. · github.com, 4 Oct 2026
Limit: pooler trade-offs: The same independent comparison warns that poolers can add latency, complicate authentication and create more troubleshooting paths. · postgresql.eu, 21 Oct 2026
Limit: setup complexity: A PostgreSQL conference comparison described Supavisor setup as difficult to understand from the operator's perspective. · postgresql.eu, 21 Oct 2026
Maker company size: LinkedIn lists Supabase as a privately held company with 201–500 employees and a 2020 founding year. · linkedin.com, 21 Oct 2026

Where Supavisor stands on Freedom251

Database Proxy Software#4 of 31