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

Amazon Kinesis vs Confluent comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Feb 8, 2026

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

Amazon Kinesis
Ranking in Streaming Analytics
5th
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
29
Ranking in other categories
No ranking in other categories
Confluent
Ranking in Streaming Analytics
9th
Average Rating
8.2
Reviews Sentiment
6.3
Number of Reviews
25
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Streaming Analytics category, the mindshare of Amazon Kinesis is 4.2%, down from 7.9% compared to the previous year. The mindshare of Confluent is 6.6%, down from 8.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Amazon Kinesis4.2%
Confluent6.6%
Other89.2%
Streaming Analytics
 

Featured Reviews

reviewer1480695 - PeerSpot reviewer
Director of Software Development at a tech vendor with 10,001+ employees
Has enabled real-time processing of critical event streams with seamless cloud integration
We are contemplating moving away from Amazon Kinesis primarily because of the cost. It is very useful, but if we write our own analytics and data processing pipeline, it would be much cheaper for us. The cost is a primary hindrance. That's why we are not using it widely. For our critical pipeline we are using it, but after that we are putting it in an S3 bucket. Other pipelines directly put the events in an S3 bucket and then process from there. There is no lack of functions in Amazon Kinesis. Functionality-wise, we feel it's complete. The cost aspect is what we are really concerned about.
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.

Quotes from Members

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

Pros

"Setting Amazon Kinesis up is quick and easy; it only takes a few minutes to configure the necessary settings and start using it."
"The solution's technical support is flawless."
"Amazon Kinesis is easy to get started with, provides good documentation, and has a multilang daemon interface that makes it programming-language agnostic."
"The product's initial setup phase is not difficult because we are using the tool on the cloud."
"Amazon Kinesis has improved our ROI."
"The Kinesis VideoStream and DataStream are the most important features."
"Amazon Kinesis's main purpose is to provide near real-time data streaming at a consistent 2Mbps rate, which is really impressive."
"The scalability is pretty good, as one can have any number of nodes spawned or replicated on the primary so that any load can be handled, perhaps a few terabytes with ease in around 15 seconds."
"I find Confluent's Kafka Connectors and Kafka Streams invaluable for my use cases because they simplify real-time data processing and ETL tasks by providing reliable, pre-packaged connectors and tools."
"Our main goal is to validate whether we can build a scalable and cost-efficient way to replicate data from these various sources."
"The most valuable is its capability to enhance the documentation process, particularly when creating software documentation."
"The biggest benefit of Confluent as a tool is that it is a distributed platform that provides more durability and stability."
"To date, we have seen improvements in performance and scalability, so we recommend this solution."
"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."
"Their tech support is amazing; they are very good, both on and off-site."
 

Cons

"Kinesis Data Analytics needs to be improved somewhat. It's SQL based data but it is not as user friendly as MySQL or Athena tools."
"We were charged high costs for the solution’s enhanced fan-out feature."
"One area for improvement in the solution is the file size limitation of 10 Mb. My company works with files with a larger file size. The batch size and throughput also need improvement in Amazon Kinesis."
"Something else to mention is that we use Kinesis with Lambda a lot and the fact that you can only connect one Stream to one Lambda, I find is a limiting factor. I would definitely recommend to remove that constraint."
"We are contemplating moving away from Amazon Kinesis primarily because of the cost."
"There could be valid data in Kinesis that is not being processed, which affects stability. Although it rarely happens, this issue has been observed in many deployments, making it not completely stable."
"For me, especially with video streams, there's sometimes a kind of delay when the data has to be pumped to other services. This delay could be improved in Kinesis, or especially the Kinesis Video Streams, which is being used for different use cases for Amazon Connect. With that improvement, a lot of other use cases of Amazon Connect integrating with third-party analytic tools would be easier."
"The default limit that they have, which at the moment is 5,000 records per second seems too low."
"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."
"Confluent has fallen behind in being the tool of the industry. It's taking second place to things such as Word and SharePoint and other office tools that are more dynamic and flexible than Confluent."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"The product should integrate tools for incorporating diagrams like Lucidchart. It also needs to improve its formatting features. We also faced issues while granting permissions."
"It could have more themes. The themes in the version I'm using are very limited; they offer two to three themes."
"From the control center perspective, there is a lot of room for improvement in the visualization."
"Confluent's price needs improvement."
"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."
 

Pricing and Cost Advice

"The product falls on a bit of an expensive side."
"The pricing depends on the use cases and the level of usage. If you wanted to use Kinesis for different use cases, there's definitely a cheaper base cost involved. However, it's not entirely cheap, as different use cases might require different levels of Kinesis usage."
"The tool's entry price is cheap. However, pricing increases with data volume."
"In general, cloud services are very convenient to use, even if we have to pay a bit more, as we know what we are paying for and can focus on other tasks."
"Amazon Kinesis is an expensive solution."
"Amazon Kinesis pricing is sometimes reasonable and sometimes could be better, depending on the planning, so it's a five out of ten for me."
"The tool's pricing is cheap."
"I rate the product price a five on a scale of one to ten, where one is cheap, and ten is expensive."
"Confluent is highly priced."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"The solution is cheaper than other products."
"You have to pay additional for one or two features."
"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."
"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."
"It comes with a high cost."
"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
12%
Manufacturing Company
8%
Construction Company
5%
Financial Services Firm
16%
Retailer
11%
Computer Software Company
8%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise10
Large Enterprise10
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise17
 

Questions from the Community

What is your experience regarding pricing and costs for Amazon Kinesis?
Amazon Kinesis and Lambda pricing is competitive, but we noticed that scaling and large volumes could potentially increase costs significantly.
What needs improvement with Amazon Kinesis?
We are contemplating moving away from Amazon Kinesis primarily because of the cost. It is very useful, but if we write our own analytics and data processing pipeline, it would be much cheaper for u...
What is your primary use case for Amazon Kinesis?
We use Amazon Kinesis for stream processing. We get events from on-premise devices to the cloud. We get many device events and we have to process these events that are coming from the devices. To p...
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...
 

Comparisons

 

Also Known As

Amazon AWS Kinesis, AWS Kinesis, Kinesis
No data available
 

Overview

 

Sample Customers

Zillow, Netflix, Sonos
ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Find out what your peers are saying about Amazon Kinesis vs. Confluent and other solutions. Updated: June 2026.
900,644 professionals have used our research since 2012.