streaming platform

Redpanda

Redpanda is a Kafka-compatible streaming platform written in C++. This profile covers what it does, how it is priced, and where it stops being the right choice.

What the product actually does

Redpanda implements the Kafka protocol without the JVM and without ZooKeeper. A single binary handles the broker, the schema registry and the HTTP proxy, and the storage engine is written to use the disk directly rather than relying on the page cache.

The compatibility is the selling point. Existing Kafka clients, connectors and tooling work unchanged, so adopting it is a deployment decision rather than an application one.

How pricing works once you are inside

The self-hosted product is free up to a point and licensed beyond it. The cloud product prices on throughput and storage, with the shape of the meter similar to Confluent's but the numbers lower.

The operational saving is the real cost argument: fewer moving parts means fewer machines and less engineering time, and for a team without a dedicated platform group that difference is larger than the licence.

Where it breaks down

Ecosystem depth. Kafka's connector catalogue is vast and Redpanda's compatibility means most of it works, but the long tail of tools that reach into Kafka internals rather than using the protocol will not.

Maturity relative to Kafka. Redpanda is younger, and a team that needs a decade of operational war stories will find fewer of them.

What switching costs

Low. The protocol is the interface, so clients and applications are unaffected. The deployment tooling and monitoring are what change.

Sources

Redpanda public documentation and pricing page, read October 2026.