Sign in
Sign in
or
Create a new account
Agent Mode
Categories
Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Redpanda Cloud - Annual Commits (BYOC & Dedicated/Serverless)

Redpanda

Reviews from AWS customer

3 AWS reviews

External reviews

26 reviews
from and

External reviews are not included in the AWS star rating for the product.

4-star reviews ( Show all reviews )

    ArpitShah

Event streaming has simplified video data cleanup and now powers real-time analytics

  • April 17, 2026
  • Review provided by PeerSpot

What is our primary use case?

We use Redpanda mainly for three purposes. The first is the standard Kafka-like data ingestion pipeline where you get an event and want to distribute it into multiple applications, not just one. The second, which is our main use case, involves capturing video recording data. When you consider how many video cameras exist even in a single city or metro, the volume becomes substantial. We capture what happened at each second, but we do not directly push it into the database. Instead, we pass it through Redpanda to ensure that everything follows a certain shape. Sometimes the data is corrupted, incomplete, or missing information. For example, an amount cannot be arbitrary; it has to be a specific number. We perform all those cleanups in our code while flowing the data through Redpanda with schemas in place. The third use case is backpressure management. If you want water to do the dishes but receive a fire hose instead, we ensure that you get the right amount of quantity. We keep this very simple, and after a certain point, it becomes a day-to-day operation.

Redpanda can handle real-time financial data streams and support aggregations. For example, with stock data where each tick represents a price point per second—such as Apple stock being 252.3, then 258, then 247—you can create means, medians, and averages. All these calculations work perfectly as long as your functions are pure. You get all the data without making additional API calls or database calls, flow it through Redpanda or any Kafka instance, and perform all kinds of calculations very quickly. The database is generally the slower component. Every single time we found it was almost always the database that gets slower or the way we normalize data causing issues. Redpanda never gave us any problems. I remember RabbitMQ used to give us a lot of problems, but all those problems are gone with Redpanda.

The video example I shared involves webcams. If you consider webcams as IoT devices, we use them that way and it just works. It is not real-time in the strictest sense, but it is almost real-time, which is good enough for our case.

What is most valuable?

One thing I really appreciate about Redpanda is that it is simple and available to host yourself. You do not have to pay money upfront to Confluent or have API contracts. Unless you want very high availability, you can just host it on your own server by running the Docker container and Redpanda works. This is very good. The other valuable feature is that migrating from one version to another has almost always been a very smooth experience. With Kafka, you have to manage a thousand things. These two are big benefits in Redpanda. The third feature is that the UI is slick. I would not say it is one of the best UIs in the world, but it is much better than what Kafka or Confluent comes up with out of the box.

What needs improvement?

One area for improvement is providing more examples. For instance, Redpanda could be more useful as a sink where you get the data and can directly push to S3. While this is possible through the API, there are better and faster ways to do it. You can make a million API calls and accomplish the task in one and a half hours, but the same thing can be done in ten minutes through other methods. These faster approaches are not documented in obvious places. You have to find information scattered across various blogs. Redpanda should collect all the good blogs and best practices and put them in their documentation. This is more about knowledge management and making it easy for users to understand the product for complex use cases. For simple use cases, it is straightforward. We all use the basic pipe functionality. However, providing more examples would be useful. For example, integration with AWS and the AWS ecosystem would be cool.

For how long have I used the solution?

We have been using Redpanda for at least the last four years.

What do I think about the stability of the solution?

Stability has been pretty good. I would rate it around eight or nine. Once in a while we restarted, but overall it is pretty stable.

What do I think about the scalability of the solution?

On scalability, we always scaled vertically. When 16 GB of RAM was not enough, we went to 32 GB RAM, then 64 GB RAM. We never scaled horizontally by adding one machine, then two machines, then three machines, and so forth. We just have a three-machine setup because if one machine fails, there is a backup, but it is not to distribute the load. In a way, it just works. I would say the scalability is around eight, nine, or ten. However, I do not know how well it scales horizontally. They obviously make big claims, but I never tried it because we just scale vertically.

Which solution did I use previously and why did I switch?

