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

"Some of the best features are that it's very quick to set up, very easy to have a centralized area that gives us a history of changes, and the ability to give feedback on any information placed onto the pages."
"As an enterprise organization, data availability is critical and Confluent provides that SLA support."
"A person with a good IT background and HTML will not have any trouble with Confluent."
"Kafka Connect framework is valuable for connecting to the various source systems where code doesn't need to be written."
"Overall, it's a great company and they have excellent software."
"We primarily use Confluent for service desk and task management, and it is also good for knowledge base management."
"Our main goal is to validate whether we can build a scalable and cost-efficient way to replicate data from these various sources."
"The features I find most useful in Confluent are the Multi-Region Cluster, MRC, and the Cluster Linking for replication."
"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 saved a lot of time, gave more options, and made it very quick and easy to build a UI."
"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."
"Easy setup and easy change management are the best features Stitch offers, along with a good admin panel."
"Even though you are paying a huge amount, the quality and the time it takes to process big data is definitely lesser."
"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."
"The setup process for Stitch was pretty easy, with a plug and play approach where the data is immediately available."
 

Cons

"There is a limitation when it comes to seamlessly importing Microsoft documents into Confluent pages, which can be inconvenient for users who frequently work with Microsoft Office tools and need to transition their content to Confluent."
"Confluent has a good monitoring tool, but it's not customizable."
"Confluence could improve the server version of the solution. However, most companies are going to the cloud."
"It could have more themes. They should also have more reporting-oriented plugins as well. It would be great to have free custom reports that can be dispatched directly from Jira."
"The Schema Registry service could be improved. I would like a bigger knowledge base of other use cases and more technical forums. It would be good to have more flexible monitoring features added to the next release as well."
"It could be more user-friendly and centralized. A way to reduce redundancy would be helpful."
"It could have more themes. The themes in the version I'm using are very limited; they offer two to three themes."
"Confluent's price needs improvement."
"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."
"If there is something Stitch can improve, I would say it is the pricing structure."
"I would advise that you should not use Stitch if you are going to build a big number of screens or a heavy UI application with complex designs because it is not ready for that kind of work."
"To be frank enough, I will say right now that since we are not using it, they are too expensive."
"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 should definitely provide more extractors than it does now and provide the ability for teams to integrate their own extractors."
"The inspiration aspect for creating new screens could also have new versions, because the ones it creates look very generic."
 

Pricing and Cost Advice

"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
"Confluent is highly priced."
"Confluence's pricing is quite reasonable, with a cost of around $10 per user that decreases as the number of users increases. Additionally, it's worth noting that for teams of up to 10 users, the solution is completely free."
"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."
"It comes with a high cost."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"The solution is cheaper than other products."
Information not available
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
908,800 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Retailer
12%
Computer Software Company
8%
Manufacturing Company
6%
Construction Company
20%
Outsourcing Company
11%
Comms Service Provider
7%
Financial Services Firm
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: July 2026.
908,800 professionals have used our research since 2012.