Snapshot
Continue to About ↓- What it does
- PgDog is self-hosted PostgreSQL middleware, packaged as a single executable, that pools connections, load-balances reads across replicas, and shards databases.
More detail
- It is designed to scale PostgreSQL horizontally without application code changes and runs via Docker, Helm, or compiled binaries.
- Best for
- Teams hitting PostgreSQL connection limits, running read replicas, or outgrowing a single primary who want pooling, read/write splitting, and sharding without rewriting their application.
More detail
- Also suited to managed-cloud Postgres users such as AWS RDS and Google Cloud SQL, since it runs outside the database.
- Pricing
- The open-source edition is free to self-host, though the license is inconsistent across sources: the homepage badge says Apache-2.0 while the GitHub listing says AGPL-3.0, so confirm before adopting.
More detail
- Enterprise terms, including support and any SLA, are available only through "Talk to us"; no public
- Main limitation
- Teams on non-PostgreSQL databases, since PgDog speaks only the PostgreSQL protocol.
More detail
- Also a poor fit for buyers who need a managed service or a published price and SLA before committing, or who need every feature to be production-stable, as the docs label some features experimental.
- Record
- Static profile
- Reviewed
- Evidence
- Public web research
- Machine access
- Structured profile ↗
About
- PgDog is self-hosted PostgreSQL middleware, packaged as a single executable, that pools connections, load-balances reads across replicas, and shards databases.
- It is designed to scale PostgreSQL horizontally without application code changes and runs via Docker, Helm, or compiled binaries.
What it helps with
- PostgreSQL's process-based connection model makes it infeasible to serve thousands of clients directly; PgDog multiplexe
- A single primary becomes a bottleneck for read traffic; PgDog splits reads to replicas and detects replication lag and f
- Databases grow past what one machine can hold; sharding spreads data across smaller servers.
- Larger databases bring vacuum lag, bloat and maintenance downtime; smaller shards make these more manageable.
- Sharding normally requires application rewrites; PgDog extracts the shard key from queries and propagates DDL so migrati
Capabilities
A practical view of what is available and where limitations apply.
| Offering | Available | Detail |
|---|---|---|
| Connection pooling | Yes | Transaction mode; the site claims 100,000+ clients over a few connections, with SET, advisory locks and LISTEN/NOTIFY preserved without pinning. |
| Load balancing | Yes | Read/write split using PostgreSQL's own SQL parser, with health checks and failover detection behind a single endpoint. |
| Sharding | Yes | Shard key taken from queries; queries without a key are spread across shards in parallel, including GROUP BY, COUNT, AVG, ORDER BY, MIN, MAX and COPY. |
| Cross-shard transactions | Yes | Two-phase commit using native PostgreSQL prepared transactions, with automatic rollback on error. |
| Integer primary keys | Yes | Monotonic big-integer keys generated in the proxy, so no switch to UUIDs is required. |
| Managed cloud service | No | Self-hosted only; no hosted offering is described. |
| Non-PostgreSQL databases | No | Speaks the PostgreSQL protocol only. |
| Production stability guarantee | Limited | Docs label some features experimental and advise testing before production; no public SLA. |
| Published enterprise pricing | Unknown | Enterprise tier advertised but price is undisclosed. |
| Independent third-party reviews | Unknown | None found in the supplied evidence; the quoted customer testimonials are first-party. |
Bot trust
How confidently AI systems can verify this profile from public evidence.
—of 100
ChatGPT—/100
Claude—/100
This profile has not completed a Bot Score assessment yet.
Evidence
Where this record came from, when it was reviewed, and how confidently it can be used.
- Verification
- Scribble researched these facts from the linked public sources.
- The owner has not manually confirmed every field.
- Last reviewed
- Primary source
- pgdog.dev
Technical profile details
Record ID
e6d67455-6a3b-4dce-b7be-00b257416dd3Canonical URLhttps://profiles.scribble.network/listing/pgdog-e6d67455