One console. Eight messaging protocols.
Follow the message.
Find the answer.
Your events tell a story. See the whole picture. Inspect live messages, understand consumer lag, and bridge brokers with a self-hosted console for Kafka, RabbitMQ, and six more protocols.
An illustrative workspace with sample data. Select a connection to explore.
Different infrastructure. A shared point of view.
One connected workspace
Admin, Dev, ReadOnly
Integrations and agent tools
01 / From symptom to signal
Your brokers are different.
Your questions aren’t.
Did the event arrive? Why is the consumer behind? Where did that message go? Start with the message, then follow the evidence.
See what’s actually moving.
Watch messages across topics. Filter headers and payloads, capture a time window, and export the records you need.
Find where the flow slows down.
Inspect Kafka consumer groups and partition lag. Look beyond a single number to understand where a backlog is building.
Connect the systems you already run.
Bridge messages between brokers with filters and header transformations. Check the result with a dry run before starting.
Give failed messages a way forward.
Inspect dead-letter messages, edit a payload, and redrive at a controlled rate. Keep incident recovery in the same workspace.
02 / Your infrastructure. Your rules.
A console that belongs
in your environment.
Run EventOre alongside your brokers. Choose the providers you need and the access mode that fits the job.
Read the architecture ↗Deploy on your terms.
Docker for a local stack. Helm for Kubernetes. A modular backend lets you include only the stream providers you use.
Choose the right access.
Admin, Dev, and ReadOnly deployment modes define which actions are available in your environment.
Keep sensitive fields out.
Configure field-level masking and redaction for message payloads before they reach the workspace.
Data masking ↗Go beyond the browser.
Use the OpenAPI interface for integrations, or the optional MCP server for agent tools.
MCP integration ↗03 / Make your first connection
Less setup.
More understanding.
Start with the local Docker stack, connect a broker, and open a stream. Moving to Kubernetes? The deployment guide covers images, providers, and Helm values.
git clone https://github.com/vijayptiwari/eventore.git
cd eventore
docker compose -f docker/docker-compose.stack.yml up -d --buildRequires Git and Docker Compose. The first run builds the images.
Open localhost:8088. Connect an existing broker to start streaming.
04 / The right next step
Clarity, from the first connection.
Your first live message.
Build the local stack, connect your broker, and open the stream workspace.
Start the walkthrough ↗02 / Know your platformOne interface. Real differences.
Compare browsing, search, lag, and administration support for each provider.
Explore protocol support ↗03 / Make it yoursA place in your infrastructure.
Choose provider images, configure access modes, and deploy with Helm.
Plan your deployment ↗Learn by doing
One order. Two brokers. A clear path.
Follow a confirmed order from Kafka to a RabbitMQ queue, with a local Docker Compose lab and delivery checks.
Before you begin
A few good questions.
What is EventOre?
EventOre is a self-hosted messaging and streaming console for Kafka, RabbitMQ, Pulsar, MQTT, JMS, AWS Kinesis, GCP Pub/Sub, and Azure Service Bus. It brings connections, live streams, and supported inspection tools into one workspace.
Does every protocol support every feature?
No. Browsing, historical search, administration, and lag inspection depend on the provider and broker permissions. The protocol capability guide explains the differences.
Does EventOre replace my message broker?
No. It connects to your existing brokers. You deploy the console and its backend in your environment, then configure connection profiles for the systems you already run.
How do I choose an access mode?
Admin enables administrative workflows. Dev supports development with publish size limits. ReadOnly disables publishing and connection changes. These are deployment modes; configure broker credentials and API authentication separately. See configuration.
Can I use it with AI agents?
The optional MCP server exposes tools backed by the EventOre API. Deploy and configure it separately when your agent needs access to supported broker operations.
Built in the open. Built to be useful.
Created and maintained by Vijay Prakash Tiwari. Explore the code, report a problem, or help shape what comes next.