Ingestr CDC – open-source CDC replication in Go
Reads transaction logs directly to catch deletes that batch polling always misses.

Self-serve CDC when Fivetran and AWS DMS already dominate this space.
Data engineers, analytics teams, startups building data pipelines
Fivetran · AWS DMS · Debezium
The last time I posted here, people had to book a call with us in order to access Artie. Today, that’s no longer the case. You can now connect your source and destination and start streaming immediately.
I spent years of my career building large-scale data pipelines and experienced how difficult it was to get real-time data firsthand. I believed there must be a better way to stream data into our warehouse, which resulted in Artie being born. And now with AI agents, reducing data latency has become more and more crucial as agents need to make decisions off of fresh data.
When I first started building Artie, I quickly learned that the components meant to keep CDC running smoothly are very much bolted on with tons of edge cases. Unfortunately in practice, they were not built to work together. We ended up dealing with schema drift, backfill race conditions, Kafka offset commits, and TOAST columns. I’d love to know if others have hit these same issues while building in-house.
artie.com, would love feedback!
Reads transaction logs directly to catch deletes that batch polling always misses.
Query-as-pipeline is neat, but Fivetran and Airbyte already own this space.
Apache Beam as the interface beats building yet another custom SQL dialect.
True CDC for Postgres and MySQL beats polling, but lacks managed cloud offering.
Real-time GA4 pipeline with GDPR/HIPAA compliance, not another GA4 wrapper.
Common Lisp + BKNR stack is interesting, but it's a themed CRUD demo.