One sign-in, one permission model, one record.
The parts that differ from tool to tool are the parts a team needs to be the same: who may act, where a change is allowed, and what happened afterwards.
Roles are granted to a person or a team for a scope, and the same rules decide what anybody may read or change on every platform.
One permission model →Every connection belongs to an environment. Read-only refuses writes while browsing stays open; guarded asks for a reason with every write. The policy covers every platform in it.
Production guardrails →Every write and every refusal, on every platform, lands in one tamper-evident trail that can be exported and verified.
The audit trail →Each platform contributes the figures it actually has — consumer lag, queue depth, memory, connection health — to one set of rules, delivered by e-mail and in the console in both editions.
Alert rules you can trust →Each broker keeps its own screens and its own words.
Consolidating the tooling does not mean flattening the brokers. A Kafka topic, a Redis stream, a RabbitMQ queue and an Artemis address are different things, and each platform is operated in its own terms.
Brokers, topics, consumer groups and lag, Schema Registry, Kafka Connect, ACLs and service accounts.
Kafka in BROKA →Keys and their types, streams and their pending entries, Pub/Sub, ACL users and the cluster.
Redis in BROKA →Exchanges, queues and bindings, shovels and federation, policies, users and permissions.
RabbitMQ in BROKA →Addresses and their routing types, the queues under them, scheduled and dead-lettered messages.
Apache Artemis in BROKA →Start with Kafka; the rest joins the same console.
Community is free and covers Apache Kafka and Kafka-compatible brokers in full, with the same permission model, environments, audit trail and alert rules. Redis, RabbitMQ and Apache Artemis — and Memcached, operated as a cache — are in Commercial, together with Applications, Access Review, data masking, single sign-on and the MCP server.
The same ideas under four vocabularies, side by side.
Compare broker capabilities →A broker that speaks the Kafka protocol is managed through the ordinary Kafka connection.
Other platforms →