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

What do you like best about the product?

The clean, intuitive user interface and high processing speed stand out right away when compared to other platforms. The management console is well-designed and easy to navigate. Onboarding was very quick, and having an active community helped us get up to speed without friction.

What do you dislike about the product?

Certain pricing plans feel a bit expensive relative to alternative options. Some external integrations lacked consistent reliability during testing, and the suit of Ai agent features felt a bit excessive, with several tools not adding practical value to our workflow.

What problems is the product solving and how is that benefiting you?

We evaluated Redpanda to solve challenges around real-time streaming pipelines, through it didn't end up being our long-term fit. That said, during our test phase, the pipelines remained remarkably stable with a reduced infrastructure footprint, cutting down management time and letting us redirect effort to other core tasks.

What do you like best about the product?

The native C++ design and no overhead from the JVM are some notable highlights. The Kafka API compatibility allows us to replace broker without any charges in the application. No Zookeeper and KRaft dependencies make cluster configuration easier, and the Tiered Storage provides offloading cold partition partitions to the cloud automatically.

What do you dislike about the product?

Although the Web Console allows to monitor topics, more complicated management operations and fine-grained access control need additional enterprises-level licence. Also, as the ecosystem-level licence. Also, as the ecosystem is younger than that of Kafka, sometimes we need to spend more time searching for some troubleshooting guides in community.

What problems is the product solving and how is that benefiting you?

First of all, it reduces the heavy memory usage and GC latency spikes in traditional Kafka cluster. Secondly instead of wasting time on configuring nodes, Redpanda provides high throughput and low tail latency as a single excutedable.

What do you like best about the product?

The best things about it are the simple UI and how fast it is compared to other platforms. The console is very clean and easy to navigate. Onboarding was quick, and their community is quite active as well, which helped a lot.

What do you dislike about the product?

Pricing for specific plans was a little higher compared to other platforms. The external integrations didn’t work very reliably, and there are also so many AI agent features that it feels like too much many of them don’t really make sense.

What problems is the product solving and how is that benefiting you?

We were trying to solve the problem of running real-time data streaming, but it didn’t work out for us. That said, while we were testing it, the pipelines were stable and required less infrastructure. It also took less time for us to set up and manage, which freed us up to focus on other important problems.

What do you like best about the product?

The Kafka-compatible API makes it easier to implement streaming without having to completely rewrite the entire pipeline or change the overall development paradigm. For payment event processing, this can be especially useful for delivering transaction events to downstream services with low latency. I also appreciate the emphasis on minimizing the overhead involved in running the streaming infrastructure.

What do you dislike about the product?

Even with reliable streaming in place, you still have to think carefully about partitioning, retention policies, and consumer performance. For payment event pipelines in particular, consumer lag can delay transaction updates in downstream services, so monitoring and capacity planning become essential. On top of that, the migration process needs thorough compatibility testing to ensure existing integrations continue to work as intended.

What problems is the product solving and how is that benefiting you?

It helps when implementing real-time data pipelines by delivering payment events to downstream services, so each service doesn’t have to constantly poll the database for updates. With this approach, data stays fresher and you can reduce unnecessary database queries. Kafka compatibility can also make it easier to integrate with existing streaming solutions, although production performance still depends heavily on how the workload is designed and how well it’s monitored.

What do you like best about the product?

Transitioning our event streaming pipelines to the Redpanda Data Platform has substantially reduced our operational overhead while maintaining robust throughput. The primary advantage is its single binary C++ architecture, which completely eliminates the need for JVM garbage collection tuning and ZooKeeper dependencies, delivering predictable, ultra low p99 latencies under heavy load. Because Redpanda is natively compatible with the Apache Kafka API, we were able to migrate our existing producers, consumers, and connectors without making any code changes to our application layer. Features like built in Tiered Storage which automatically offloads historical log segments to object storage have significantly lowered our local storage costs, while the integrated console makes monitoring topic throughput and consumer lag straightforward right out of the box...

What do you dislike about the product?

The main limitations stem from documentation depth for niche setups and a heavy reliance on command line management for complex tasks. While the built in web dashboard works well for high level monitoring, detailed administrative actions still depend entirely on the rpk CLI tool. Additionally, while the core product documentation is thorough, finding specific guidance for complex deployment edge cases occasionally requires reaching out to their community Slack rather than finding immediate answers in the official docs, and certain legacy Kafka Connect plugins require extra validation before deploying at scale!...

