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

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?

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.

What do you like best about the product?

That there are a lot of disk integrations that help with writes making things like disaster recover, IceBerg ingestion, very very fast, simple and their support teams helping us do that.

Most Kafka varients have connector platforms and those are helpful. But performant reliable disk level integrations I think postitions RedPanda at a better place.

What do you dislike about the product?

Some of the documentation for various layers of APIs are a little confusing. Similar to the connector platform documentation. People feel like they can administrate things via the UI. But sometimes I think it confuses the audience while giving them a lot of power.

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

RedPanda helps with resilience and guarantees but it positions us to turn on different data sources and sinks with ease without us having to rethink architecture (other areas often do). I haven't had to consider follower strategies once because their raft algorithm. I would like that we could potentially use it for disaster recovery for greater peace of mind

What do you like best about the product?

I really like Redpanda Streaming for its incredible customer support and impressive product quality. The cost of using Redpanda is another great feature, making it a compelling choice for my team. I also appreciate that it provides a managed BYOC Kafka solution, which is perfect for processing real-time and analytical data. Switching from Confluent to Redpanda was motivated by its cost-effectiveness and BYOC support, and the initial setup was very easy.

What do you dislike about the product?

Faster (and ideally proactive) reaction to cluster stability issues

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

Redpanda Streaming processes large scale data quickly.

What do you like best about the product?

What stands out most about Redpanda is how it modernizes the Kafka ecosystem without the traditional overhead. Here’s how it delivers value across our key focus areas:

UI / UX: The Redpanda Console provides a clean, intuitive, and high-performance interface that makes topic management, message inspection, and consumer group monitoring effortless for both developers and SREs.

Integrations: Its API compatibility with Kafka is flawless. We were able to leverage our existing ecosystem of connectors and tools without changing of code, making the transition seamless.

Performance: Their architecture provide significantly lower latency and higher throughput compared to JVM-based solutions.

Pricing / ROI: We’ve seen a better ROI - both in terms of cloud infrastructure costs and reduced operational "toil".

Support / Onboarding: The onboarding process was straightforward, and the Redpanda team's support is highly proactive. They feel more like partners in our architecture than just a vendor.

AI / Intelligence: We are excited about Redpanda’s vision for Data Transforms and its ability to process data in-stream. This is crucial for our AI workflows, allowing us to pre-process and clean data at the edge before it hits our models.

What do you dislike about the product?

Overall, the platform is very stable and meets our expectations. However, if I were to point out areas for improvement:

Integrations (Kafka Connect): Our main concern at the moment is the upcoming end-of-life/deprecation of managed Kafka Connect support. For a team that relies on a streamlined, managed ecosystem, this transition introduces additional operational complexity, as we now have to rethink how we manage our connectors.

UI / UX: Console is great, more terraform (IaC) support would be a welcome addition.

Support / Onboarding: No complaints here.
Pricing / AI / Performance: In these areas, we haven't encountered any significant issues.

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

Redpanda solves several pain points that we previously faced with traditional streaming platforms:

Operational Complexity (UI/UX & Onboarding): Providing a built-in, high-quality Console, Redpanda has simplified our entire stack. This benefits us by significantly reducing the time spent on cluster management and troubleshooting, allowing our engineers to focus on building features rather than managing infrastructure.

Infrastructure Efficiency (Performance & Pricing/ROI): We’ve seen a reduction in cloud infrastructure costs and achieved much more consistent performance for our real-time data pipelines.

Ecosystem Fragmentation (Integrations): Redpanda solves the 'compatibility gap' by being fully Kafka-API compatible. This benefited us by allowing a seamless migration - we kept our existing integrations and tools while upgrading the underlying engine without any friction.

Future-Proofing (AI & Intelligence): We hope that It addresses the challenge of processing massive data streams for AI workflows. With its low-latency profile and upcoming in-stream transformation capabilities, it benefits us by providing a scalable foundation for our real-time AI and machine learning initiatives.

Business Continuity (Support): Having direct access to technical experts during onboarding and scaling has ensured that our streaming services remain highly available and reliable.

What do you like best about the product?

I appreciate Redpanda Streaming for its ease of use in terms of setup and Kafka topic management, ACL management, and schema registry. The easy-to-define setup through the Redpanda web console is a big plus. I also like being able to access the APIs using the rpk tool, which provides a seamless CI/CD experience. The fast initial setup is complemented by the extensive and great documentation curated by the Redpanda team. I find the documents AI feature particularly useful as it makes it easy to search for information.

What do you dislike about the product?

Ability to set the broker node IP addresses as static from the get-go for the BYOC architecture. Ability to have basic features for networking and security such as CIDR ranges to pick and IP whitelisting.

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

I use Redpanda Streaming to allow our internal teams to publish and consume data easily. It provides customers real-time data access and centralizes data storage across the organization.

What do you like best about the product?

I like the Redpanda UI and how easy it is to navigate and search for topics/consumers

What do you dislike about the product?

I think the search is pretty difficult for the events in each topic. Looks like there's limit to how many events we can search from.
Also the reported metrics are a little different from other Kafka services which got me confused in the beginning; not sure if this is a bad thing tho

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

We're mostly using Redpanda for streaming services. I think we benefit from the performance and reasonable pricing for the services.

What do you like best about the product?

I find Redpanda Streaming easy to use with its user-friendly UI. I really appreciate its Kafka compatibility, which allows for seamless integration with Kafka tools and connections. This compatibility is a key feature for me as it enhances the functionality and connectivity of my backend systems.

What do you dislike about the product?

I don't like the price of bandwidth on BYOC when staying in the same zone. I'd prefer it to be free because it's free on GCP.

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

I use Redpanda Streaming to address ordering, scaling, and reliability issues in data streaming for our backend.

What do you like best about the product?

I really appreciate that Redpanda Streaming is fully Kafka compatible, making it easier to deploy and achieve high performance. The responsive support is a big plus, and I enjoy the nice UI. It's also a boon that Redpanda's performance and reliability are a lot better compared to the previous system we used.

What do you dislike about the product?

Support for Go clients leaves something to be desired, as the franz-go client often has trouble during leadership changes and coordinator transfers, causing clients to be stuck or lag. It's hard to determine if this is due to a Redpanda bug or a client-side issue. Additionally, the pricing model recently changed for the worse.

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

We use Redpanda Streaming for low-latency, async communication between services, with high availability and Kubernetes-friendly deployment, which solves our need for efficient data streaming like trade execution and ledger bookings internally.

What do you like best about the product?

BYOC, along with the excellent support, is helping us scale our systems stress-free.

What do you dislike about the product?

I don’t see any real downsides, but you do need to bring your own operational expertise around Kafka. As with any solution, without that experience it’s easy to architect yourself into something painfully inadequate.

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

We can move much faster by using streaming data and the contracts we define in the schema registry. With Confluent, every solution became painfully expensive over time as we grew. But now with RedPanda and BYOC we know we can trust the economics of our design to grow comfortably alongside us.