We previously evaluated Confluent and Kafka itself. I would not dare to go with Kafka because it requires way more orchestration than required. Confluent was good, and Redpanda was also good. However, Redpanda was an order of magnitude cheaper than Confluent, so we went with Redpanda.

How was the initial setup?

The initial setup for Redpanda is very smooth. Compared to Kafka, which feels like it requires a lot of knobs and pieces, Redpanda feels like a thirty-minute setup. This was actually one of the reasons why we wanted something we could just use rather than master first and then use. We started using Redpanda and then mastered it along the way because our use case is to flow it through the pipes, and that is done beautifully with Redpanda.

What about the implementation team?

We use Docker Swarm and deployed Redpanda on-premises.

What was our ROI?

The pricing for Redpanda is very good. I would rate it around nine.

Which other solutions did I evaluate?

We evaluated a couple of alternatives and liked three of them: Confluent, Redpanda, and others. However, Redpanda was simple and fast, so we went with Redpanda and it just works. Under the hood, it is just Kafka. They say that since it is written in C++ and Rust as a high-performance Kafka, it is fast. All the programming libraries we have are written for Kafka, and our Kafka is Redpanda. Since Redpanda provides compatibility with Kafka SDKs and APIs, we do not use Redpanda-specific SDKs or APIs. I cannot tell you how fast or slow Redpanda is compared to the original Kafka because the only Kafka instance I use is Redpanda. Redpanda is fast enough, but I cannot say that the original Kafka is slow because I never used the original Kafka.

What other advice do I have?

In my opinion, I am not sure about features for decision-making processes because I do not even know what kind of features are there for that. We just use Redpanda as a pipe. My overall rating for Redpanda is eight and a half out of ten.

    reviewer2785254

Stream processing has become faster and configuration time is reduced for high message volumes

  • January 21, 2026
  • Review from a verified AWS customer

What is our primary use case?

Our main use case for Redpanda is to send a large volume of messages and consume those messages, essentially processing them.

Redpanda is renowned for handling very high throughput. Redpanda, or Kafka, is able to process billions of messages.

What is most valuable?

Instead of using raw Kafka, Redpanda helps us manage Kafka at a production level, and it has a nice user interface so we can interact with any pending messages and processed messages.

Redpanda is developer-friendly, and we need to do much less configuration because Redpanda provides out-of-the-box configuration for us. It is not only a nice UI, but it also requires less configuration compared to a raw Kafka server. Redpanda is built on top of Kafka; their main architecture is Kafka only.

It has impacted us in a way that we need to do very little configuration, so we can quickly deploy Redpanda in stage, development, or production environments. We spend less time managing the raw Kafka server compared to Redpanda; Redpanda is less maintainable.

Using Redpanda, we do not need a separate team that specifically manages Kafka, so we have fewer employees needed, possibly one or two less employees, and time is also saved.

What needs improvement?

Redpanda can be improved by providing more local meetups or online meetups to increase awareness, as very few people know about it.

I think Redpanda is overall very good for us, and I am uncertain whether Redpanda can scale to very large companies as we are a medium-sized startup. However, if we consider an example of a very large company like Uber, I am not sure whether it would fit there.

For how long have I used the solution?

I have been working in my current field for more than 3.5 years.

What do I think about the stability of the solution?

Redpanda is very stable. As per our use case, it is very good.

How are customer service and support?

Overall, the customer service was very good, and the AWS team is also supporting us at any point.

How would you rate customer service and support?

Negative

Which solution did I use previously and why did I switch?

From the initial stages, we have been using Redpanda. Kafka server is one alternative, and another alternative is privately hosted Kafka servers on other cloud services.

What about the implementation team?

Our DevOps team has deployed Redpanda and manages it. I do not have any specific configuration or measurements.

Which other solutions did I evaluate?

Kafka server is one alternative, and another alternative is privately hosted Kafka servers on other cloud services.

What other advice do I have?

I recommend reading the documentation as it is comprehensive, and their user interface is also good. If you are a small startup or a medium-level startup, you can use Redpanda instead of Kafka. I would rate this product an 8 out of 10.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)

    Akhil S Varughese

