Kafbat UI vs Offset Explorer

Comparisons

Factor House·August 30, 2026·6 min read·Updated August 31, 2026

Kafbat UI vs Offset Explorer, compared

F1 Kafbat UI and Offset Explorer, side by side

Kafbat UI Offset Explorer

Pricing unit Free under Apache 2.0, with no seat cap, no cluster cap and production use permitted. A purchase per named user, plus an annual maintenance renewal.

One engineer Free, and a container somebody has to run. 139 US dollars in the 1 to 10 user band, with 365 days of support included, then 46 a year.

Twenty engineers Still free, and still one deployment. 128 US dollars per user in the 11 to 20 band, so 2,560 once and then 920 a year.

Who the tool authenticates A person. Roles scoped per resource type with regular-expression subjects, over OAuth, LDAP and Active Directory. The connection only. No login, no single sign-on and no OIDC against the product itself.

Masking and audit Server-side masking with remove, replace and mask policies, and an audit log written to a Kafka topic. Neither is in the product.

What it needs to run A container computing its views from the cluster, with a published Helm chart, and one deployment reaching many clusters. Nothing server-side. Windows and macOS builds bundle a JRE, the Linux build wants Java 21 or later, and connections are configured on each workstation.

Message decoding JSON, plain text and Avro, with custom serialiser and deserialiser plugins. String, binary, Avro, Protobuf, JSON Schema, regular expressions and JsonPath, with a Java plugin interface for anything else.

Support No commitment from the project. Professional services are quoted rather than listed, and a published vulnerability is remedied by an upgrade the operator performs. 365 days at purchase, then 46 US dollars per licence a year covering upgrades with email and phone support.

Both products as published in August 2026.

Key takeaway

Kafbat UI and Offset Explorer both put a screen in front of an Apache Kafka cluster somebody else runs; one is a web application deployed once for a whole team, the other installed on each engineer’s machine. Kafbat UI is the maintained continuation of the project many call Kafka UI, and costs nothing; the cost instead is a container somebody deploys and patches. Offset Explorer costs 139, 128 or 119 US dollars per named user by band, plus 46 a year, and nothing authenticates a person to it. Kpow by Factor House is licensed per cluster at a published price.

What is Kafbat UI?

Kafbat UI is a free, open-source web dashboard for observing and managing Kafka clusters, licensed Apache 2.0 with no source-available restriction on production use. It is deployed as a container rather than installed per engineer, and one deployment reaches many clusters. It is the maintained continuation of the Provectus kafka-ui project, whose last release, v0.7.2, was April 2024 and which has taken no commit since that July. CVE-2023-52251 records remote code execution through the message filter parameter on versions 0.4.0 through 0.7.1 of that lineage.

Cluster view: topic insight with partition count and replication status, a broker overview with partition assignments and controller status, and multi-cluster management.
Consumer groups: parked offsets, and both combined and per-partition lag.
Messages: a browser for JSON, plain text and Avro, with custom serialiser and deserialiser plugins.
Integrations: cloud IAM for GCP, Azure and AWS, a Swagger UI over its own API, and an MCP server from v1.3.0.

Role-based access control, server-side data masking and the audit log are all in the free product, because there is no paid product to put them behind. Releases run from v1.0.0 in March 2024 to v1.5.0 in April 2026.

What is Offset Explorer?

Offset Explorer is a graphical application for managing and using Kafka clusters, installed on an engineer’s own machine rather than deployed as a service. It runs on Windows, Linux and macOS, with a bundled JRE on the first two, and the Linux build wants Java 21 or later first. It was renamed from Kafka Tool, and the vendor’s domain still carries the old name. It supports Apache Kafka 0.11 and above.

Search: string, binary, Avro, Protobuf, JSON Schema, regular expressions and JsonPath.
Command line tool: replays a saved project file with real exit codes and text, JSON, XML or CSV output, and carries listAcl, addAcl and deleteAcl.
Plugins: a custom Java plugin implementing a two-method interface decodes a payload format the product does not natively understand.
Integrations: Schema Registry, Kafka Connect and ksqlDB, plus a documented Compare Clusters tool. KRaft quorum support arrived at 4.0.3.

