"I'm preferably a Windows desktop application, but … given that I see it runs in Docker, it sounds like it may be web based."
Senior product manager, energy services company
Most people who ask for a Kafka GUI client picture an app on their own machine. For one developer on a test cluster, it's the simplest setup.
The setup changes once ten people point the same app at production. Each copy connects to the brokers itself, with credentials stored on that laptop.
Kafka GUIs split into desktop clients and web UIs you host once for the team, and the split decides where credentials live, who sets each person's permissions and what an audit log can tell you.
The common options, compared on those three points:
| Tool | Runs as | License | How people sign in | Where Kafka credentials live | Per-person permissions | Audit log |
|---|---|---|---|---|---|---|
| Offset Explorer | Desktop app | Commercial | No sign-in | On each laptop | The ACLs of the principal each person configures | None in the client |
| AKHQ | Web UI, one container | Apache 2.0 | LDAP, OIDC, GitHub or reverse-proxy headers | AKHQ's server config | Roles and topic patterns in its config file | Changes only, to a Kafka topic, off by default |
| Kafbat UI | Web UI | Apache 2.0 | OAuth 2 or LDAP | Server config | RBAC in its config | — |
| Redpanda Console | Web UI | BSL | SSO with an Enterprise license | Server config | RBAC with an Enterprise license | — |
| Kpow | Web UI | Commercial, free Community edition (3 clusters, 10 users) | SSO on Enterprise | Server config | RBAC in a YAML file (Enterprise) | Full audit log (Enterprise) |
| Conduktor Console | Web UI, with PostgreSQL | Commercial, free Community Edition (3 clusters, 50 users) | Local users, OIDC, SAML or LDAP | Console's cluster configuration | Per topic, consumer group, subject and connector | Changes and topic browsing (paid plans) |
kcat and the Kafka CLI tools aren't GUIs, but they connect from the laptop the way a desktop client does, so the next section applies to them too. A desktop client connects to the brokers from each laptop
A Kafka client first reaches a bootstrap server. It then opens connections to the brokers that lead the partitions it reads, at the addresses in each broker's advertised.listeners. A desktop GUI is a Kafka client like any other, so every laptop that runs it needs a network route to those brokers.
On a production cluster, that usually means a VPN or a bastion host for each person. The app also needs credentials the brokers accept:
- SASL/SCRAM or PLAIN. A username and password, saved in the app's connection settings or typed in each session (authentication options).
- mTLS. A client certificate and its private key, stored on the laptop (mTLS for Kafka).
- OAuth (
OAUTHBEARER). A token from your identity provider, which can identify each person if the cluster maps tokens to principals.
That last case is the strongest argument for a desktop client: when each person has their own Kafka principal, the brokers can tell people apart. When people share one principal per environment instead, the brokers see one user, and rotating its password means updating every laptop that stored it.
A web UI signs people in and connects with one service account
A self-hosted web UI runs once, on a host that can reach the brokers, and connects with the service account configured on the server. People open it in a browser and sign in through your directory or identity provider.
Rotating the service account's password becomes one change on one server. Removing someone's access means removing them from a group in the identity provider, and no laptop keeps a copy of the cluster credentials.
The cost is a service to run and upgrade. AKHQ runs as one container with no database to back up. Others keep users and settings in a database such as PostgreSQL, which you deploy next to them.
Kafka ACLs or the UI's roles decide what each person can do
With a desktop client, Kafka's ACLs decide everything. The app can do whatever its configured principal may do, so a shared principal with write access gives write access to everyone who has its password.
A web UI adds its own permissions in front of the service account. The service account holds everything any user needs, and the UI narrows it per person: who can consume a topic, reset a consumer group's offsets or delete a subject. A lead developer at a public-sector agency described when that starts to matter:
"The desktop app works fine for us but … as we grow, we'll want to lock things down, have some of those security roles."
Lead developer, public-sector agency
Those roles live in the UI, so they cover people using the UI. Masking follows the same boundary. AKHQ, Kafbat UI, Kpow and Conduktor Console can hide fields from people on screen, while an application reading the topic still gets the full record.
The broker log and the UI's audit log name different users
Kafka's authorizer can log allowed and denied requests with the principal that made them, through the kafka.authorizer.logger in the broker's log4j configuration. With per-person principals and a desktop client, that log names people. With a shared principal, it names the shared account.
Behind a web UI, the broker log names the UI's service account for every action. The record of which person did what has to come from the UI itself:
- AKHQ. Writes changes to a Kafka topic once you turn auditing on: topics created or deleted, records produced, offsets reset. It doesn't record who browsed which data.
- Kpow. Keeps a full audit log on its Enterprise edition.
- Conduktor Console. Records changes, topic browsing (
Kafka.Topic.Browse), produced records and SQL queries on topics, on paid plans.
If the security team asks who read a topic holding customer data, check that the tool records reads before you commit to it.
Conduktor replaced its desktop app with a web UI
Conduktor started as a desktop Kafka client, Conduktor Desktop, and has retired it. Conduktor Console took its place as a self-hosted web UI: it connects with the service account set in its cluster configuration, signs people in through local users, OIDC, SAML or LDAP, and applies permissions down to a topic, consumer group, subject or connector.
Community Edition is free for up to 50 users and 3 clusters, with SSO and basic user permissions. Audit logs, masking, alerting and federated ownership need a paid plan.
Matching the GUI to who uses the cluster
Start from how many people will point the GUI at production:
- One developer, a local or test cluster. A desktop client such as Offset Explorer, or
kcatif you prefer a terminal. There's nothing to host. - A few developers sharing a cluster, no audit requirement. AKHQ or Kafbat UI: one deployment, free, with sign-in through your directory.
- Running Redpanda. Redpanda Console is built for it and works with Apache Kafka too.
- On Confluent Platform. Control Center ships with it.
- Many users on a few clusters. Kpow prices per cluster, with 100 users included on Enterprise.
- Several teams on production clusters, and security asks who read what. Conduktor Console signs people in through SSO, scopes permissions per resource and records topic browsing in its audit log.
What no Kafka GUI does
Each of these needs something besides the GUI, Conduktor Console included:
- Replace application ACLs. A UI's roles govern people in the UI. Services connect with their own principals, and those still need ACLs from the CLI, Terraform or an operator such as Strimzi.
- Change what applications read. Masking in a UI hides fields on screen. Changing the bytes an application receives takes a proxy in the data path, such as Conduktor Gateway.
- Protect the service account for you. A web UI's service account can do everything any of its users can, so whoever reads the server's configuration holds that access.
A desktop GUI client is the right tool for one developer and one test cluster. Once a team shares a production cluster, the security review asks where the credentials live and who read which topic, and a web UI that keeps one service account on one server is the setup that can answer both.
Install Community Edition next to the GUI you use today and compare them on the same cluster.
Is there a desktop GUI client for Kafka?
Yes. Offset Explorer, formerly Kafka Tool, is a desktop application. Conduktor Desktop was one too and has been retired; Conduktor Console replaced it as a web UI.
Does Apache Kafka ship with a GUI?
No. Apache Kafka ships command-line tools only. Every Kafka GUI is a separate project.
Can I run a Kafka web UI on my laptop?
Yes. AKHQ, Kafbat UI and Conduktor Console all run in Docker, so one developer can run them locally and point them at a test cluster.
Do I need a Kafka user for every person?
With a web UI, no: it connects with one service account and applies each person's permissions itself. With a desktop client, the brokers can only tell people apart if each person has their own principal.
Related: Kafka UI: Open-Source vs Enterprise → · Kafka UI Tools Compared → · AKHQ vs Paid Kafka Tools →
