Try our new research platform with insights from 80,000+ expert users

Stitch vs StreamSets comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Stitch
Average Rating
6.8
Reviews Sentiment
5.5
Number of Reviews
5
Ranking in other categories
Cloud Data Integration (25th)
StreamSets
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
Data Integration (22nd)
 

Featured Reviews

reviewer2783532 - PeerSpot reviewer
Cloud Data Architect at a comms service provider with 10,001+ employees
Improved data management has reduced errors while consistent loads have saved weekly effort
I think the best feature Stitch offers is that it handles deleted records. Stitch's ability to handle deleted records is a standout feature for me because if a record is deleted at the source, I can easily track it with soft delete and all that functionality. Stitch has impacted my organization positively, as I have both positive and negative aspects with it. One positive aspect is that full loads are free, so whenever I see data issues, I can go for full loads. At the same time, I need to look at the limitations, such as API limits. Stitch has helped my organization achieve better data management, making it easier. Better data management means that Stitch helps my team access data faster and reduces errors.
SS
Enterprise Solutions Architect at a energy/utilities company with 1,001-5,000 employees
Enables effective batch loading with visual interface and enterprise support
One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infrastructure. I had to switch to a new EC2 box, even though the processor was not fully utilized. It would be beneficial if StreamSets addressed any potential memory leak issues to prevent unnecessary upgrades. Additionally, it would be a great enhancement if StreamSets could produce a lineage graph to visualize how the data has passed through the system.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Stitch has positively impacted my organization by allowing us to create MVPs quickly."
"Stitch helps immensely because in just a day, we are able to cover the work that would normally take two to three weeks worth of design work nonstop."
"Stitch has helped my organization achieve better data management, making it easier, as it helps my team access data faster and reduces errors."
"The setup process for Stitch was pretty easy, with a plug and play approach where the data is immediately available."
"The most valuable feature of Stitch for us is ease of use. This solution is fire-and-forget. All an organization has to do is set up the connection or integration and move on."
"The Ease of configuration for pipes is amazing. It has a lot of connectors. Mainly, we can do everything with the data in the pipe. I really like the graphical interface too"
"Also, the intuitive canvas for designing all the streams in the pipeline, along with the simplicity of the entire product are very big pluses for me. The software is very simple and straightforward. That is something that is needed right now."
"The ability to have a good bifurcation rate and fewer mistakes is valuable."
"In StreamSets, everything is in one place."
"The entire user interface is very simple and the simplicity of creating pipelines is something that I like very much about it. The design experience is very smooth."
"The scheduling within the data engineering pipeline is very much appreciated, and it has a wide range of connectors for connecting to any data sources like SQL Server, AWS, Azure, etc. We have used it with Kafka, Hadoop, and Azure Data Factory Datasets. Connecting to these systems with StreamSets is very easy."
"I really appreciate the numerous ready connectors available on both the source and target sides, the support for various media file formats, and the ease of configuring and managing pipelines centrally."
"The ETL capabilities are very useful for us. We extract and transform data from multiple data sources, into a single, consistent data store, and then we put it in our systems. We typically use it to connect our Apache Kafka with data lakes. That process is smooth and saves us a lot of time in our production systems."
 

Cons

"The customer support of Stitch is horrible."
"The designs that Stitch produces sometimes cannot really be used for final launch, but I understand Stitch was designed just for rapid prototyping and for teams to get from the point where they just have an idea to having an actual product."
"The conversion to Figma is not effective."
"Generally speaking, support is a pain point. In the next release, I would love to see a change in support from the current chat to a more comprehensive portal."
"My experience with customer support for Stitch has been very bad."
"We create pipelines or jobs in StreamSets Control Hub. It is a great feature, but if there is a way to have a folder structure or organize the pipelines and jobs in Control Hub, it would be great. I submitted a ticket for this some time back."
"One thing that I would like to add is the ability to manually enter data. The way the solution currently works is we don't have the option to manually change the data at any point in time. Being able to do that will allow us to do everything that we want to do with our data. Sometimes, we need to manually manipulate the data to make it more accurate in case our prior bifurcation filters are not good. If we have the option to manually enter the data or make the exact iterations on the data set, that would be a good thing."
"The execution engine could be improved. When I was at their session, they were using some obscure platform to run. There is a controller, which controls what happens on that, but you should be able to easily do this at any of the cloud services, such as Google Cloud. You shouldn't have any issues in terms of how to run it with their online development platform or design platform, basically their execution engine. There are issues with that."
"The monitoring visualization is not that user-friendly. It should include other features to visualize things, like how many records were streamed from a source to a destination on a particular date."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"There aren't enough hands-on labs, and debugging is also an issue because it takes a lot of time. Logs are not that clear when you are debugging, and you can only select a single source for a pipeline."
"Currently, we can only use the query to read data from SAP HANA. What we would like to see, as soon as possible, is the ability to read from multiple tables from SAP HANA. That would be a really good thing that we could use immediately. For example, if you have 100 tables in SQL Server or Oracle, then you could just point it to the schema or the 100 tables and ingestion information. However, you can't do that in SAP HANA since StreamSets currently is lacking in this. They do not have a multi-table feature for SAP HANA. Therefore, a multi-table origin for SAP HANA would be helpful."
"I would like to see it integrate with other kinds of platforms, other than Java. We're going to have a lot of applications using .NET and other languages or frameworks. StreamSets is very helpful for the old Java platform but it's hard to integrate with the other platforms and frameworks."
 

Pricing and Cost Advice

Information not available
"The overall cost is very flexible so it is not a burden for our organization... However, the cost should be improved. For small and mid-size organizations it might be a challenge."
"The pricing is too fixed. It should be based on how much data you need to process. Some businesses are not so big that they process a lot of data."
"The pricing is affordable for any business."
"StreamSets is an expensive solution."
"It's not so favorable for small companies."
"We use the free version. It's great for a public, free release. Our stance is that the paid support model is too expensive to get into. They should honestly reevaluate that."
"We are running the community version right now, which can be used free of charge."
"It has a CPU core-based licensing, which works for us and is quite good."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Insurance Company
8%
Financial Services Firm
8%
Manufacturing Company
8%
Computer Software Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise2
Large Enterprise11
 

Questions from the Community

What needs improvement with Talend Stitch?
I wish Stitch could handle changes and updates to data better. I think improvement is needed in the licensing process.
What is your primary use case for Talend Stitch?
I have been using Stitch for the last five years. My main use case for Stitch is to ingest SFDC data and also Google Analytics, Facebook Ads, and GA4. I use Stitch as a data ingestion tool for SFDC...
What advice do you have for others considering Talend Stitch?
I do not want to add more about the features of Stitch. I do not have any other improvements needed for Stitch that I have not mentioned yet. My advice to others looking into using Stitch is to con...
What do you like most about StreamSets?
The best thing about StreamSets is its plugins, which are very useful and work well with almost every data source. It's also easy to use, especially if you're comfortable with SQL. You can customiz...
What needs improvement with StreamSets?
One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infr...
What is your primary use case for StreamSets?
We are using StreamSets for batch loading.
 

Comparisons

 

Also Known As

Talend Stitch ETL
No data available
 

Overview

 

Sample Customers

AB InBev, Accolade, Accor, AstraZeneca, Beachbody
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about Stitch vs. StreamSets and other solutions. Updated: December 2025.
881,082 professionals have used our research since 2012.