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

What do you like best about the product?

What I like best about Redpanda Streaming is its operational simplicity combined with strong performance. It provides Kafka API compatibility while avoiding the complexity of managing ZooKeeper and reducing overall infrastructure overhead. The platform delivers predictable low-latency performance, scales well, and offers a straightforward developer experience. I also appreciate that it enables us to standardize on a single streaming platform for a wide range of use cases, from event-driven architectures to data integration, while maintaining full control over deployment and upgrades.

What do you dislike about the product?

What I dislike about Redpanda Streaming is that, while the core platform is mature and reliable, the surrounding ecosystem is not as extensive as Apache Kafka's. Some integrations, community resources, and third-party tooling are less common, which can occasionally require additional effort during implementation or troubleshooting. There are also areas where operational visibility and management capabilities could be further improved, particularly for large-scale enterprise deployments. Overall, these are relatively minor concerns compared to the benefits the platform provides.

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

Redpanda Streaming provides a reliable, scalable event-streaming platform that allows us to decouple systems and build event-driven architectures. It helps us standardize messaging across multiple applications while supporting high-throughput, low-latency workloads. The Kafka API compatibility enables easy integration with existing tools and frameworks, while the simplified operations reduce the effort required to deploy, maintain, and upgrade the platform. This results in faster delivery of new services, lower operational overhead, and a more consistent approach to real-time data distribution across the organization.

What do you like best about the product?

Redpanda Streaming offers quick support, a nice UI, and much cheaper and simple solutions.

What do you dislike about the product?

Latency that affects users in production. Every company has this but the longer a company is there the better they are at mitigating these risks.

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

Expensive storage.

What do you like best about the product?

Open source and straight to the point, with excellent performance for very common use cases.

Their integrations and massive component library is basically batteries-included for everything that you need. Pricing is decent, but the support has it comes with has been excellent.

What do you dislike about the product?

Bloblang is incredibly powerful and flexible, but performance is unideal. Then again, I haven't compared it to any other alternatives.

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

Our logistics company generates millions of events every day (scans, manifests, telemetry). Streaming them reliably to our various platforms is a critical part of our infrastructure.

What do you like best about the product?

The performance / price compared to options, e.g. DynamoDB

What do you dislike about the product?

I'd rather the licensing costs be less. We've had to scale the cluster up a few times, so the price point has escalated.

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

Ad bids from various vendors, and analytics on those bids. Complicated multi-region, multi-account, multi vendor interaction -- and soon multi-cloud deployments.

What do you like best about the product?

I really like Redpanda Streaming because it offers small latency, which enhances data accessibility and custom connectors. The event-driven architecture is a big plus, as it's Kafka API compatible without requiring Zookeeper, making it more lightweight. It also comes with a nice UI that allows me to filter data using JavaScript, which is better than what I've used with Confluent. Additionally, Redpanda Streaming's command-line interface, rpk, helps with certain low-level tasks. Their support is top-notch and readily available, answering all my questions no matter how big or small, and they also provide engineering expertise when needed. I appreciate their documentation and support team, which made the initial setup process manageable.

What do you dislike about the product?

Redpanda needs a data lineage graph that shows the data pipelines from ingress, to Kafka processors, producers and consumers, and egresses via connectors (to databases, etc). Also, sometimes the UI is a little 'hokie' when trying to find certain messages if there is a lot of traffic.

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

I use Redpanda Streaming for near real-time data acquisitions, aggregations, and queries. It offers small latency, data accessibility, and custom connectors, all without requiring Zookeeper, making it lightweight. The Kafka API compatibility helps us easily integrate into our existing systems.

What do you like best about the product?

Redpanda connectors work great and there is a great support from the account management and technical team, which is always willing to resolve doubts and escalate situations that require more attention on timely manner

What do you dislike about the product?

In one specific case, a connector was using a data type that apparently wasn’t properly tested in the new version of Redpanda being released, and it ended up causing issues in our development environment, but then it was resolved accordingly

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

It is helping with the migration of massive amounts of data from legacy databases into newer ones

What do you like best about the product?

What I like best about Redpanda Streaming is the level of support and partnership they provide. Their account team is highly responsive, accountable, and easy to work with. We consistently receive timely responses to questions and issues, along with proactive feedback on the health and performance of our clusters. I also appreciate their AWS BYOC offering, which is straightforward to understand and oeprate, making adoption and ongoing management much simpler. Overall, the combination of strong customer support, proactive engagement, and an easy-to-use platform has made for a very positive experience.

What do you dislike about the product?

While Redpanda is highly performant, the management interface can sometimes feel a bit difficult to navigate. Additionally, because we are using the Bring Your Own Cloud (BYOC) deployment model, it can occasionally be challenging to isolate and troubleshoot the exact root cause of errors when they arise. The built-in monitoring and observability features could definitely be improved to provide better visibility into these underlying infrastructure issues.

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

Redpanda is solving the challenge of managing high-volume, latency-sensitive data streams within our fintech ecosystem. As a high-performance messaging service, it allows us to ingest and process massive workloads concurrently while maintaining the ultra-low latency required for financial transactions. The biggest benefit has been a streamlined infrastructure that keeps our real-time applications fast, stable, and highly reliable.

What do you like best about the product?

