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 (6th)
Stitch
Average Rating
7.2
Reviews Sentiment
5.9
Number of Reviews
9
Ranking in other categories
Cloud Data Integration (16th)
 

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

"The most valuable feature of Confluent is the wide range of features provided; they're leading the market in this category."
"The solution can handle a high volume of data because it works and scales well."
"Confluent is an amazing tool that is highly configurable, integrates very well with Jira, and lets you create nice documentation for various products while also supporting reporting and online content hosting."
"Kafka Connect framework is valuable for connecting to the various source systems where code doesn't need to be written."
"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 documentation process is fast with the tool."
"It is also good for knowledge base management."
"The design of the product is extremely well built and it is highly configurable."
"The setup process for Stitch was pretty easy, with a plug and play approach where the data is immediately available."
"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 has positively impacted my organization by allowing us to create MVPs quickly."
"The best features Stitch offers are that I can copy the designs directly to Figma, which has helped my team and me tremendously because in the beginning we had to design the application from scratch, but now we can get inspirations from Stitch and copy directly from Stitch to shorten our time."
"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."
"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 saved a lot of time, gave more options, and made it very quick and easy to build a UI."
 

Cons

"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 would be great if the knowledge based documents in the support portal could be available for public use as well."
"Confluent has a good monitoring tool, but it's not customizable."
"The pricing was high for our needs. We should not have to pay for features we do not use."
"Currently, in the early stages, I see a gap on the security side. If you are using the SaaS version, we would like to get a fuller, more secure solution that can be adopted right out of the box. Confluence could do a better job sharing best practices or a reusable pattern that others have used, especially for companies that can not afford to hire professional services from Confluent."
"It could be improved by including a feature that automatically creates a new topic and puts failed messages."
"One area we've identified that could be improved is the governance and access control to the Kafka topics. We've found some limitations, like a threshold of 10,000 rules per cluster, that make it challenging to manage access at scale if we have many different data sources."
"It could have more themes. The themes in the version I'm using are very limited; they offer two to three themes."
"Stitch should definitely provide more extractors than it does now and provide the ability for teams to integrate their own extractors."
"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."
"Until then, it does get a little bit complicated when we have Qlik and Stitch components together."
"The conversion to Figma is not effective."
"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."
"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."
"The customer support of Stitch is horrible."
"My experience with customer support for Stitch has been very bad."
 

Pricing and Cost Advice

"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
"It comes with a high cost."
"Confluent is an expensive solution."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"The solution is cheaper than other products."
"Confluent is highly priced."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"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."
Information not available
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
894,738 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Retailer
11%
Computer Software Company
10%
Manufacturing Company
5%
Construction Company
14%
Healthcare Company
12%
Outsourcing Company
12%
Financial Services Firm
9%
 

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 Business4
Midsize Enterprise3
Large Enterprise4
 

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?
Stitch could be improved by embedding more AI agentic features where the agents can perform part of the work and by being flexible enough to be trained to company culture and the entire data ecosys...
What is your primary use case for Talend Stitch?
My main use case for Stitch is cost optimization. During my work, we wanted to optimize costs to manage expenses, so the tool was quite helpful in that regard, and I used it frequently in my day-to...
What advice do you have for others considering Talend Stitch?
I'm not certain if I purchased Stitch through the AWS marketplace, as I was not involved in the procurement. My advice to others looking into using Stitch is to try it out, as the product is excell...
 

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 Confluent vs. Stitch and other solutions. Updated: April 2026.
894,738 professionals have used our research since 2012.