PgDoorman vs Supavisor
PgDoorman
ozontech.github.ioSupavisor
github.comSide by side
| Figure | PgDoorman | Supavisor |
|---|---|---|
| Price from | Free | $25/mo |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 5 |
| Spec score · Database Proxy Software | 7.5 (#18) | 8.5 (#4) |
| Authentication | Documented authentication methods include MD5 or SCRAM passthrough, auth_query, PAM, JWT, Talos JWT, and pg_hba.conf access rules. | Client credentials can be verified using tenant user records or an authentication query. |
| High availability | Patroni-assisted fallback can direct new backend connections to another live cluster member when the local PostgreSQL server disappears during a switchover. | Cluster nodes monitor tenant pools and reconnecting clients can start replacement pools after a node failure. |
| What it does | PgDoorman is a multithreaded PostgreSQL connection pooler written in Rust and described as a drop-in replacement for PgBouncer and Odyssey. | Supavisor is a scalable, cloud-native connection pooler that proxies many PostgreSQL client connections into pooled database connections. |
Plans
Supavisor
- FreeFree
- Open-source SupavisorFree
- Pro$25 a month
- Team$599 a month
- EnterprisePriced on request
In their own words
PgDoorman
PgDoorman is a free, open-source, self-hosted PostgreSQL connection pooler written in Rust. It is described as a drop-in replacement for PgBouncer and Odyssey, and supports PostgreSQL 10 and newer on Linux or macOS. Listed capabilities include connection pooling, load balancing, and automatic failover; query routing is not supported. The pool coordinator enforces per-database connection caps and can reclaim idle capacity from pools with spare connections. Patroni-assisted fallback can direct new connections to another live cluster member during a switchover. Monitoring includes a Prometheus endpoint and an optional local diagnostic console for pool, latency, error, query, log, CPU, and memory information. Authentication includes MD5 or SCRAM passthrough, auth_query, PAM, JWT, Talos JWT, and pg_hba.conf rules. TLS is supported for client and backend connections. It can be built from source, installed from packages, or downloaded as a binary.