What I like best about Redpanda Streaming is that it gives us a Kafka-compatible platform with strong performance, better operational simplicity, and a clear positive impact on infrastructure costs. In our case, this was very valuable because we could migrate existing Kafka-based services without fully redesigning the way teams produce and consume messages. Redpanda has helped us modernize our streaming platform and reduce part of the complexity and cost related to our previous Kafka architecture, especially around multi-region traffic and infrastructure operations. The BYOC model also fits well with our infrastructure strategy, as we can run the platform close to our workloads while still getting vendor support and managed operational guidance. Another important point is the performance and stability improvements we have seen during the migration, especially after tuning configuration and working with the Redpanda team on specific issues. The onboarding and support experience has also been useful: when we found problems around retention, disk usage, or producer behavior, the Redpanda team helped us understand the root cause and apply the right changes. Overall, Redpanda has helped us improve our real-time streaming platform while reducing operational burden and infrastructure costs compared with our previous Kafka setup.

What do you dislike about the product?

The main thing I dislike about Redpanda Streaming is that some operational behaviors are still not always easy to understand or predict without help from the Redpanda team. During our migration, we found some cases where disk usage, local retention, and cleanup behavior were not as clear as expected. For example, we had topics configured with local retention, but older segments were still kept on disk until additional settings were adjusted. This created some uncertainty during production operations because it was not obvious from the beginning why disk usage was not decreasing. Another area that could be improved is the Terraform provider and infrastructure-as-code experience. Since we manage most of our infrastructure through Terraform, provider stability, complete resource coverage, clear examples, and predictable behavior are very important for us. Some parts of the provisioning and configuration flow still feel less mature than the core streaming product, which can slow down platform teams when automating environments or applying changes safely. I think the product would benefit from clearer documentation, better defaults, stronger Terraform provider support, and more visible explanations in the UI around retention, tiered storage, housekeeping, and space management decisions. The support team has been helpful, but ideally the platform should make it easier for users to understand and operate these situations directly through metrics, alerts, recommendations, and reliable automation tooling.

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

Redpanda Streaming is helping us modernize our real-time data streaming platform and reduce the operational complexity we had with our previous Kafka-based architecture. Before Redpanda, we had several Kafka clusters across regions and needed to replicate a lot of traffic between them, which increased infrastructure cost, operational effort, and the risk of having a fragile setup. With Redpanda, we are moving to a more efficient and easier-to-operate streaming platform that is Kafka-compatible, so our teams can migrate progressively without changing all their applications from scratch. This is important for us because many critical services depend on streaming data, and we need good performance, low latency, and predictable operations. Redpanda also helps us improve ownership and visibility because we can create specific users per service, track usage better, and manage access in a more controlled way. The main benefits are reduced complexity, better scalability, clearer service ownership, and a path to reduce cross-region replication costs while keeping compatibility with our existing Kafka workflows.

What do you like best about the product?

UI / UX
Redpanda Console is clean and intuitive. I can browse topics, check consumer group lag, and get basic cluster configuration at a glance without digging through config files. For day-to-day monitoring this saves me from running repeated rpk commands just to sanity-check the cluster state. Deeper operations like ACL management still push me to the CLI, but for the routine checks I do multiple times a day, the Console cuts that time significantly.

Integrations
The Kafka API compatibility means we can integrate Redpanda with many tools/technologies such as Kroxylicious (a Kafka protocol proxy) without any changes to client code. That gave us tenant isolation and header enrichment at the proxy layer, something that would have taken weeks of refactoring to achieve natively in Kafka. Existing connectors, monitoring agents, and tooling all just worked from day one.

Performance
Broker restarts are noticeably fast compared to what I was used to with Kafka. Predicting workload is much more comfortable because the latency profile is consistent. I'm not constantly second-guessing whether a spike is GC or actual load.

Pricing / ROI
Best example is the Community edition covers most production use cases at zero licensing cost, which I've seen benefit multiple organisations I've worked at. It removes the conversation about budget approval before you can even prove the technology works.

Support / Onboarding
Documentation is well-structured and developer-friendly. I can usually find what I need without raising a ticket. Moreover, when I needed to raise a Redpanda Support Ticket, I asked its built-in AI and it gave me needed solution. The Redpanda community Slack is active and I've had blockers resolved same day. When we do need enterprise-level help, our Principal Customer Success Manager is genuinely engaged with our use case, not just routing us to generic docs.

AI / Intelligence
The built-in AI for support is already useful, but there's a next step that I'd love to see: AI that can correlate metrics directly inside the Console and explain anomalies in plain language during an incident. Right now I'm context-switching between dashboards, logs, and external tools to piece together what's happening.

What do you dislike about the product?

The Helm chart configuration surface is large, and when you’re deploying across multiple environments and regions, it’s very easy to end up with a sprawl of values files that are difficult to diff and audit.

A more structured knowledge base for common operational problems would help a lot. It would cut down the time I spend asking questions that have almost certainly already been answered.

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

Because Redpanda is fully Kafka API compatible, the proxy layer just works, clients connect to Kroxylicious exactly as they would connect to Kafka, with no changes on their side. We configure header enrichment and routing rules in the proxy, and those changes are completely invisible to producers and consumers.

As a result, what would have been a weeks-long refactor across multiple client codebases turned into an infrastructure-side configuration change instead.

What do you like best about the product?

The best part of Redpanda is the part that isn't flashy. Stability, performance, and cost effectiveness. The integrations save time and the support is phenomenal. The documentation is also excellent.

What do you dislike about the product?

There is nothing that I dislike about Redpanda so far. It replaced a much more expensive product and performs better than the previous product.

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

Redpanda is solving log collection and distribution at massive scale.