
Switching our data pipelines from Fivetran to Estuary was one of the best infrastructure decisions we’ve made. It drastically lowered our monthly bill while also giving us true real-time streaming capabilities. Migrating to Estuary immediately stabilized our spend with a far more predictable, volume-based model.
Moving away from delayed batch syncs to continuous, low-latency streaming completely upgraded our data freshness, letting operational data flow virtually instantly. Estuary also gives us the flexibility to customize schemas and handle in-flight transformations directly within the pipeline, which has helped us save on downstream compute costs.
While the initial setup and schema mapping required deliberate effort, day-to-day management has been remarkably smooth and genuinely “set-and-forget.” Ultimately, Estuary delivered the blend of real-time performance, developer control, and budget relief we needed as we scaled. Review collected by and hosted on G2.com.
What I don’t like about Estuary is the UI. At times it isn’t very intuitive. For instance, when I’m backfilling records, the progress details aren’t very clear and are mostly shown as a percentage, which doesn’t always help me understand what’s actually happening. The logs are also pretty noisy and hard to follow, especially when I’m troubleshooting. Since I’ve had to work through capture failures, binlog position changes, and backfills during our migration, clearer progress indicators and more structured, easier-to-scan logs would make the overall experience much better. Review collected by and hosted on G2.com.