// the find
xaecbd/KCenter
KCenter(KafkaCenter) is a unified platform for kafka cluster management and maintenance, producer / consumer monitoring, and use of ecological components(ksql/kafka connect).it's kafkacenter(kafka center).
KCenter is a web UI for managing Apache Kafka clusters — topic management, consumer lag monitoring, Kafka Connect job administration, and KSQL, all in one place. It's aimed at platform/data engineering teams that want self-service topic requests and lag alerting without cobbling together three separate tools. Think of it as a more opinionated, team-aware alternative to CMAK.
The team-based access model is genuinely useful: users belong to teams, topics belong to teams, and approval workflows gate who can create what — that's the actual pain point CMAK ignores. Consumer lag visualization backed by Elasticsearch gives you historical graphs rather than just a current snapshot, which matters when you're trying to understand whether a consumer is recovering or trending worse. The Docker-first deployment with a single config file is low friction. Kafka Connect and KSQL management being in the same UI as topic ops reduces context switching for data pipeline teams.
No SASL or OAuth support for the Kafka connection itself — it says so right in the README, which means you can't use this against any cluster with security enabled, ruling out most production environments. The frontend is compiled static JS with numeric filenames (0.js, 1.js, 24.js) and no source maps in the repo, so the UI is effectively a black box if something breaks. The last meaningful commit activity and the 'commercial products have better functions' note in the README signals that the open-source version is a feature-limited lead-gen vehicle, not a fully maintained project. Elasticsearch is required for monitoring, which is a heavy dependency to add just for lag history.