Rapid data handling with increased peace of mind and significant cost savings

  • September 19, 2024
  • Review from a verified AWS customer

What is our primary use case?

We handle high volumes of telemetry data and operate under stringent latency requirements, with our data pipeline demanding sub-second response times. Redpanda seamlessly integrates into our data plane, particularly as a message broker system, where performance is absolutely critical. Its low-latency capabilities and robust performance have been essential to meeting our operational demands

How has it helped my organization?

The cost savings have been significant. We were able to eliminate one MSK cluster, and still, the end-to-end lag hasn't been worse. The performance is superb, and the value we are getting for the money we pay is great. Additionally, peace of mind is also a significant benefit due to the high performance and fault tolerance.

What is most valuable?

The whole system itself is valuable. The cost and performance are the primary benefits. Redpanda is extremely fast, which I describe as Kafka on steroids.

What needs improvement?

When it comes to self-hosting, their documentation could be improved. At the time we were onboarded, we had to apply our logic. Updating the documentation and managing the automation file for customer users to self-host would be beneficial.

For how long have I used the solution?

I have been using Redpanda for two years now.

What do I think about the stability of the solution?

Redpanda has been highly stable for our workloads. It utilizes the RAFT consensus algorithm, which ensures reliability by maintaining a quorum for data consistency and fault tolerance in cluster formation.

What do I think about the scalability of the solution?

I would rate the scalability of Redpanda as very high, around nine out of ten. They support a feature called tiered storage to offload data to keep the systems running efficiently, which provides us with ample capacity.

How are customer service and support?

They are really helpful. During our onboarding, they were very resourceful and knew what they were doing.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We previously used AWS MSK. We switched because MSK was very costly.

How was the initial setup?

The initial setup of Redpanda was straightforward and rated an eight out of ten. The setup involved using an Ansible script to bootstrap the cluster, which took about 10-15 minutes per cluster.

What about the implementation team?

The deployment was handled internally by one person with assistance from the provided Ansible script.

What was our ROI?

Apart from cost savings, the high performance and low latency provide peace of mind and operational efficiency.

What's my experience with pricing, setup cost, and licensing?

Redpanda is very cost-effective and offers competitive pricing compared to other options in the market. While not the lowest, the pricing is reasonable considering the high performance and value it delivers.

Which other solutions did I evaluate?

We considered Confluent Cloud, but after reviewing our needs, Redpanda seemed like the perfect fit due to its superior performance and cost benefits. Given that, we decided to move forward without a formal evaluation of other options.

What other advice do I have?

I would advise users to consider their in-house technical expertise when deciding the deployment model for Redpanda. If there is a lack of expertise, it is better to opt for the managed service offered by Redpanda.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)

    ArpitShah

Affordable, easy to deploy, and it is easy to find things on the user interface

  • June 21, 2024
  • Review provided by PeerSpot

What is our primary use case?

We use the tool for a simple use case. We use it for data streaming and data normalization. We receive a lot of messages from many different systems. We normalize them and highlight errors. We get 5000 to 6000 messages per minute, so we dump them in the database to handle the load. We use the tool for microservices.

What is most valuable?

The UI is modern. It is simple. We find what we are looking for.

What needs improvement?

The version control mechanism must be improved. Converting messages takes time. There is a version mechanism in the tool. It follows the coding standard, but sometimes, it gets confusing because I have to remove the older version to ensure the new version works fine.

For how long have I used the solution?

I have been using the solution for more than a year. I am using the latest version of the tool.

What do I think about the stability of the solution?

The product is pretty stable.

What do I think about the scalability of the solution?

We have around 20 users.

Which solution did I use previously and why did I switch?

We used RabbitMQ before.

How was the initial setup?

The setup is straightforward. The vendor takes care of everything. We just paid for the tool and started using it.

What's my experience with pricing, setup cost, and licensing?

Redpanda is cheaper than its competitors. It is cheaper than Vanilla Kafka and Confluent.

What other advice do I have?

We use the libraries in the different programming languages. We use the message format in Avro, convert the data in the format, and pass it on. We have contacted the sales team about the solution. So far, the product fulfills our requirements. We get lots of data. The data flows through Kafka to Redpanda. Then it goes to a database.

