Hevo Pipeline

What differentiates Hevo Pipeline from other similar products?

Easy to use, great CSM and support teams, adds new features and improvements very frequently, API tools for unsupported sources, dbt integration

What is your favorite aspect of this product?

Changed my daily ETL checks with long hours of troubleshooting issues on the previous tool to automated messages that require a few clicks to resolve, if there are issues at all, as most of the time it is smooth sailing, freeing up my time for more impactful work

What do you dislike most about this product?

Some of the supported data sources are not quite there yet and it is not clear which source connectors are robust and proven implementations and which are in early stages or are still missing some features, causing frustration when we try to implement them.

What recommendations would you give to someone considering this product?

Try it out as it is super easy to implement and you can have the trial running in a few hours. It works best paired with a cloud database that enables ELT practices rather than traditional ETL. If you are after a specific feature or connector offered by the tool, double check with them first if that feature/connector is mature and has no known issues.

What differentiates Hevo Pipeline from other similar products?

Data source connectivity Deploy seamlessly

What is your favorite aspect of this product?

No code funcatinality

What do you dislike most about this product?

Schedulling

What recommendations would you give to someone considering this product?

This os one of the top used product with high level user experiance. Very good product to use for data transformation

What differentiates Hevo Pipeline from other similar products?

It's highly simple to implement. We first tried working with AWS DMS and Glue, and also looked at Matillion and several other products. What set Hevo apart was how vastly simple it was to set up and get going. It provides helpful documentation all the way on how to set up, say, change tracking, or log-based replication, or whatever it might be for the type of database you choose. You can effortlessly select a source, select a destination, choose a bunch of objects and off you go. It simply works as if by magic. It's also significantly lower cost than the alternatives, many of which have a license fee and hosting costs.

What is your favorite aspect of this product?

The absolute simplicity to set it up and get going. You can have pipelines operational within minutes of signing up for Hevo. It directs you easily through the process.

What do you dislike most about this product?

It has a scalability limit. Despite the costs being measured in events per month, and despite the pipelines being able to be set at any frequency from five minutes and above, the reality is the product hits a ceiling and then all scheduling is unpredictable. Partly this is because a Hevo pipeline is the combination of database server, database, and schema, so if your database has multiple schemas you end up with multiple pipelines, and it turns out Hevo can only handle so many concurrent pipelines from the same sources. Push it too far and it will become wildly non-performant and certainly unable to keep pace with the schedule you set.

What recommendations would you give to someone considering this product?

If you have a large number of sources check with Hevo how well they can confirm they can handle it at the frequency you want. Also, review the API docs. You can't act on pipelines in bulk in the GUI so you need to script it against the API - but the API is also not fully feature-equivalent with the GUI. Yes, in the age of micro-services and API-driven design, the GUI offers capabilities the API does not. Hevo is catching up on these though. One example was setting a pipeline to not automatically ingest new objects that might be added; it took a while for this to come to the API too.