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

FME vs StreamSets comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 19, 2024

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

FME
Ranking in Data Integration
24th
Average Rating
8.6
Reviews Sentiment
6.8
Number of Reviews
5
Ranking in other categories
No ranking in other categories
StreamSets
Ranking in Data Integration
16th
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the Data Integration category, the mindshare of FME is 1.8%, up from 1.5% compared to the previous year. The mindshare of StreamSets is 1.6%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration
 

Featured Reviews

Alan Bloor - PeerSpot reviewer
Great for handling large volumes of data, but it is priced a bit high
When I do coding, I think about every single function. Some of these functions can be very elementary, like doing a substring or some capitalization. But FME removes all that coding because it's a transformer, so the time to develop an application to get to a point where you're producing results is decreased massively. It used to take weeks and months to develop software, and now I can use something like FME, and within one day, we get results. We can look at and validate data. We make minor subtle changes to the workbenches to improve it. We can share the workbenches. We don't have to use GitHub or anything else.
Karthik Rajamani - PeerSpot reviewer
Integrates with different enterprise systems and enables us to easily build data pipelines without knowing how to code
There are a few things that can be better. 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. There are certain features that are only available at certain stages. For example, HTTP Client has some great features when it is used as a processor, but those features are not available in HTTP Client as a destination. There could be some improvements on the group side. Currently, if I want to know which users are a part of certain groups, it is not straightforward to see. You have to go to each and every user and check the groups he or she is a part of. They could improve it in that direction. Currently, we have to put in a manual effort. In case something goes wrong, we have to go to each and every user account to check whether he or she is a part of a certain group or not.

Quotes from Members

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

Pros

"We make minor subtle changes to the workbenches to improve it. We can share the workbenches. We don't have to use GitHub or anything else."
"It has standard plug-ins available for different data sources."
"It has a very friendly user interface. You don't need to use a lot of code. For us that's the most important aspect about it. Also, it has a lot of connectors and few forms. It has a strong facial aspect. It can do a lot of facial analysis."
"All spatial features are unrivaled, and the possibility to execute them based on a scheduled trigger, manual, e-mail, Websocket, tweet, file/directory change or virtually any trigger is most valuable."
"The most valuable feature of FME is the graphical user interface. There is nothing better. It is very easy to debug because you can see all steps where there are failures. Overall the software is easy to optimize a process."
"StreamSets’ data drift resilience has reduced the time it takes us to fix data drift breakages. For example, in our previous Hadoop scenario, when we were creating the Sqoop-based processes to move data from source to destinations, we were getting the job done. That took approximately an hour to an hour and a half when we did it with Hadoop. However, with the StreamSets, since it works on a data collector-based mechanism, it completes the same process in 15 minutes of time. Therefore, it has saved us around 45 minutes per data pipeline or table that we migrate. Thus, it reduced the data transfer, including the drift part, by 45 minutes."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"For me, the most valuable features in StreamSets have to be the Data Collector and Control Hub, but especially the Data Collector. That feature is very elegant and seamlessly works with numerous source systems."
"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."
"The most valuable feature is the pipelines because they enable us to pull in and push out data from different sources and to manipulate and clean things up within them."
"The best feature that I really like is the integration."
"The most valuable would be the GUI platform that I saw. I first saw it at a special session that StreamSets provided towards the end of the summer. I saw the way you set it up and how you have different processes going on with your data. The design experience seemed to be pretty straightforward to me in terms of how you drag and drop these nodes and connect them with arrows."
"I have used Data Collector, Transformer, and Control Hub products from StreamSets. What I really like about these products is that they're very user-friendly. People who are not from a technological or core development background find it easy to get started and build data pipelines and connect to the databases. They would be comfortable like any technical person within a couple of weeks."
 

Cons

"Improvements could be made to mapping presentations."
"FME can improve the geographical transformation. I've had some problems with the geographical transformations, but it's probably mostly because I'm not the most skilled geographer in-house. The solution requires some in-depth knowledge to perform some functions."
"To get a higher rating, it would have to improve the price and the associated scalability. These are the main issues."
"The one thing that always appears in the community is the ability to make really easy loops to loop through data efficiently. That needs to be added at some point."
"FME's price needs improvement for the African market."
"The software is very good overall. Areas for improvement are the error logging and the version history. I would like to see better, more detailed error logging information."
"The design experience is the bane of our existence because their documentation is not the best. Even when they update their software, they don't publish the best information on how to update and change your pipeline configuration to make it conform to current best practices. We don't pay for the added support. We use the "freeware version." The user community, as well as the documentation they provide for the standard user, are difficult, at best."
"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."
"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."
"One area for improvement could be the cloud storage server speed, as we have faced some latency issues here and there."
"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."
"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."
"Visualization and monitoring need to be improved and refined."
 

Pricing and Cost Advice

"FME Server used to cost £10,000; now it can cost over £100,000."
"The product's price is reasonable."
"We used the standard licensing for our use of FME. The cost was approximately €15,000 annually. We always welcome less expensive solutions, if the solution could be less expensive it would be helpful."
"StreamSets is an expensive solution."
"Its pricing is pretty much up to the mark. For smaller enterprises, it could be a big price to pay at the initial stage of operations, but the moment you have the Seed B or Seed C funding and you want to scale up your operations and aren't much worried about the funds, at that point in time, you would need a solution that could be scaled."
"We are running the community version right now, which can be used free of charge."
"There are two editions, Professional and Enterprise, and there is a free trial. We're using the Professional edition and it is competitively priced."
"It's not so favorable for small companies."
"The pricing is affordable for any business."
"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."
"StreamSets Data Collector is open source. One can utilize the StreamSets Data Collector, but the Control Hub is the main repository where all the jobs are present. Everything happens in Control Hub."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
850,236 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Government
30%
Energy/Utilities Company
14%
Computer Software Company
8%
Comms Service Provider
5%
Financial Services Firm
13%
Computer Software Company
11%
Manufacturing Company
10%
Insurance Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about FME?
We make minor subtle changes to the workbenches to improve it. We can share the workbenches. We don't have to use GitHub or anything else.
What is your experience regarding pricing and costs for FME?
The pricing is really bad. Last year, they rebranded the whole pricing structure. It used to be moderately priced at about £400 per user per year. Now they've changed the whole thing, and it's expe...
What needs improvement with FME?
The one thing that always appears in the community is the ability to make really easy loops to loop through data efficiently. That needs to be added at some point. There must be a technical or comm...
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

 

Overview

 

Sample Customers

Shell, US Department of Commerce, PG&E, BC Hydro, City of Vancouver, Enel, Iowa DoT, San Antonio Water System
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about FME vs. StreamSets and other solutions. Updated: April 2025.
850,236 professionals have used our research since 2012.