What problems is the product solving and how is that benefiting you?

We needed a high-throughput event streaming platform that wouldn't require excessive engineering overhead to maintain. Redpanda solved our infrastructure cost and operational efficiency challenges by using a thread-per-core architecture that delivers higher throughput on fewer, smaller compute nodes compared to traditional options. By eliminating complex JVM tuning and external quorum management, our engineering team spends significantly less time managing cluster infrastructure and can onboard new developers to our data streaming platform much faster...

What do you like best about the product?

I like that Redpanda makes real-time data streaming fast and reliable without adding unnecessary complexity. Its Kafka compatibility, along with how easy it is to use, makes it a practical choice for building, running, and managing data streaming applications.

What do you dislike about the product?

Some parts of the platform can take time to learn, especially when you’re setting up and managing more complex streaming environments. I think the experience would be even better with more documentation and additional examples tailored to specific use cases, particularly for those more advanced setups.

What problems is the product solving and how is that benefiting you?

Redpanda helps simplify real-time data streaming while handling large volumes of data with low latency. It makes it easier to process data reliably, cut down on operational overhead, and build applications that can respond more quickly to events as they happen.

What do you like best about the product?

I like that Redpanda Data Platform is cost-efficient and easy to use. It feels sleek, and it helps my team make slick transactions in our workflow. I find it efficient and smooth. The upload feature for our team's AI lead source is the best feature for me. Uploading is easy, and it works smoothly alongside other apps. The initial setup was very easy.

What do you dislike about the product?

NOTHING, it really is so efficient and works like a dream

What problems is the product solving and how is that benefiting you?

I use Redpanda Data Platform to get full CRM access through its AI bandwidth and store everything in one simple bandwidth.

What do you like best about the product?

I like Redpanda Data Platform’s single-binary architecture and zero JVM dependencies. Deploying it on Kubernetes is painless, and Kafka API compatibility meant my team only had to update connection strings, not application code. Its thread-per-core design keeps tail latencies steady during traffic spikes without the memory thrashing or GC lag we had with Kafka. Restarts and rolling updates are fast, and Raft gets brokers back in sync almost immediately. It handles a few terabytes of events a day without choking on spikes, takes practically no day-to-day babysitting, and lets us get the same throughput with fewer AWS nodes. We also stopped dealing with JVM memory crashes, garbage collection lag, and broker rebalance storms during deploys.

What do you dislike about the product?

The jump to enterprise pricing feels steep just to get basic SSO and role-based access in the console. The web console feels limited for day-to-day operations, and its error messages give very little detail when connectors, partition syncs, or storage offloading fail. I end up using the rpk CLI and digging through raw pod logs to figure out what went wrong. Documentation can also be thin for edge cases with tiered storage or niche Kafka Connect plugins, and Redpanda needs fast local NVMe storage to hit its advertised throughput.

What problems is the product solving and how is that benefiting you?

Redpanda Data Platform stopped the constant JVM memory crashes and garbage collection lag we had on Kafka. I cut our AWS bill by running far fewer nodes for the exact same throughput, and no longer worry about random broker rebalance storms during deploy rollouts.

What do you like best about the product?

I like Redpanda Data Platform’s high-performance, low-latency event streaming. Deployment and management are simpler than with traditional messaging platforms, and its efficient resource use helps reduce infrastructure costs. I also value its strong Kafka compatibility, which makes it straightforward to integrate with existing tools and ecosystems without significant redevelopment.

What do you dislike about the product?

I found the initial setup a bit complex, and teams new to streaming architecture may face a steeper learning curve with event-driven architecture, streaming concepts, topic management, retention policies, partitioning, and performance tuning. Advanced administration and troubleshooting can require specialized experts, especially for deployment, performance optimization, security configuration, and diagnosing production issues. More detailed documentation for complex deployment scenarios would be helpful, and the community ecosystem is smaller than some long-established alternatives.

What problems is the product solving and how is that benefiting you?

I use Redpanda Data Platform to address real-time processing, scalability, and operational complexity across systems. It helps with latency and integration challenges, supports real-time data movement and event-driven architectures, simplifies infrastructure management, reduces operational overhead, improves application responsiveness, and gets critical business data downstream with minimal delay.

What do you like best about the product?

Easy to use for processing large amounts of data. Works fast and easy.

What do you dislike about the product?

It's not for everyone, you need some technical skills to use it.

What problems is the product solving and how is that benefiting you?

It helps handle data more efficiently and makes it a lot faster.