Lenses vs Offset Explorer

Lenses vs Offset Explorer, compared

F1 Offset Explorer and Lenses, side by side

Offset Explorer Lenses

Pricing unit A purchase per named user: 139 US dollars for 1 to 10 users, 128 for 11 to 20, and 119 for 21 to 50, plus 46 per licence a year after the first 365 days. Capability tiers with user caps, on two ladders: DevX for the platform, and K2K for replication.

Free route Free for personal use with no time limit, and a 30-day evaluation for everything else. Community, free for up to 5 users with Basic Auth, no SSO and no RBAC. It installs Postgres before it starts.

What governance costs Nothing is on sale, because nothing authenticates a person to the application. SSO, SAML and RBAC arrive at DevX Team, from 4,000 US dollars a year for up to 15 users.

What has to be deployed An installer on each engineer's machine. Windows and macOS builds carry a bundled JRE; the Linux build needs Java 21 or later first. A central HQ node with PostgreSQL as its only supported store, plus one agent and one agent database per Kafka cluster, on the free tier too.

Adding an engineer Another licence at the band rate. A shared machine needs one per person on it. Nothing until a cap is reached, at 5 users on Community and 15 on Team. A team of 16 is custom priced.

Where the configuration lives On each workstation. Connections export and import as files. In the control plane, shared by everybody who logs into it.

Automation A command line tool covering export, import, data generation, message search and cluster comparison against a saved project file. SQL Studio for queries, and SQL Processors compiled and run on Kubernetes.

What leaving costs An uninstall on each machine. Saved messages and exports are already ordinary files on local disk. It connects as an ordinary Kafka client, so removing it changes no client configuration. SQL Processors are proprietary and compiled.

Key takeaway

Offset Explorer is a purchase per named user at 139, 128 or 119 US dollars by band, plus 46 for each year after the first, and Lenses DevX Team starts at 4,000 US dollars a year for up to 15 users. Both are free for somebody, and not the same somebody: Offset Explorer for personal use, Lenses Community for up to 5 users with no RBAC. Offset Explorer, renamed from Kafka Tool, installs on each engineer’s machine; Lenses is a central control plane with an agent on every cluster. Kpow by Factor House is licensed per cluster.

What is Offset Explorer?

Offset Explorer is a GUI application for managing and using Apache Kafka clusters, published by DB Solo, LLC, and installed on an engineer’s own machine rather than deployed as a service. It runs on Windows, Linux and macOS. The Windows and macOS builds carry a bundled JRE, so installation is a single download; the Linux build needs Java 21 or later on the machine first.

• Payloads: shown as hex or UTF-8, and pretty-printed as JSON or XML.
• Search: string, binary, Avro, Protobuf, JSON Schema, regular expressions and JsonPath.
• Integrations: Schema Registry, Kafka Connect and ksqlDB.
• Command line tool: exportMessages, importMessages, generateData, scriptGenerator, findMessages and compareClusters against a saved project file, with real exit codes.

Where a payload format is proprietary, a Java class implementing ICustomMessageDecorator2 ships as a jar into the installation’s plugins folder and is selected per topic. The ACL commands live in the command line tool rather than the main interface.

What is Lenses?

Lenses is a commercial Kafka governance and data exploration platform that sits on top of clusters somebody else runs. It connects as an ordinary Kafka client rather than a proxy, so nothing sits in the data path and a KRaft cluster needs no modification. The architecture is a central Lenses HQ node with lightweight agents deployed per cluster, and one agent reaches one Kafka cluster. Celonis acquired the company in 2022, and 6.2.6 was released on 19 August 2026.

• SQL Studio: queries a topic instead of writing a consumer to trawl millions of JSON, Avro or Protobuf records.
• SQL Processors: stateful and stateless rules defined in SQL, built on Kafka Streams and run on Kubernetes.
• Identity: SSO and SAML, RBAC, and built-in roles where Operator and Security Admin are distinct from Admin.
• Audit: logs on the 6.2.6 line carry principal delegation.

What is the official 2026 pricing of Lenses and Offset Explorer?

The two published ladders are not the same kind of object. Offset Explorer is a purchase: 139 US dollars per user for 1 to 10 users, 128 for 11 to 20, and 119 for 21 to 50, with 365 days of support and maintenance included, renewing at 46 US dollars per licence for a further 12 months. Lenses DevX Team starts at 4,000 US dollars a year for up to 15 users.

