PgDoorman
5.9#14 in database proxy softwareFree planFree planLinuxmacOSSelf-hosted
Visit| Fact | PgDoorman | Supavisor |
|---|---|---|
| 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. |
PgDoorman suits teams that operate PostgreSQL themselves and need connection pooling, load balancing, or automatic failover. Its Linux or macOS and PostgreSQL version requirements matter when assessing a deployment.
Supavisor suits teams operating PostgreSQL that need connection pooling across tenants or a single-tenant PgBouncer replacement. It is aimed at self-hosted deployments rather than serverless environments.