If our infrastructure goes down for a week, we will not lose data. It is an advantage of Redpanda. I recommend the product to others. We might choose a different solution if we find something cheaper. We used Redpanda because we did not want to self-host our software. Redpanda is a piece of infrastructure. There is not much of a learning curve.

Overall, I rate the tool an eight out of ten.

    Adam L.

Scalability, Usability, Stability - Pick all

  • April 29, 2024
  • Review provided by G2

What do you like best about the product?
Red Panda is substantlially easier to get up and running than a traditional Kafka queueing solution; while it's also more scalable and performance.
What do you dislike about the product?
So far, nothing really. The team has been extremely helpful, the application was trivial to deploy, and we've had few if any issues.
What problems is the product solving and how is that benefiting you?
We need a highly available, highly scalable real-time throughput persistence solution. Red Pandas offers this to us in spades.

    Javier B.

Solid product with great and efficient support

  • April 02, 2024
  • Review provided by G2

What do you like best about the product?
Red Panda has been our choice when we wanted to migrate our data pipeline to a stream-oriented approach, and since then, we've been very happy with the choice.
The support team is great and guides you through every step during the integration, and being able to deploy it in our cloud infrastructure /BYOC) was also a critical feature for us.

To sum it up: Great product, great support!
What do you dislike about the product?
The web interface sometimes falls a bit short, and you have to do the more complex stuff via the CLI.
What problems is the product solving and how is that benefiting you?
Red Panda is the backbone of our event-oriented data pipeline.
It hhelped us migrate our stack from a batch-oriented architecture to an event-oriented architecture.

    Austin H.

Great low cost alternative for kafka compliant data streaming

  • March 28, 2024
  • Review provided by G2

What do you like best about the product?
There are quite a few highlights. Working with the Redpanda team has been a really smooth process, during the sales and onboarding times especially. The team has been quite responsive and the slack channel for questions and tickets has been easy to use. The trial gave us ample time to validate our use case and confirm our estimates for data use.

The other real benefit comes from the pricing. Redpanda has allowed my small team the flexibility with learning as we build out our platform without worrying about going through our entire budget in a week or two, whereas some other data streaming platforms require an ironclad understanding of how much data you're putting into the system.
What do you dislike about the product?
The biggest downside so far revolves around the maturity of the product. Setting up a local environment still requires some deeper knowledge of data streaming and some other open source tools. Some of the documentation isn't complete, and features that are available in other platforms require a little bit of guesswork and experimentation to figure out.
What problems is the product solving and how is that benefiting you?
Redpanda is solving streaming data and distribution, and it is benefitting us by allowing our application to scale horizontally.

    Karl T.

Convenient and powerful tool for streaming data

  • March 18, 2024
  • Review provided by G2

What do you like best about the product?
We are replacing Kafka throughout all our systems with Redpanda and have been pleased with the performance and ease of use. The permanent backup to S3 to allow full replay of topics is a game changer of us. Additionally, support has been very responsive when we have had questions or issues.
What do you dislike about the product?
Some behavior was a little counterintuitive to us at first but now that we are more familiar with Redpanda we haven't had any significant issues.
What problems is the product solving and how is that benefiting you?
Data streaming at scale with no TTL on storing the data for replay

    Computer Software

Simple and cost-efficient Kafka alternative

  • March 16, 2024
  • Review provided by G2

What do you like best about the product?
It's very easy to use. Redpanda has replaced Kafka in our integration testing and we've been using it in production for more than a year.
What do you dislike about the product?
The Tiered Storage support could still somewhat unstable.
What problems is the product solving and how is that benefiting you?
Redpanda is used as a backbone of our infrastructure. It's the source of truth that powers all user-facing datasets. We leverage ClickHouse and Apache Flink together with Redpanda to provide critical real-time data pipelines to our users.

It has support for Tiered Storage, which allows us to use it as a source of truth. It's very cost-efficient. The compatibility with the Kafka protocol is great, we've never had any issues with that.

showing 1 - 9