Ten engineers on Offset Explorer is 1,390 US dollars to buy and 460 a year to stay current, against 4,000 a year on Lenses. Fifty engineers on Offset Explorer is 5,950 US dollars and 2,300 a year; fifty on Lenses is past the 15-user Team cap and becomes a Multi-Kafka Enterprise agreement priced by negotiation. Free means a different thing on each side: Offset Explorer is free for a person, with personal use unlimited in time and a 30-day evaluation for anything else, and Lenses Community is free for a deployment, up to 5 users with Basic Auth, no SSO and no RBAC. There is a second Lenses meter too: exactly-once replication, offset replication or schema migration puts a team on the K2K ladder on top of DevX, from 1,000 US dollars a month with five clusters included and 200 a month for each cluster after.

Where does each one run out?

Offset Explorer’s load-bearing limit is identity. The documented authentication is client to broker only: plaintext, SASL over plaintext or SSL with a JAAS configuration, SSL with a truststore and optional client certificates, and OAUTHBEARER. Nothing authenticates a person to the application, so there is no user identity for a role model to key on and no server-side audit log to read.

• Configuration: the cluster list lives on each workstation, and connections export and import as files, so nothing keeps two people in step.
• Plugins: a jar copied into an installation directory, so a decoder lands one machine at a time.
• ACLs: available from the command line tool rather than the main interface.
• Bill: tracks headcount, with maintenance a separate annual charge on every licence.

Lenses runs out on the control plane, which is wider than it first looks: HQ plus its Postgres, which is the only supported store, plus one agent and one agent database for every Kafka cluster, so a four-cluster estate is HQ, four agents and five databases. The Community edition carries the same dependency.

• Availability: the published Helm chart runs a single HQ replica and exposes no way to run a second, and its default update strategy is Recreate.
• Masking: data policies match on field name across every registered dataset and are global, with no escape even for an admin.
• Permissions: 6.2.5 split UpdateTopicDetails into two actions, so custom roles granting the old one needed re-granting by hand.
• Weight: a server-side JVM backend runs alongside the web interface, which is heavy for one local topic.

Which should you pick?

Pick Offset Explorer if:

• it is one engineer, one laptop, several clusters, and the work is today
• the hunt is for a single bad record across Avro, Protobuf, JSON Schema or JsonPath
• the repeatable work is a CI step rather than a service

Pick Lenses if:

• people who will not write consumer code need to answer their own questions
• somebody has asked who can see what
• continuous transformation defined in SQL is part of the plan

The middle case is structural rather than a feature count: one product sells identity, with SSO, RBAC, roles that separate duties and an audit trail, and the other has no concept of a person to attach any of that to. Count the deployment into the price, though, because that is a database for HQ and one for every agent. On automation, Offset Explorer’s command line tool replays a saved project from a shell and exits 0 or nonzero, and SQL Processors run continuously on Kubernetes: one is a script and the other is a service.

Kpow: a bill that does not grow with headcount

Offset Explorer and Lenses both size the invoice to how many people are logged in, not to how many clusters are being run. Offset Explorer charges per named user on a three-band ladder, 139 US dollars in the 1-to-10 range, 128 in the 11-to-20 range and 119 above that, so a shared machine still needs a licence for every person who uses it. Lenses caps by tier instead of by seat, five users free on Community and fifteen on DevX Team, before a sixteenth person forces a Multi-Kafka Enterprise agreement priced by negotiation, on top of a central HQ node and PostgreSQL that Community carries too. Kpow by Factor House is licensed per cluster, so a team of five becoming a team of fifty does not change it. It runs as one stateless container on top of whatever Kafka the team already has, rather than running the broker itself.

Headcount already decides two bills here. Start on Kpow and see whether a per-cluster price fits your headcount better than either of these licences would.

Sources

• Apache Kafka documentation on authorization and ACLs
• Apache Kafka documentation on basic operations
• Apache Avro documentation

Related reading

• Integrate Confluent-compatible registries in Kpow
• Kafka consumer monitoring and performance tuning
• Integrate Kpow with Redpanda Streaming Platform
• Accelerating incident response with AI queries