compare
Estuary Flow vs ingestr
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Estuary Flow | ingestr |
|---|---|---|
| Language | Rust | Go |
| Licence | Other | Other |
| Stars | 982 | 4k |
| Latest | v0.6.13 | v1.1.63 |
| Last push | 2026-10-06 | 2026-10-06 |
| Release cadence | about 22 days between releases | about 1 day between releases |
| Active contributors | 19 commit authors on the default branch in the last 90 days | 11+ commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace Fivetran. Alternatives to Fivetran →
PartialEstuary FlowReal-time CDC and batch connectors into warehouses and other destinations.
PartialingestrCopies tables between databases and SaaS sources with one command, without a server.
Estuary Flow
- v0.6.132026-08-10control-plane-api: fix storage-mapping suffix strip to respect path-segment boundaries
- v0.6.122026-07-23docs: surface MCP and agent skills for coding agents
- v0.6.112026-07-14runtime: periodically store primary FSMHints of V2 shards
- v0.6.102026-06-15docs/redaction: document hash salting and redactSalt override
- v0.6.92026-05-21v6.0.9
Estuary Flow
unsigned The latest release, v0.6.13, carries no signature GitHub could verify.
Loading the security report
ingestr
✓ signed The latest release, v1.1.63, carries a signature GitHub verified.
Loading the security report