[abledon]

CMAK, AKHQ, Kafdrop, Kowl, Conduktor, Kafkatool etc.... why are there so many attempts to build a kafka UI? Does each one have its own use case? I'd think that something as large as "Kafka" in the software ecosystem would have a goto defacto standard UI for managing it.

[weeco]

You are absolutely right, there are many options which we looked at before we began with the project. None of existing solutions provided the features we needed:

Authentication and authorization to meet our compliance needs, a satisfactory UI/UX, message streaming with JavaScript filters and a couple more features. We thought we can do better and just started hacking something. There's a lot more to come. I'll create a blog post describing in more detail why we've created Kowl.

[vogtb]

Having looked into a couple of these, it seems like they each have their own sort of focus, which makes sense. From my own experience, and talking to other engineers, companies use kafka for: an http replacement that lets subscribers have down time, a way to record and replay time series data, a tool for buffering to some async path, or general pub-sub event bus. Sometimes all of these at once! Each one has it's only operational patterns, so having UIs that focus on these patterns sorta clicks with me.

That said, it's been a while since kafka gained popularity, so it's surprising we've not seen any coalesce into a main contender.

[tutfbhuf]

There are also many different UIs for kubernetes.