HeliosProxy vs PgDoorman
HeliosProxy
heliosdb.comPgDoorman
ozontech.github.ioSide by side
| Figure | HeliosProxy | PgDoorman |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Database Proxy Software | 7.8 (#8) | 7.5 (#18) |
| Deployment | The maker documents Docker, Kubernetes, and standalone deployment options. | PgDoorman can be built from source, installed from distribution packages, or downloaded as a prebuilt binary; Docker is intended for development, CI, and demos rather than production. |
Plans
In their own words
HeliosProxy
HeliosProxy is a self-hosted, programmable PostgreSQL data-plane for routing connections, handling failover, replaying traffic, and supporting database upgrades. It provides session, transaction, and statement pooling, with multiplexing up to 100:1. Routing can account for replica lag, workload type, and failing backends through circuit breaking. Cache options include local memory, Redis-backed storage, and semantic tiers, with invalidation when writes occur. Transaction Replay can move sessions to a new primary and optionally replay reads or transactions when conditions permit, although prepared statements, temporary tables, open cursors, advisory locks, and extended-protocol SET statements are not restored. A WebAssembly plugin runtime offers five hook points, Ed25519 verification, and OCI distribution. The admin console includes topology, plugin, chaos, shadow-execution, and traffic-replay panels. Authentication supports JWT, OAuth 2.0, LDAP, and API keys. HeliosProxy works with PostgreSQL 12+ and compatible databases, and deployment documentation covers Docker, Kubernetes, and standalone setups. It is open source under Apache 2.0 and costs nothing.
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.