Compare
Filament vs Airbyte
Side-by-side capabilities and benchmarks.
ROWS PER SECOND
90.5× wall
90.5× faster
NYC Taxi, Postgres -> Postgres
WALL TIME
90.5× higher
32.3× FASTER
TPC-H, Postgres -> Postgres
CPU SECONDS
377
36.3× less
NYC Taxi, Postgres -> Postgres
PEAK MEMORY
2.97 GiB
4.3× less
NYC Taxi, Postgres -> Postgres
Airbyte is a data integration platform. It is known for a large catalog of connectors, most of them built and maintained by its community. It is source-available and runs on Kubernetes or as a hosted service. Filament is an open-source replication engine that moves data into the systems you already run, verifies every batch it writes, and resumes where it left off when a run fails.
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. Airbyte's Taxi figures come from one run of 2 h 53 m. Everything else on this page is a median of three. Filament standalone image, 32 parallel readers, 25,000-row batches. Airbyte source-postgres 3.8.1 and destination-postgres 3.0.13 as open-source containers with 16 GiB limits, full refresh overwrite, typing and deduplication on. 75% of Airbyte's CPU on the Taxi load was spent in the destination container on typing and deduplication.
Move data with Filament