Confluent Control Center vs Lenses

Confluent Control Center vs Lenses, compared

F1 Confluent Control Center and Lenses, side by side

Confluent Control Center Lenses

Pricing unit The Confluent Platform enterprise licence, which Confluent does not publish. Control Center, multi-tenancy and encryption are each billed above the base. Two published ladders: DevX by capability and user count from 4,000 US dollars a year at Team, and K2K replication from 1,000 US dollars a month.

Adding an engineer No change. The unit was never people. Community stops at five users and Team at fifteen. A sixteenth is custom priced.

Free tier None. A time-limited Confluent Platform evaluation is the only route in. Community, free, with basic authentication, no SSO and no RBAC, carrying the same Postgres dependency as the paid tiers.

Which clusters it connects to Confluent Platform only. The brokers have to carry a proprietary reporter JAR, which MSK, Redpanda and Aiven do not permit. Any Kafka. The agent is a standard client, so nothing changes on the broker side.

What has to be deployed Dedicated nodes that cannot share a host with the platform packages, sized at 4 cores, 8 GB of memory and 200 GB of disk for a 100,000-replica cluster. A central HQ on PostgreSQL, plus an agent and a database of its own for every cluster.

Capabilities unique to it Kafka Streams topology visualisation, and ksqlDB development in place. SQL Studio, which puts a query in front of a topic for somebody who does not write consumers.

Upgrading the tool Legacy to next generation is a migration: metrics history is left behind, and the two architectures run in parallel for 7 to 15 days. One HQ instance, replaced rather than rolled, so the control plane is offline for the length of it.

What leaving costs Broker-side work. The reporter JAR, and interceptors on the legacy architecture, have to be removed deliberately. SQL Processors are proprietary and compiled. Stream Reactor connectors are open source and survive the move.

Key takeaway

Control Center only reaches brokers running Confluent Platform, because the proprietary reporter it depends on cannot be installed on Amazon MSK, Redpanda or Aiven, and it carries no price of its own, arriving inside an enterprise licence Confluent does not publish. Lenses reaches any of those clusters instead, and publishes two ladders: DevX starts at 4,000 US dollars a year at Team, though it puts a Postgres database behind HQ and behind every per-cluster agent. Kpow by Factor House is licensed per cluster at a published price.

What is Confluent Control Center?

Control Center is a web management and monitoring interface bundled with Confluent Platform, Confluent’s commercial Kafka distribution. It is closed source, it arrives under an enterprise licence, and it is not available on its own. One dashboard covers brokers, topics, consumer groups, Kafka Connect workers, Schema Registry, ksqlDB and Kafka Streams topologies. The current release line is 2.6.x, and 2.6.0 shipped on 14 July 2026.

Kafka publishes its own metrics over JMX, and a console reads them rather than producing them, which is why the prerequisite matters more than the screens do. Control Center needs the proprietary Confluent Metrics Reporter JAR in the broker classpath, and that JAR cannot be installed on Amazon MSK, Redpanda or Aiven. That is what the product is rather than a shortcoming of it: it is the console for a distribution.

• Legacy architecture: a Kafka Streams metrics pipeline, shipped with 7.x and earlier.
• Next generation: Prometheus-based, generally available with Confluent Platform 8.0 in May 2025.
• What changed: startup fell from 15 to 50 minutes to about one, and supported partition scale rose from 120,000 to 400,000.
• Unmatched: Kafka Streams topology visualisation and native ksqlDB development.

What is Lenses?

Lenses is a commercial Kafka governance and data exploration platform that sits on top of clusters you already run. It operates as a Kafka client and does not sit in the data path. The architecture is a central Lenses HQ node with lightweight agents deployed one per cluster, and because an agent connects as a standard Kafka client, a KRaft cluster needs no modification to be reached. Celonis acquired Lenses in early 2022, and 6.2.6 shipped on 19 August 2026.

• SQL Studio: a SQL interface for querying topics without writing consumer code, aimed at people who are not Kafka-savvy.
• Topology and lineage: one picture across producers, topics, connectors and consumers.
• SQL Processors: Kubernetes-native stream processing defined in SQL and built on Kafka Streams.
• Portability: those processors are proprietary and compiled, which is the part that is hardest to leave.

