No more typing reviews! Try our Samantha, our new voice AI agent.

Confluent vs Stitch 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

Confluent
Average Rating
8.2
Reviews Sentiment
6.3
Number of Reviews
25
Ranking in other categories
Streaming Analytics (7th)
Stitch
Average Rating
7.4
Reviews Sentiment
6.0
Number of Reviews
12
Ranking in other categories
Cloud Data Integration (11th)
 

Featured Reviews

PavanManepalli - PeerSpot reviewer
AVP - Sr Middleware Messaging Integration Engineer at Wells Fargo
Has supported streaming use cases across data centers and simplifies fraud analytics with SQL-based processing
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools. They need to improve in that direction by not only reducing costs but also providing better solutions for the problems customers face to avoid frustrations, whether through future enhancement requests or ensuring product stability. The cost should be worked on, and they should provide better solutions for customers. Solutions should focus on hierarchical topics; if a customer has different types of data and sources, they should be able to send them to the same place for analytics. Currently, Confluent requires everything to send to the same topic, which becomes very large and makes running analytics difficult. The hierarchy of topics should be improved. This part is available in MQ and other products such as Solace, but it is missing in Confluent, leading many in capital markets and trading to switch to Solace. In terms of stability, it is not the stability itself that needs improvement but rather the delivery semantics. Other products offer exactly-once delivery out of the box, whereas Confluent states it will offer this but lacks the knobs or levers for tuning configurations effectively. Confluent has hundreds of configurations that application teams must understand, which creates a gap. Users are often unaware of what values to set for better performance or to achieve exactly-once semantics, making it difficult to navigate through them. Delivery semantics also need to be worked on.
Jason Hale - PeerSpot reviewer
Enterprise Architect at Waikato Regional Council
Data team has transformed diverse environmental streams and now delivers real-time insights
The best thing that we've seen coming out of Stitch is the Talend and Qlik relationship becoming more of a single entity rather than two entities. A couple of years ago there was a distinction between Stitch and Qlik. The biggest challenge when we were dealing with both was that we felt like we were dealing with two different companies. They are quickly merging the two different entities into a single one, and by around the end of this year, they're planning to basically consolidate everything. Until then, it does get a little bit complicated when we have Qlik and Stitch components together. It's not quite exactly one solution. That's probably the biggest negative at the moment. Each month we're seeing improvements in the cloud platform, and they're coming out with capabilities that we haven't even thought about that are going to make our lives easier. Probably the biggest negative they have is they're doing so much good stuff, but we don't know about it. It just appears and then we figure it out ourselves, but the communication of changes could be improved. However, the positives are that they're changing so much at the moment.

Quotes from Members

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

Pros

"To date, we have seen improvements in performance and scalability, so we recommend this solution."
"Kafka Connect framework is valuable for connecting to the various source systems where code doesn't need to be written."
"The monitoring module is impressive."
"I would rate the scalability of the solution at eight out of ten. We have 20 people who use Confluent in our organization now, and we hope to increase usage in the future."
"Confluence's greatest asset is its user-friendly interface, coupled with its remarkable ability to seamlessly integrate with a vast range of other solutions."
"The benefit is escaping email communication. Sometimes people ignore emails or put them into spam, but with Confluence, everyone sees the same text at the same time."
"We mostly use the solution's message queues and event-driven architecture."
"Our main goal is to validate whether we can build a scalable and cost-efficient way to replicate data from these various sources."
"The setup process for Stitch was pretty easy, with a plug and play approach where the data is immediately available."
"Easy setup and easy change management are the best features Stitch offers, along with a good admin panel."
"After setting up Stitch, that pipeline maintenance dropped down to practically zero, cutting our data integration and engineering workload by at least eighty to ninety percent and allowing us to get data into our dashboards in real time instead of waiting days for manual updates."
"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."
"Previously it took me about a month to a month and a half to have a prototype of roughly five to ten screens, now I can do it in about two to three days."
"We've got a project at the moment that we estimated the integration was going to be around $200,000 to $300,000, and we've been able to achieve the integration for less than a tenth of that, doing it in-house using Stitch."
"Stitch's best features include reporting and real-time insights, and what stands out to me is the speed, accuracy, and creativity in providing state-of-the-art features, leading to better insights, quicker time to market, and facilitating decisions, which I find quite impressive."
"Stitch has positively impacted my organization by allowing us to create MVPs quickly."
 

