
emacs-slack
Slack Gitsin
Axolo
PullNotifier
Wey
Graphite
Code Input
Review and release pull requests faster with Slack reminders and metrics.

Conduktor
UI for Apache Kafka
Kpow by Factor House
KafkaHQ
Lenses.io
Redis Commander
Another Redis DeskTop Manager
Self-hosted console for Kafka, Redis, RabbitMQ and Apache Artemis: one permission model, production guardrails and a tamper-evident audit trail.

Which is more popular?
Based on our record, PullReminders seems to be more popular. It has been mentioned 1 time since March 2021.
Website, pricing, platforms and company facts side by side.
|
|
|
|
|---|---|---|
| Website | pullreminders.com | broka.dev |
| Pricing | — | |
| Platforms | — | |
| Company | — | Startup from Turkey · 1 - 9 employees · 2026 |
| Listed in |
In their own words, as submitted to SaaSHub.


No description of PullReminders yet.
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. –...
What each product offers, as listed by its team.


Possible disadvantages
Walkthroughs and reviews on video.
No PullReminders videos yet. You could help us improve this page by suggesting one.
BROKA — One platform for your messaging infrastructure
How often each product is chosen within a category, 0–100% relative to the other.


As answered by people managing PullReminders and BROKA.
BROKA's answer:
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.
BROKA's answer:
BROKA's answer:
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.
BROKA's answer:
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.
BROKA's answer:
Share your experience with using PullReminders and BROKA. For example, how are they different and which one is better?
Recommendations tracked on public social media and blogs since March 2021.


Note: GitHub acquired Pull Panda, a company responsible for Pull Assigner and Pull Reminders. Those tools are currently being migrated into GitHub products. - Source: dev.to / almost 5 years ago
Tracking BROKA since Nov 2026.
When comparing PullReminders and BROKA, you can also consider the following products.

slack client for emacs. Contribute to yuya373/emacs-slack development by creating an account on GitHub.
Compare emacs-slack to PullReminders or BROKA:


A beautiful Slack command line interface
Compare Slack Gitsin to PullReminders or BROKA:

Open-Source Web GUI for Apache Kafka Management
Compare UI for Apache Kafka to PullReminders or BROKA:


Advanced Apache Kafka UI for monitoring and analytics
Compare Kpow by Factor House to PullReminders or BROKA: