Compare
Filament vs ingestr
Side-by-side capabilities and benchmarks.
ROWS PER SECOND
114.8 s
5.3× faster
NYC Taxi, Postgres -> Postgres
WALL TIME
2,597,498
4.6X FASTER
TPC-H, Postgres -> Postgres
PEAK MEMORY
3.79 s
1.6X LESS
NYC Taxi, Postgres -> Postgres
CPU SECONDS
2,288,144
2.4X MORE
NYC Taxi, Postgres -> Postgres
ingestr is a command line tool for copying data from one system to another in a single command. It is simple to pick up and useful for one-off moves. Orchestration, scheduling, and monitoring are left to whatever you run around it. Filament is an open-source replication engine with a CLI for one-off transfers and a service for everything else, with scheduling, checkpoints, and verified writes built in.
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. ingestr latest image (the 2026 Go rewrite), one ingestr ingest process per table with the pyarrow SQL backend flag, 100,000-row pages, partitioned extraction, and a 32-worker budget. ingestr spent less CPU because it averaged under a third of one core for the whole run. It never engaged the parallelism it was given.
Move data with Filament