KubeMQ Documentation
Kubernetes-native enterprise message broker. Connect existing Kafka, RabbitMQ, MQTT, SQS, and Pub/Sub clients unchanged — or build with SDKs in 10 languages.
One broker. Every protocol. KubeMQ is a Kubernetes-native enterprise message broker. It runs as one container on Docker or Podman for development and testing, or as an operator-managed cluster of 3 or more servers on Kubernetes. Your existing Kafka, RabbitMQ, MQTT, AMQP, STOMP, AWS SQS/SNS, and Google Cloud Pub/Sub clients connect to it unchanged — and native SDKs in 10 languages give you queues, pub/sub, and request-reply over gRPC, REST, and WebSocket. No ZooKeeper, no external database, no sidecars.
Try KubeMQ in 5 minutes
Install kmq, start a server, send your first message.
Migrate from your broker
Keep your Kafka, RabbitMQ, SQS, or MQTT code — change one connection string.
What brings you here?
Start fresh
Choose kmq, Docker or Kubernetes and install the latest release.
Migrate an existing system
Point your existing messaging clients at KubeMQ — no rewrite, no new SDK, no bridges.
Build an application
Native SDKs for Go, Java, C#, Python, TypeScript, C++, Kotlin, Ruby, Rust, and Elixir — plus framework integrations.
Operate a cluster
Configure, secure, monitor, and scale KubeMQ in production.
Keep your clients — change one connection string
KubeMQ speaks each protocol natively, on its standard port. The client that talks to Kafka or RabbitMQ today talks to KubeMQ tomorrow.
Kafka
Producers, consumer groups, transactions, Kafka Connect and Streams. On by default, no flag needed.
RabbitMQ
Exchanges, queues, bindings, dead-lettering — AMQP 0-9-1. On by default, no flag needed.
AMQP 1.0 / JMS
Qpid JMS, go-amqp, AMQP.Net Lite, message selectors.
MQTT
MQTT 3.1.1 and 5.0, QoS 0/1/2, shared subscriptions.
STOMP
STOMP 1.0–1.2 with receipts, heartbeats, and request-reply.
AWS SQS / SNS
Point your AWS SDK or CLI at KubeMQ — queues, topics, FIFO.
Google Cloud Pub/Sub
Official Google client libraries, ordering, filters, snapshots.
CloudEvents
Native HTTP endpoint for structured and binary CloudEvents.
Built on four messaging patterns
Every protocol and every SDK rides the same core patterns.
Events
Fire-and-forget pub/sub for real-time broadcasting to multiple subscribers.
Events Store
Persistent pub/sub with replay, retention policies, and consumer groups.
Queues
Point-to-point messaging with guaranteed delivery, acknowledgment, and dead-letter queues.
RPC
Request-reply messaging for commands (execute and confirm) and queries (request data).
Why teams choose KubeMQ
- Built for Kubernetes — Helm charts and an operator, KEDA autoscaling, and clustering designed for safe rollouts.
- Enterprise-grade — role-based access control, audit logging, FIPS builds, and replicated storage with a strict zero-loss durability mode.
- AI-ready — built-in Model Context Protocol (MCP) and Agent-to-Agent (A2A) gateways for agentic workloads.
- Simple to run — one container, a web dashboard, and the kmq CLI for installing, messaging, administration, and observability.
Explore the documentation
Deploy
Install KubeMQ locally, with Docker, or on Kubernetes.
Licensing
Plans compared, how licensing works, data sent to KubeMQ, troubleshooting.
Configure
Server configuration, security, and storage.
Operate
Dashboard, monitoring, clustering, and day-2 operations.
Learn
Messaging patterns, concepts, and guided tutorials.
AI Way
MCP and A2A — connect LLM hosts and build agent workflows.
Client SDKs
Native libraries for 10 languages, with examples for every pattern.
Connectors
Protocol compatibility — Kafka, RabbitMQ, MQTT, AMQP, and more.
Integrations
Frameworks and platforms: Spring Boot, NestJS, KEDA, and beyond.
Release notes
What changed in each KubeMQ release — features, breaking changes, upgrades.
Questions? Open an issue on GitHub or Contact KubeMQ. Ready for production? Buy a license. Building with AI agents? This site ships llms.txt for machine consumption.
Was this page helpful?