Why I built a Apache Kafka Explorer that doesn't need Docker or Java?

Kafka is powerful, but inspecting it shouldn't be painful.

We’ve all been there: trying to debug a message flow and having to deal with complex CLI commands, heavy enterprise tools, or spinning up massive Docker containers just to see what's inside a topic.

I wanted something faster, lighter, and more intuitive. That’s why I’m building StreamLupe.

What is StreamLupe?

StreamLupe is a productivity-focused tool designed for developers who work with Apache Kafka daily. It’s not just another GUI; it’s a lightweight environment to visualize, filter, and manage your streams without the overhead.

Key Features that save me time:

• Real-time Streaming: Watch messages as they arrive with clear visibility over keys, headers, and metadata.
• SQL-powered Queries: Sometimes "Search" isn't enough. I've integrated a SQL console so you can query topics using familiar syntax and export results to JSON or CSV.
• One-click Local Kafka: This is a personal favorite. You can spin up a local broker (KRaft or Zookeeper mode) directly within the app. No Docker, no YAML mess—perfect for quick local testing.
• Zero Dependencies: It’s a native experience. You don't need to install Java or Docker to run StreamLupe itself.

Why not just use [Existing Tool]?

Most tools out there fall into two categories: they are either too basic (CLI) or way too "enterprise" (resource-heavy and complex). StreamLupe aims for the sweet spot: the power of a SQL engine with the agility of a native desktop app.

Current State & Roadmap

The first public version is live for Windows (Installer/Portable) and Linux (AppImage). I’m currently working on:

• macOS support (coming soon!)
• Schema Registry integration
• More advanced data visualization formats

I’d love your feedback!

As developers, our workflow is everything. I'd love to hear from the dev.to community:

1. How do you currently inspect your production Kafka topics?
2. What is the biggest "pain point" in your current Kafka GUI?
3. Would having a built-in local Kafka broker change how you prototype?

Check it out at: 🔗 streamlupe.com