Estuary
Estuary reviewed: change data capture and batch pipelines in one platform, 200+ connectors, per-GB pricing as of October 2026, and when it beats batch ELT.
Data integration platform that combines real-time change data capture (CDC) streaming with batch pipelines.
Best for
Data teams that need database changes in a warehouse or downstream system within seconds, not hours.
Not great for
App-to-app business workflows, or teams whose only need is a nightly batch sync.
Verdict
A strong option when freshness matters and you want CDC without running Kafka. Pricing is transparent and usage-based.
Pros
- + Real-time CDC with low impact on production databases
- + Published, usage-based pricing
- + Free developer tier
Cons
- − Smaller connector catalog than the largest ELT vendors
- − Requires data-engineering knowledge
- − Not built for business process automation
Key features
- • Change data capture from databases (inserts, updates, deletes)
- • Streaming and scheduled batch movement in one pipeline
- • 200+ source and destination connectors
- • Transformations on data in flight
- • Private and BYOC deployments on Enterprise
What is Estuary?
Estuary is a data integration platform that moves data from sources (databases, SaaS apps, event streams) to destinations (warehouses, lakes, operational databases) either in real time or on a schedule. Its distinguishing feature is change data capture (CDC): instead of re-querying tables, it reads database logs and streams inserts, updates and deletes as they happen. The platform is built on Estuary’s source-available Flow project.
How Estuary works
- Capture: a source connector reads data. For databases this is CDC from the transaction log, which keeps load on production systems low.
- Collections: captured data lands in collections that act as durable, replayable streams.
- Derivations (optional): transformations reshape or join data while it moves.
- Materialize: destination connectors write the data continuously or on a schedule into Snowflake, BigQuery, Databricks, Postgres and others.
The practical benefit is one tool for both streaming and batch, so you do not need a separate Kafka-plus-Debezium setup for real-time and a batch ELT tool for everything else.
Estuary pricing
As of October 2026:
- Developer: free for up to 10 GB/month and 2 concurrent connector instances.
- Cloud: $0.50 per GB moved plus a monthly fee per connector instance ($100/month each for the first six, $50/month for additional ones, per Estuary’s FAQ).
- Enterprise: custom; volume discounts, SSO, SOC 2 and HIPAA reports, custom SLAs, private or BYOC deployment.
Check estuary.dev/pricing for current terms; usage-based pricing makes it worth estimating your monthly GB before choosing.
Who Estuary is for (and not for)
Good fit: data teams powering real-time analytics, operational dashboards, search indexes or AI features that go stale with hourly batch loads.
Poor fit: ops teams automating actions between apps (create a task, post to Slack, update a CRM record). That is workflow automation, not data replication.
Estuary alternatives
- Fivetran and Airbyte for batch-first ELT; see Airbyte vs Fivetran.
- Kafka Connect if you already run Kafka.
- Stitch for simple, low-cost batch ingestion.
How Estuary compares to Automatite
Estuary replicates data; Automatite runs business processes. Automatite workflows react to triggers and webhooks, apply data mapping and take actions in apps. A common pattern is to use both: a pipeline tool like Estuary to keep the warehouse fresh, and a workflow tool to act on specific events.
FAQ
What does Estuary do?
It moves data between systems in real time with change data capture, or on a schedule, through 200+ connectors.
Is Estuary free?
There is a free developer tier up to 10 GB/month and two connector instances. Larger usage is billed per GB and per connector.
Is Estuary open source?
Its core Flow project is source-available on GitHub under the Business Source License; the managed platform is commercial.