Supavisor alternatives
Supavisor is an open-source PostgreSQL connection pooler with a free self-hosted option. It groups many client connections onto pooled database connections and supports transaction, session, and native modes.
Key difference: alternatives range from another PostgreSQL pooler to database services and systems for routing, sharding, or replication. They suit different needs; who they suit depends on the job Supavisor handles for you.
PPgBouncer is a lightweight PostgreSQL connection poolerAPIOpenFree PgBouncer, like Supavisor, reuses PostgreSQL connections to reduce the impact of opening new ones. It offers session, transaction, and statement pooling, while Supavisor offers session, transaction, and native modes. PgBouncer lists a default memory requirement of 2 kB per connection. It is free and self-hosted, and can be a closer fit when the goal is a straightforward PostgreSQL pooler rather than Supavisor's multi-tenant and cluster features.
Trade-off: You give up Supavisor's documented multi-tenancy, management API, and cluster deployment strategies. Suits: Teams seeking a free, self-hosted PostgreSQL pooler with several pooling modes.
H
HeliosProxy routes PostgreSQL traffic and supports failoverAPIOpenFreeHeliosProxy is an open-source PostgreSQL data-plane for connection routing, failover, traffic replay, and upgrades. Like Supavisor, it offers session and transaction pooling; it also offers statement pooling and up to 100:1 connection multiplexing. Its routing includes lag-aware replicas and workload-based rules, and Transaction Replay can move sessions to a new primary under suitable conditions. Supavisor instead highlights multi-tenant pooling, metrics, and deployment strategies.
Trade-off: You give up Supavisor's documented multi-tenant support and its specific cluster deployment guidance. Suits: PostgreSQL teams that need routing and failover features alongside pooling.
TTurbineProxy pools and routes MySQL and PostgreSQL trafficAPIOpenFree TurbineProxy is a free database proxy for MySQL and PostgreSQL, while Supavisor is a PostgreSQL pooler. Both provide connection pooling. TurbineProxy also routes reads and writes based on query intent and lists security controls such as read-only enforcement and query allowlists. For MySQL 8.0 and later, it supports read-your-own-writes using GTID awareness. Supavisor instead documents tenant management, three pool modes, and a management API.
Trade-off: You give up Supavisor's documented tenant-level metrics and multi-tenant PostgreSQL setup. Suits: Teams wanting a free proxy for MySQL or PostgreSQL with automatic read/write routing.
SSPQR shards PostgreSQL databases across key rangesAPIOpenFree SPQR is a free, open-source system for scaling PostgreSQL horizontally through sharding, not a general connection pooler like Supavisor. Its router can use a query's sharding key to select a key range and shard, and it supports single-column or composite keys. Queries can also specify a key or select a shard in a SQL comment. Supavisor focuses on pooling client connections and managing tenants rather than distributing data across shards.
Trade-off: You give up Supavisor's connection pooling modes and pool-management features. Suits: PostgreSQL teams that need query routing across shards rather than connection pooling.
TFTencentDB for MySQL Database Proxy routes and pools MySQL requestsAPIOpenFree This paid proxy sits between TencentDB for MySQL and an application, providing a separate address for database requests. Like Supavisor, it includes connection pooling; unlike Supavisor, it can route reads to read-only instances and writes to the source instance. Transaction splitting can send reads and writes within a transaction to different instances. It is specific to TencentDB for MySQL, while Supavisor supports PostgreSQL and multi-tenant connections to PostgreSQL instances.
Trade-off: You give up Supavisor's free, open-source self-hosted option and PostgreSQL support. Suits: TencentDB for MySQL users who need pooling and read/write routing through one address.
AR
Amazon RDS manages relational databases in the cloudAPIOpenFreeAmazon RDS is a managed relational database service, rather than a standalone PostgreSQL connection pooler. It automates provisioning, patching, backups, and scaling, and supports PostgreSQL, MySQL, and six other listed engines. Supavisor is an open-source pooler that can be self-hosted and connects clients to PostgreSQL pools. RDS is a different choice for teams looking to have database operations managed, not simply to replace Supavisor's pooling layer.
Trade-off: You give up Supavisor's open-source, self-hosted pooling layer and its pool modes. Suits: Teams seeking a managed database service with several supported database engines.
ODOceanBase Database combines transactional, analytical, and AI workloadsAPIOpenFree OceanBase is a distributed database for transactional, analytical, and AI workloads, not a PostgreSQL connection pooler. Its built-in Oracle and MySQL compatibility is intended to simplify workload migration. Supavisor instead proxies client connections into PostgreSQL connection pools and supports multiple PostgreSQL tenants. OceanBase may fit teams considering a database platform change; it does not match Supavisor's role as a pooling layer for existing PostgreSQL instances.
Trade-off: You give up Supavisor's PostgreSQL connection pooling and multi-tenant proxy role. Suits: Teams considering a distributed database with Oracle or MySQL compatibility.
TTiCDC replicates incremental data from TiDBAPIOpenFree TiCDC captures TiKV change logs from TiDB, sorts the changes, and exports row-based data to downstream systems. It can also replicate between TiDB clusters with second-level recovery point objectives and minute-level recovery time objectives. This is data replication, not connection pooling: Supavisor handles client connections to PostgreSQL, while TiCDC moves changes from TiDB. It is relevant when the need is keeping TiDB data flowing to another system or cluster.
Trade-off: You give up Supavisor's PostgreSQL client connection pooling and tenant features. Suits: TiDB users who need incremental data replication to downstream systems or another cluster.
M
MySQL is a free, open-source relational databaseAPIOpenFreeMySQL Community Edition is a freely downloadable open-source database under the GPL license, and is available on over 20 platforms and operating systems. It is not a connection pooler like Supavisor: MySQL provides the database, while Supavisor proxies PostgreSQL client connections into pooled database connections. Consider it only when changing the database itself is part of the plan; the supplied facts do not specify usage or storage limits for its free tier.
Trade-off: You give up Supavisor's PostgreSQL pooling function and its connection-management modes. Suits: Teams choosing an open-source database for supported platforms, rather than a PostgreSQL pooler.
More near it on Database Proxy Software
- 3 AAvidemuxavidemux.sourceforge.net
Avidemux is a free video editor designed for simple cutting, filtering and encoding tasks.
- 9 P
PgDogpgdog.devPgDog is a PostgreSQL connection pooler, load balancer, and database sharder designed to scale databases without application changes.
- 10 OOdysseypg-odyssey.tech
Odyssey is an advanced, multithreaded PostgreSQL connection pooler and request router.
- 12 SP
ShardingSphere-Proxyshardingsphere.apache.orgShardingSphere-Proxy is a transparent database proxy that provides a database server using a binary protocol for heterogeneous programming languages.
- 13 Kkingshardgithub.com
kingshard is a Go-powered MySQL proxy that routes read and write SQL and aims to simplify MySQL sharding.
- 14 PPgCatgithub.com
PgCat is a PostgreSQL pooler and proxy supporting sharding, load balancing, failover and mirroring.
- 15 Ppgagroalpgagroal.github.io
pgagroal is a high-performance connection pool for PostgreSQL.
- 16 PPgDoormanozontech.github.io
PgDoorman is a multithreaded PostgreSQL connection pooler written in Rust and described as a drop-in replacement for PgBouncer and Odyssey.
- 17 PI
Pgpool-IIpgpool.netPgpool-II is middleware between PostgreSQL servers and database clients that relays PostgreSQL protocol messages transparently.
- 18 GGaeagithub.com
It supports database and table sharding, SQL routing, and read/write separation.
- 19 D
DBLEopensource.actionsky.comDBLE is high-scalability middleware for MySQL sharding.
- 21 MMycat2github.com
Mycat2 is a distributed relational database middleware that supports distributed SQL queries and the MySQL communication protocol.
Questions
Can I use Supavisor alternatives with PostgreSQL?
PgBouncer, HeliosProxy, and SPQR all cover PostgreSQL. TurbineProxy supports both PostgreSQL and MySQL. SPQR focuses on sharding rather than connection pooling.
Which alternative can route reads and writes?
TurbineProxy routes reads and writes based on query intent for MySQL and PostgreSQL. TencentDB for MySQL Database Proxy routes reads to read-only instances and writes to the source instance.
Why might someone leave Supavisor?
The project says it is not intended for serverless environments. Its setup has also been described as difficult for operators to understand, and transaction mode does not support ordinary prepared statements unless a specific option is enabled.
Are any alternatives free and self-hosted?
PgBouncer, SPQR, and HeliosProxy are listed as free or open source and support self-hosting. TurbineProxy is also free and lists self-hosted support.