peerdb
PeerDB is a PostgreSQL-focused ETL tool that replicates data from Postgres to data warehouses, message queues, and storage systems. It uses change data capture (CDC) and cursor-based replication to stream data 10x faster than comparable tools, with a Postgres-compatible SQL interface for defining and managing data pipelines.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | PeerDB-io/peerdb |
| Owner | PeerDB-io |
| Primary language | Go |
| License | AGPL-3.0 — OSI-approved |
| Stars | 3.2k |
| Forks | 198 |
| Open issues | 192 |
| Latest release | v0.36.32 (2026-06-29) |
| Last updated | 2026-07-08 |
| Source | https://github.com/PeerDB-io/peerdb |
What peerdb is
Written in Go with Rust components, PeerDB provides log-based CDC, cursor-based (timestamp/integer), and XMIN replication modes for Postgres sources. It stages data via MinIO and actively maintains ClickHouse and Postgres destinations; Snowflake, BigQuery, Kafka, and S3 destination connectors are deprecated. The system uses Temporal for fault tolerance and state management, supporting advanced Postgres types (JSONB, arrays, geospatial) and TOAST column streaming.
Get the peerdb source
Clone the repository and explore it locally.
git clone https://github.com/PeerDB-io/peerdb.gitcd peerdb# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- AGPL-3.0 license requires code modifications to be shared under the same license; review implications for proprietary deployments or forks.
- Requires PostgreSQL logical replication enabled; ensure your Postgres instance is configured with wal_level=logical and adequate replication slot settings.
- MinIO staging dependency: if ClickHouse runs outside Docker, ensure network access from both PeerDB and ClickHouse to MinIO endpoint; requires explicit configuration in docker-compose.yml.
- Deprecated destination connectors (Snowflake, BigQuery, Kafka, S3, etc.) remain functional but receive no new features or active maintenance; plan migration paths if using these.
- Temporal dependency for fault tolerance and state management; ensure Temporal cluster is sized and tuned for your replication volume and parallelism settings.
When to avoid it — and what to weigh
- Snowflake or BigQuery as destination — These destination connectors are deprecated and no longer actively maintained. Consider alternative ETL tools or pin to an older release if Snowflake/BigQuery targets are required.
- Multi-source federation across diverse databases — PeerDB is Postgres-first; while MySQL, MongoDB, and BigQuery sources are supported, optimization and feature parity is not guaranteed for non-Postgres sources.
- Fully managed SaaS with vendor support included — PeerDB is open source under AGPL-3.0; commercial support and hosting options are not detailed in provided data. Requires self-hosting or community engagement.
- Message queue destinations (Kafka, Pub/Sub, Event Hubs) — Kafka, Redpanda, Confluent, Azure Event Hubs, and Google Pub/Sub destination connectors are deprecated. These code paths remain functional but are not actively maintained.
License & commercial use
PeerDB is licensed under AGPL-3.0 (GNU Affero General Public License v3.0). This is a strong copyleft license requiring that any modifications or network-accessible derivative works must publish their source code under AGPL-3.0 or compatible license. Unmodified use and distribution of the open-source binary is permitted.
AGPL-3.0 permits commercial use of unmodified PeerDB binaries, but any modifications or SaaS deployment must be open-sourced under AGPL-3.0. No commercial license, vendor support terms, or managed hosting options are documented in the provided data. For proprietary modifications or closed-source deployment, contact the PeerDB team directly or engage legal review; otherwise, self-hosting and community support are the stated paths.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
AGPL-3.0 requires source transparency but does not guarantee security. Logical replication credentials, MinIO access keys, and destination credentials must be managed securely. Network access between PeerDB, MinIO, Postgres, and destination systems must be restricted per security policies. No security audit, CVE history, or vulnerability disclosure policy is documented in provided data. Self-hosted deployment requires standard database hardening practices (firewall, authentication, encryption).
Alternatives to consider
Airbyte
Broader connector ecosystem (300+ sources/destinations) with community and enterprise tiers. Less Postgres-specific optimization; AGPL-3.0 license with commercial cloud offering.
Fivetran
Fully managed SaaS with vendor support and SLAs. No self-hosting required. Broader enterprise connector support but higher cost and less transparency.
Debezium + Apache Kafka
Open-source CDC foundation with pluggable sinks; more modular but requires operational overhead. Kafka dependency and less turnkey for small teams.
Build on peerdb with DEV.co software developers
Review the AGPL-3.0 license terms with your legal team, assess the ClickHouse/Postgres focus against your destination requirements, and validate Temporal and MinIO dependencies in your infrastructure. Start with the 5-minute quickstart to test replication performance.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
peerdb FAQ
Can I use PeerDB with Snowflake or BigQuery as a destination?
What license restrictions apply if I modify and self-host PeerDB?
How does PeerDB achieve 10x faster performance than other tools?
Is ClickHouse the only actively maintained destination?
Software development & web development with DEV.co
Adopting peerdb is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source databases software in production.
Evaluate PeerDB for Your Postgres Data Pipeline
Review the AGPL-3.0 license terms with your legal team, assess the ClickHouse/Postgres focus against your destination requirements, and validate Temporal and MinIO dependencies in your infrastructure. Start with the 5-minute quickstart to test replication performance.