Estuary

What do you like best about the product?

Low-maintenance, solid availability for syncing data from disparate data sources.

What do you dislike about the product?

Some limited observability - would be nice to see more detailed logs, and have more insight/direct queryability into the individual data collections. Also the BYOC model is a bit annoying, would be nice to be able to use our existing cloud VPC.

What problems is the product solving and how is that benefiting you?

Our company has a LOT of different data stored in very different places, so this is helping us get it all into one.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

Estuary has been highly effective in supporting our cost-reduction strategy while still delivering a robust, reliable, high-quality data ingestion service. Migrating from Fivetran to Estuary helped us significantly reduce our data pipeline costs without sacrificing reliability or performance.

Data ingestion and loading have been largely seamless, and the platform has handled our production workloads well. We’ve also found the Slack support team responsive and helpful, especially when troubleshooting issues related to captures, backfills, binlog positions, and migrations. The AI-powered support through Kapa.ai has been useful as well, letting us quickly find answers and navigate the documentation.

Overall, Estuary strikes a strong balance between cost efficiency, reliability, performance, and developer support, and it has become a valuable part of our modern data stack.

What do you like best about the product?

I like how Estuary is a key element within our data stack, making data ingestion from all of our Postgres data sources and Salesforce reliable. It's easy to use, and I appreciate the strong communication when something is broken. Their support is very quick to help us, and it's nice knowing there's a part of our stack we don't have to worry about. Estuary just works, allowing us to focus on other high-priority tasks. I also found the initial setup of Estuary to be very easy. Support is readily available if we have questions, which is really helpful. The reliability of Estuary makes everything a lot easier.

What do you dislike about the product?

Sometimes I find it hard when we want to add a new data source or a connector because it's like $200 per connector, which has made us purposely not use Estuary at times. I wish there was a way to onboard a source with pricing charged per active row instead, so we could use it without having to think about the cost.

What problems is the product solving and how is that benefiting you?

Estuary reliably ingests data from Postgres and Salesforce, simplifying our workflow. Its ease of use and strong support mean we focus on priorities without worry. It's a key part of our data stack, making us trust that it just works, saving time and effort.

What do you like best about the product?

Support actually has been more than outstanding, many hours spent talking with the estuary guys.

What do you dislike about the product?

As noted in the review no issues since that first outage

What problems is the product solving and how is that benefiting you?

Easy deata ingestion

What do you like best about the product?

The reliability of the platform and the responsiveness of support.

What do you dislike about the product?

Creating templates for transformations. I would prefer an easier and quicker GUI based approach.

What problems is the product solving and how is that benefiting you?

We are moving real time data from Azure SQL to Snowflake. This has avoided us having to either find an open source solution or creating our own and maintaining it due to costs.

What do you like best about the product?

The speed of implementation. It takes a matter of minutes to set up a pipeline from source to destination. The also have great customer support on Slack.

What do you dislike about the product?

Missing Timescale as a source. Ideally would be able to modify a connector to not be on 24/7 for cases where daily data extracts are required.

What problems is the product solving and how is that benefiting you?

Allows us to consolidate our various data sources into a single data warehouse, thereby enabling business analytics.

What do you like best about the product?

For streaming/CDC sources, estuary is a no brainer. Very easy to implement and monitor usage. Costs are reasonable and predictable

What do you dislike about the product?

The UI can be a little challenging sometimes, but they are quick to make changes based on feedback.

What problems is the product solving and how is that benefiting you?

Estuary makes it easy to quickly ingest data sources

What do you like best about the product?

Estuary eliminates the need to stand up and maintain costly infrastructure, like kafka topics and data pipelines. It's replication from any source to cloud data warehouses made simple and very cost effective.

Implementation and integration is also dead easy!

Lastly, their customer support teams are very responsive and resolve issues immediately.

What do you dislike about the product?

The UI needs a little polishing but that will come with time. It's lacking in data observability and pipeline observability features, but those are also coming and luckily the service is very reliable.

What problems is the product solving and how is that benefiting you?

We are using snowflake to serve customer facing analytics and needed up-to-date data from our main product database which resides in AWS aurora. Since we're a small startup, we didn't have the time and resources to dedicate to costly middleware infrastructure builds and maintenance, like kafka topics and data pipelines that consume from them. We tried using Airbyte and experienced very poor performance and failures with binlogs.

Fivetran is way too expensive given the size and frequency of our data loads.

Estuary is a perfect solution and provides near real time data replication at the right price.

What do you like best about the product?

For initial and basic setup, Estuary offers a fast and cost-effective way to integrate major data sources. I was able to connect my MongoDB to Snowflake for analytics purposes within just a few hours, which is something I haven't seen any other tool accomplish. I switched from Fivetran to Estuary to achieve lower latency and to significantly reduce my expenses for both Fivetran and Snowflake.

After more than a year, I am using more data sources and destinations on daily basis. In this period, error messages in the UI have become more helpful (yet still are not perfect) when debugging connections to a new data source.

The founder, David, is very hands-on and has been extremely helpful, taking the time to explain configuration quirks and respond to feature requests on several occasions. The Slack channel serves as the main and efficient way to get support.

What do you dislike about the product?

Setting up the tool does demand a certain amount of data engineering work. While this is likely true for any platform aimed at achieving a solid level of data governance, I found the process of de-nesting JSON using slashes in variable names, as well as removing or renaming variables via the CLI, to be conceptually challenging-especially during my migration from Fivetran.

What problems is the product solving and how is that benefiting you?

Lowering data replication latency and warehousing costs in Snowflake without need to write any connectors at my core application level.

What do you like best about the product?

Easy to setup. Pricing for starter not scary like Fivetran. Great support in slack.

What do you dislike about the product?

- Hope their can be more connectors. Like databricks to postgres
- Backfill is a bit slow (take 3-4 days to backfill a 500GiB table)

What problems is the product solving and how is that benefiting you?

Data replication from live database to analytic/data warehouse