What is the official 2026 pricing of Confluent Control Center and Lenses?

Control Center is not sold on its own. It arrives with a Confluent Platform enterprise licence, and Confluent does not publish a price for it. Control Center, multi-tenancy support and encryption each carry cost above the base licence, and the unit is the platform rather than a cluster or a seat, so it cannot be bought for a cluster somebody else runs. The Enterprise licence covers quarterly patch updates for the current version only, and the Platinum support tier is not available for this product.

Lenses publishes two ladders. DevX is tiered by capability and user count: Community is free and reaches five users with basic authentication, no SSO and no RBAC; Team starts at 4,000 US dollars a year, caps at fifteen users, and adds SSO, SAML, RBAC and team support; Multi-Kafka Enterprise is custom priced. K2K replication is a second meter, from 1,000 US dollars a month with five clusters included and additional clusters at 200 US dollars a month. For a team of five that needs SSO, Lenses is 4,000 a year on the first day. For a team of fifty, Lenses is past the Team cap and into a sales conversation, while Control Center’s bill has not moved on headcount at all.

Where does each one run out?

Control Center’s limits begin where Confluent Platform ends. MSK’s native IAM authentication is not supported, and neither is SAML SSO for self-managed deployments, where OIDC is the only protocol.

• RBAC: no metrics-only mode. Full management has to be enabled, which is all or nothing.
• Footprint: dedicated nodes, never sharing a host with Confluent Platform packages, at 4 cores, 8 GB of RAM and 200 GB of storage for clusters up to 100,000 replicas.
• Upgrades: legacy to next generation is a migration. Historical metrics do not carry over, and 7 to 15 days in parallel is recommended.
• Alerting: plenty of teams run Prometheus and Confluent’s own Grafana dashboards for production alerting even where Control Center is deployed.

Lenses puts its cost in the control plane. HQ requires PostgreSQL and it is the only supported storage option. Each agent needs its own database as well, and an agent connects to one Kafka cluster at a time, so a four-cluster estate is one HQ, four agents and five databases. The Community edition carries the same dependency.

• Availability: the Helm chart pins replicas to 1 as a literal and sets the update strategy to Recreate, so an upgrade takes the control plane down.
• 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.
• Reach: one agent per cluster, so the component count climbs with the estate.

Which should you pick?

Pick Control Center if:

• the estate is Confluent Platform and is going to stay that way
• the licence is already paid
• a Kafka Streams topology or a ksqlDB query under development is what you need to see

Pick Lenses if:

• the estate is mixed, or is not Confluent at all
• the people who need the tool are not all Kafka engineers
• a SQL query should replace a search through raw JSON, Avro or Protobuf payloads

Be honest about the price of the second: Postgres for each component, an agent for each cluster, and a control plane that goes down during its own upgrade. The question underneath both is whose Kafka this is. If the answer is Confluent Platform, both are available and the comparison is real. If it is anything else, only one of them is.

Kpow: a bill that tracks the cluster, not the distribution or the org chart

Control Center and Lenses each price something other than the cluster in front of you. Control Center’s unit is the Confluent Platform licence, so the bill answers to a distribution you have committed to, not to the clusters underneath it, and it never reaches Amazon MSK, Redpanda or Aiven. Lenses’ unit is the user count: Team caps at fifteen users for 4,000 US dollars a year, a sixteenth person moves the whole team into a custom-priced conversation, and that is before the Postgres database behind HQ and another behind every per-cluster agent. Kpow by Factor House is licensed per cluster at a published price, so neither a distribution commitment nor a growing headcount changes it. It is a single stateless JVM container with no external database, running on top of a cluster you already operate.

A bill that tracks the clusters you run, not the distribution you’re locked into or the team you hire, is worth comparing on your own numbers. Start with Kpow on that cluster and see.

Sources

• Apache Kafka documentation on monitoring
• Apache Kafka documentation on authorization
• Apache Kafka documentation on basic operations

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