Cons

"It could be improved by including a feature that automatically creates a new topic and puts failed messages."
"From the control center perspective, there is a lot of room for improvement in the visualization."
"The pricing model should include the ability to pick features and be charged for them only."
"Areas for improvement include implementing multi-storage support to differentiate between database stores based on data age and optimizing storage costs."
"Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools."
"I am not very impressed by Confluent. We continuously face issues, such as Kafka being down and slow responses from the support team."
"The pricing was high for our needs. We should not have to pay for features we do not use."
"The solution could have an extra plugin or upgrading feature. In addition, it could have more integration with different platforms and be more compatible."
"The customer support of Stitch is horrible."
"The conversion to Figma is not effective."
"Stitch should definitely provide more extractors than it does now and provide the ability for teams to integrate their own extractors."
"My experience with customer support for Stitch has been very bad."
"Until then, it does get a little bit complicated when we have Qlik and Stitch components together."
"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."
"Stitch can be improved by being able to connect the design system to it, and being able to design any components from that design system would be the best improvement."
"To be frank enough, I will say right now that since we are not using it, they are too expensive."
 

Pricing and Cost Advice

"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
"Regarding pricing, I think Confluent is a premium product, but it's hard for me to say definitively if it's overly expensive. We're still trying to understand if the features and reduced maintenance complexity justify the cost, especially as we scale our platform use."
"The solution is cheaper than other products."
"On a scale from one to ten, where one is low pricing and ten is high pricing, I would rate Confluent's pricing at five. I have not encountered any additional costs."
"The pricing model of Confluent could improve because if you have a classic use case where you're going to use all the features there is no plan to reduce the features. You should be able to pick and choose basic services at a reduced price. The pricing was high for our needs. We should not have to pay for features we do not use."
"Confluent is highly priced."
"You have to pay additional for one or two features."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
Information not available
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Retailer
12%
Computer Software Company
7%
Manufacturing Company
6%
Construction Company
19%
Outsourcing Company
11%
Healthcare Company
9%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise17
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise3
Large Enterprise5
 

Questions from the Community

What is your experience regarding pricing and costs for Confluent?
They charge a lot for scaling, which makes it expensive.
What needs improvement with Confluent?
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about ...
What is your primary use case for Confluent?
The main use cases for Confluent are log aggregation and streaming. I'm familiar with Confluent stream processing with KSQL. KSQL helps in terms of data analytics strategies because if we are the d...
What needs improvement with Talend Stitch?
If there is something Stitch can improve, I would say it is the pricing structure. It scales based on row count, so if we suddenly have a massive surge in data, our cost can jump up pretty fast. Wh...
What is your primary use case for Talend Stitch?
My main use case for Stitch is to integrate retail data and connect different sources seamlessly. I mostly use it for moving data into a central warehouse, so I can easily analyze and build visuali...
What advice do you have for others considering Talend Stitch?
Regarding Stitch's AI capabilities, the governance and security side feels pretty tight. When you are feeding data through AI-driven pipelines, you worry about a lot of things. But Stitch handles d...
 

Comparisons

 

Also Known As

No data available
Talend Stitch ETL
 

Overview

 

Sample Customers

ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
AB InBev, Accolade, Accor, AstraZeneca, Beachbody
Find out what your peers are saying about Amazon Web Services (AWS), Informatica, Palantir and others in Cloud Data Integration. Updated: August 2026.
909,725 professionals have used our research since 2012.