PgCat vs Supavisor
PgCat
github.comSupavisor
github.comSide by side
| Figure | PgCat | Supavisor |
|---|---|---|
| Price from | Free | $25/mo |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 5 |
| Spec score · Database Proxy Software | 7.6 (#15) | 8.5 (#4) |
| Authentication | MD5 auth passthrough can use auth_query so cleartext passwords are not required in the configuration file. | Client credentials can be verified using tenant user records or an authentication query. |
| Purpose | PgCat is a PostgreSQL pooler and proxy supporting sharding, load balancing, failover and mirroring. | Supavisor is a scalable, cloud-native Postgres connection pooler. |
Plans
Supavisor
- FreeFree
- Open-source SupavisorFree
- Pro$25 a month
- Team$599 a month
- EnterprisePriced on request
In their own words
PgCat
PgCat is a free, open-source PostgreSQL pooler and proxy for self-hosted Linux deployments. Its stable features include transaction and session pooling. Read queries can be balanced across replicas and the primary, while health checks detect broken replicas and redirect queries to remaining servers. PgCat uses Tokio’s asynchronous runtime and a multithreaded design for multicore machines. Operators can view pooler statistics through the pgcat and pgbouncer admin databases or a Prometheus HTTP endpoint. Client and PostgreSQL server connections can use SSL/TLS, with MD5 and SCRAM-SHA-256 authentication supported. MD5 passthrough can use auth_query so cleartext passwords need not be stored in the configuration file. Docker deployment is documented, and a container image is published. Sharding syntax, comment parsing, automatic sharding, and mirroring are experimental. Transaction mode is enabled by default and does not support prepared statements, SET, or advisory locks. The project describes PgCat as stable and says it serves high query volumes in production. It is licensed under MIT.