Everything runs on your machine.
Two small pieces, both local, and a direct line to your brokers.
The two parts
Desktop app
A native window with the Kafui interface. It starts the agent for you when it opens and stops it when you quit.
Local agent
A small service bundled inside the app. It listens only on your own machine, holds your saved clusters, and holds the real connections to your Kafka brokers.
How an action runs
- 1. AskYou click something in the app, such as listing topics. The app sends the request to the agent on your machine.
- 2. RunThe agent runs it against your Kafka cluster using the official Kafka clients.
- 3. ShowThe result comes back to the app. Live tails stream in as messages arrive.
Design principles
- Local by default
- There is no Kafui server and no account. Your cluster settings and messages stay on your machine.
- Direct to brokers
- The agent connects to your brokers itself, so it works over your own network or VPN.
- Secrets stay secret
- Saved credentials are encrypted at rest, stored in a file only your user can read, and never returned to the interface.
- Self-contained
- Each installer bundles the interface, the agent and a trimmed Java runtime, so you don't need Java installed.
Built with
- Desktop
- Tauri and Angular
- Agent
- Java with Spring Boot, using the official Kafka clients