RoxaDocumentation

A Kafka-compatible message broker with S3 storage. A single binary, no ZooKeeper or JVM, self-hosted.

Data lives in S3

The ack arrives only after a durable write to storage (S3/MinIO or the local file system). The broker is near-stateless — the node is disposable.

Kafka ecosystem

Produce/Fetch, consumer groups, compression, idempotent producers, SASL/PLAIN. Existing clients work without a rewrite.

Deployed in a minute

A single container, or a docker compose production stack with the web console, MinIO and monitoring. Air-gapped — via an offline tarball.

Perpetual license

Perpetual + maintenance — the version you bought works forever, a year of updates is included. License verification is offline, no phone-home.

Components

Component	What it does
`roxa serve`	the broker: gRPC data-plane (`:50051`) + Kafka wire protocol (`:9092`) + Prometheus `/metrics`
`roxa admin`	the web console: topics, messages, consumers, monitoring, diagnostics (`:8080`)
`roxa license show`	license token verification (offline)
`roxactl`	CLI: topics, produce/consume, offsets, cluster status — over gRPC
`roxa-client`	the Rust library (SDK) on top of gRPC

Where to start

Just want to look around — the shared demo environment on roxa.dev, no installation.
Want to try it locally — the single-container quickstart.
Rolling out production — the docker compose stack and operations.
Migrating from Kafka — the compatibility matrix and client examples.

Current status

Roxa is a single-node broker: reliability comes from storing data in S3 rather than from replication (a node dies — a new one starts and reads the same data). An HA cluster is in development (the Enterprise edition).