HeliosProxy vs PgDog
HeliosProxy
heliosdb.comPgDog
pgdog.devSide by side
| Figure | HeliosProxy | PgDog |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 2 |
| Spec score · Database Proxy Software | 7.8 (#8) | 7.7 (#12) |
| Deployment | The maker documents Docker, Kubernetes, and standalone deployment options. | PgDog can be deployed with Kubernetes Helm, Docker, AWS ECS Terraform, pre-built binaries, or from source. |
| Integrations | It works with PostgreSQL 12+ and PostgreSQL-compatible backends including Amazon RDS, Aurora, Cloud SQL, Azure Database, CockroachDB, YugabyteDB, TimescaleDB, Citus, and AlloyDB. | The enterprise insights page lists Prometheus and OTEL exporters, plus Incident.io integration for alerts. |
| License | HeliosProxy is open source under the Apache 2.0 license. | The project is free and open source under AGPL-3.0, and the documentation says internal use does not require sharing source code. |
| Security | The proxy supports JWT, OAuth 2.0, LDAP, and API-key authentication, with identity claim-to-database-role mapping. | The enterprise control plane page describes SSO for access protection, while installation documentation says user credentials can be encrypted at rest in supported environments such as Kubernetes or AWS Secrets Manager. |
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.
PgDog
PgDog is a PostgreSQL connection pooler, load balancer, and database sharder designed to scale databases without application changes. It multiplexes many application connections across fewer PostgreSQL server connections and supports SET, LISTEN/NOTIFY, and advisory locks. Read queries can be distributed across replicas while writes go to the primary, with health checks and failover detection. Sharding keys guide query routing; queries without a key can run across databases in parallel. Cross-shard transactions use PostgreSQL prepared transactions and two-phase commit, with automatic rollback on errors. PgDog can copy data and stream row changes to another database without pausing query traffic. Deployment options include Kubernetes Helm, Docker, AWS ECS Terraform, pre-built binaries, and source. Releases include Linux arm64 and amd64, Apple Silicon Mac, and Debian packages; the macOS binary is unsigned. The project is free and open source under AGPL-3.0, and documentation says internal use does not require sharing source code. Enterprise support includes architecture reviews, a dedicated Slack channel, and an SLA promising a response within 15 minutes.