BROKA
Self-hosted console for Kafka, Redis, RabbitMQ and Apache Artemis: one permission model, production guardrails and a tamper-evident audit trail.
A startup from Turkey, founded by H. Yusuf Yavuz, M. Ali Goren, O. Kumcular.
Self-hosted console for Kafka, Redis, RabbitMQ and Apache Artemis: one permission model, production guardrails and a tamper-evident audit trail.
A startup from Turkey, founded by H. Yusuf Yavuz, M. Ali Goren, O. Kumcular.
This page is designed to help you find out whether BROKA is good and if it is the right choice for you.
BROKA is a self-hosted operations console for Kafka, Redis, RabbitMQ and Apache Artemis, with Memcached operated as a cache. It runs on your own infrastructure with Docker Compose; there is no hosted version.
– One permission model: users, teams and scoped roles across every broker you connect. – Production guardrails: read-only or guarded environments, a reason for destructive operations, offset resets previewed before they run. – A tamper-evident audit trail of every administrative action, which you can export and verify outside BROKA. – Kafka: topics, consumer groups, Schema Registry, Kafka Connect, ACLs, a message browser with filters, broker health over JMX, and alerting.
BROKA Community is free and covers Kafka, with no account needed. BROKA Commercial adds Redis, RabbitMQ, Apache Artemis and Memcached, single sign-on, Message Search, data masking, applications and Slack/Teams alerts. It is licensed per installation, not per user or broker.
Listed in
Multi-broker console
Kafka, Redis, RabbitMQ and Apache Artemis in one self-hosted console, with Memcached operated as a cache.
One permission model
Users, teams and scoped roles across every broker you connect.
Production guardrails
Read-only or guarded environments, a reason for destructive operations, offset resets previewed before they run.
Tamper-evident audit trail
Every administrative action is recorded; export the trail and verify it outside BROKA.
Kafka management
Topics, consumer groups, Schema Registry, Kafka Connect, ACLs and a message browser with filters.
Kafka broker health over JMX
Request performance, utilisation, disk and JVM figures read live from the brokers.
Alerting
Rules are checked against live clusters before saving. E-mail in Community; Slack, Teams and webhooks in Commercial.
Single sign-on
OpenID Connect and LDAP, with identity-provider groups mapped to teams (Commercial).
Data masking
Masking rules applied on every message read path, failing closed (Commercial).
Self-hosted
Runs on your own infrastructure with Docker Compose; there is no hosted version.
BROKA operates Kafka, Redis, RabbitMQ and Apache Artemis, with Memcached as a cache, from one self-hosted console. They share one permission model, one set of environments and one tamper-evident audit trail.
Most tools cover a single broker, so a team that runs several ends up with a separate UI, login and permission set for each.
Platform, SRE and backend teams who operate message brokers and caches in production, and the team leads who need to know who can change what, and who did.
Inside one company, different teams often run different brokers with different tools: one team on Kafka with its own UI, another on the RabbitMQ management UI, a third on the Redis CLI. Each has its own logins and permissions, and nobody has one picture of which service uses which topic or queue, who owns it, or who changed what.
The changes that hurt are usually the routine ones, like an offset reset on the wrong consumer group or a purge on the wrong queue. BROKA puts those brokers under the same roles, guardrails and audit trail.
We have collected here some useful links to help you find out if BROKA is good.
Check the traffic stats of BROKA on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of BROKA on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of BROKA's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of BROKA on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about BROKA on Reddit. This can help you find out how popualr the product is and what people think about it.
Do you know an article comparing BROKA to other products?
Suggest a link to a post with product alternatives.
Is BROKA good? This is an informative page that will help you find out. Moreover, you can review and discuss BROKA here. The primary details have been verified within the last quarter. So they could be considered up to date. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.