What is the official 2026 pricing of Kafbat UI and Offset Explorer?

Offset Explorer counts people rather than machines. The published ladder is 139 US dollars per user at 1 to 10 users, 128 at 11 to 20, and 119 at 21 to 50, with no published price above that. Every purchase includes 365 days of active support and maintenance, and a further 12 months costs 46 US dollars per licence. Twenty engineers is 2,560 US dollars once and 920 a year after. A shared machine needs a licence for every person who uses it. Personal use is free with no time limit, and commercial, educational and non-profit use all need a purchased licence after a 30-day evaluation.

On the other side there is no seat cap, no cluster cap and a licence that permits production use. What it costs instead is a container somebody deploys, monitors, upgrades and holds the pager for, plus whatever support arrangement gets negotiated. That is the crossover: for five engineers the paid tool is a small purchase and the free one is a container somebody has to own, and for fifty the paid bill has grown with every hire while the free one has not moved at all.

Where does each one run out?

Kafbat UI’s patching is yours. Three published remote code execution records exist across the two lineages, one of them exploitable by any unauthenticated user. CVE-2025-49127 is an unsafe deserialisation flaw in v1.0.0 scored 8.9 HIGH on CVSS v4.0 and fixed in v1.1.0. The project publishes no support commitment of its own and no price for its professional services. The feature list names topic creation and dynamic topic configuration, and no partition increase, no broker addition, no rebalancing and no alerting.

Metrics: the dashboard is live and nothing stores a time series behind it. Graphed lag or throughput over days is still an open feature request.
Audit defaults: modifications only until an operator raises the level, on a topic that defaults to one partition and must not be compacted.
Dynamic config: anything configured through the wizard is written inside the container and lost on restart without a mounted volume.

Nothing authenticates a person to Offset Explorer. The documented authentication is client to broker only: SASL over plaintext or SSL, SSL with a truststore and optional client certificates, and OAUTHBEARER. There is no login, no single sign-on and no OIDC against the product itself, so there is no user identity for a role model or an audit trail to key on. Authorisation is a cluster concern a client surfaces rather than owns, so the tool can add and remove ACLs from a shell and still know nobody’s name.

Shared record: no shared deployment to operate, nothing server-side to log, and no single place to see what an engineer did.
Configuration: per workstation, exported and imported as files, so nothing keeps two people in step.
Plugins: a jar copied into the installation directory, effective after a restart, so a decoder lands one workstation at a time. KRaft appears once in the vendor’s change history and never in the documentation set.

Which should you pick?

Pick Kafbat UI if:

more than a handful of people need to see the cluster
somebody will eventually ask who has access to which topics
payload fields have to be obscured before they reach a screen
the cost of adding an engineer matters

Pick Offset Explorer if:

the tool is for a small number of engineers who already hold cluster credentials
the work is deep inspection of awkward payloads rather than delegated access
nobody is going to ask who looked at what
a support contract included in the first year is worth more than a container nobody wants

The question underneath both is who the tool is for. Five people who all hold broker credentials anyway make either one work, and the choice comes down to payload handling and whether anybody wants to run a container. Fifty people, most of whom should never touch a broker, make access control the thing being bought, and one of these gives it away while the other does not sell it at all.

Kpow: one price per cluster, not per seat

Neither of these prices the actual unit of a Kafka deployment, the cluster. Kafbat UI is free to license, but three published remote-code-execution CVEs sit across its two lineages and the project makes no support commitment, so patching, deploying and holding the pager for the container stays with whoever runs it. Offset Explorer prices per named user instead, 139, 128 or 119 US dollars by band, so the bill climbs at every hire whether or not that hire touches a second cluster. Kpow by Factor House is licensed per cluster at a published price, so an extra engineer changes nothing on the invoice. It runs as a single stateless JVM container configured through environment variables, with no external database, no sidecar and no persistent volume.

Both bills above skip the unit that is actually scaling: the cluster itself. That per-cluster price is worth checking on Kpow’s own page before either alternative’s bill catches up with headcount.

Sources

Apache Kafka documentation on authorization
NVD record for CVE-2025-49127
NVD record for CVE-2023-52251
NVD record for CVE-2024-32030