Compare
Filament vs PeerDB
Side-by-side capabilities and benchmarks.
WALL TIME
114.8 s
3.6× faster
NYC Taxi, Postgres → Postgres
WALL TIME
3.79 s
4.8× faster
TPC-H, Postgres -> Postgres
CPU SECONDS
377.4
8.7× LESS
NYC Taxi, Postgres -> Postgres
CPU SECONDS
17.9
8.1× LESS
TPC-H, Postgres -> Postgres
PeerDB is a change data capture tool built for Postgres. It replicates from Postgres, mainly into ClickHouse, and it is now owned by ClickHouse with a hosted version inside ClickHouse Cloud. Filament is an open-source replication engine that replicates from Postgres and MySQL into Postgres, MySQL, ClickHouse, Iceberg, and S3, and is not tied to one destination.
Verified benchmark comparison
Why Filament
Apache 2.0, open source
Self-hosted in full
Yes. One repository, no paid tier, nothing gated
Adding a new source
A YAML manifest for REST APIs, loaded at runtime with no rebuild. A Go driver for databases and other driver-based sources
Methodology
Configuration as run. Filament standalone image, 32 parallel readers, 25,000-row batches. PeerDB stable-v0.37.0 as its seven-container service stack, 32 snapshot workers, 750,000 rows per partition, 2 tables in parallel. PeerDB's largest container peaked at 0.74 GiB. Summed across all seven containers it peaked at 1.20 GiB, still below Filament's single container. 99% of PeerDB's CPU sat in the flow worker.
Move data with Filament