Declarative deployment
Helm charts and a KubemqCluster resource configure protocol connectors, services and subsystems.
On-premises, private cloud, hybrid and edge environments.
KubeMQ V3
Your messaging.
Your infrastructure.
Keep the protocols your applications use. Run them on a self-managed, Kubernetes-native messaging platform built for predictable costs and direct infrastructure control.
V3.1.4 August 2026
The clients you already use
KafkaRabbitMQMQTTAMQP / JMSSTOMPSQS / SNSGoogle Pub/SubCloudEvents
Direct protocol connections
KubeMQ V3
Messaging · Replication · Management
Your Kubernetes environment
On-premises · Private cloud · Hybrid · Edge
Protocol Compatibility
Familiar clients. A new foundation.
V3 speaks messaging protocols directly inside the broker. Explore the capabilities and constraints that matter to your workloads.
KafkaNative wire protocol
Idempotent producers, consumer groups, offset management, multi-partition topics and transactions with exactly-once semantics. Log compaction and time-based retention support Kafka Connect and Kafka Streams workloads.
Requires the next storage engine. Share groups are a preview capability. KIP-848 and Kerberos are not supported; replication factor is cluster-managed.
RabbitMQAMQP 0-9-1
Direct, fanout, topic and headers exchanges; queues, bindings, publisher confirms, dead-letter exchanges, prefetch and virtual hosts. Connect with existing RabbitMQ clients and tools.
AMQP 0-9-1 transactions are not supported.
AMQP / JMSAMQP 1.0
Credit-based flow control, settlement, durable subscriptions, dynamic nodes, request/reply and JMS message selectors. Compatible with Qpid JMS, go-amqp and AMQP.Net Lite.
AMQP 1.0 and AMQP 0-9-1 share a port with automatic protocol detection.
MQTT3.1.1 / 5.0
QoS 0, 1 and 2, shared subscriptions, last-will messages, MQTT 5 user properties and request/response.
Retained messages are not supported. The broker advertises this to connecting clients.
STOMP1.0 / 1.1 / 1.2
All three acknowledgment modes, receipts, heartbeats and request/reply. Destinations map directly to KubeMQ messaging patterns.
STOMP transactions and selectors are not supported.
AWS SQS / SNSExisting AWS SDKs
Point your AWS SDK or CLI at KubeMQ. Use SQS long polling, visibility timeouts and FIFO queues with content-based deduplication, plus SNS topics, subscriptions and filter policies.
Signature-V4 authentication is supported.
Google Pub/SubCompatible gRPC surface
Official client libraries connect through an emulator-compatible interface: publish, pull, streaming pull, ordering keys, filters, dead-letter handling, seek, snapshots and Avro/Protobuf schema validation.
CloudEvents1.0
Publish structured and binary CloudEvents into any KubeMQ pattern over HTTP. Consume through server-sent events with resume support and route by message content using CESQL.
The native CloudEvents endpoint is enabled by default.
Other protocol connectors are enabled individually in configuration. External connector containers remain available for integrations such as databases and caches.
Four native patterns. Still here.
The gRPC, REST and WebSocket APIs continue alongside the new protocol support.
- Durable Queues
- Pub/Sub Events
- Events Store
- Commands / Queries
Self-Managed Kubernetes-Native Operations
Run on your infrastructure. Operate through Kubernetes.
Deploy KubeMQ in your own Kubernetes environment, with control over configuration, rollout and recovery.
Predictable lifecycle
Separate readiness and liveness probes, pod-aware identity and graceful shutdown support controlled rollouts.
Safe node recovery
Explicit node replacement brings a returning node back as a learner until it catches up with the cluster.
Enterprise Reliability & Security
Protect your messages. Control access to your platform.
The new Raft-based storage engine makes the durability contract explicit, with quorum replication and two acknowledgment modes.
Strict
Quorum + diskAcknowledgment follows quorum replication and a disk write, protecting acknowledged messages through node crashes.
Receive→Replicate & persist→Acknowledge
Fast
Default modeAcknowledgment follows quorum replication. Disk synchronization completes within a bounded background window.
Receive→Replicate→Acknowledge
Disk sync follows in the background.Two engines. An explicit choice.
The existing legacy engine remains supported. Kafka requires the next engine; other connectors and native patterns work on both. Moving between engines requires a planned migration. Native retention limits are currently enforced only on the legacy engine.
Enterprise security
Control access.
Trace the changes.
Management-plane roles, service accounts and API keys sit alongside TLS/mTLS, JWT and OIDC authentication. Audit events are queryable through the API, CLI and dashboard.
- Read-only, read-write and admin roles
- Dedicated FIPS builds
- Vulnerability-scanned images and signed CLI checksums
Management authentication and RBAC must be enabled in configuration.
Management & Observability
See what is happening. Control what changes.
Inspect cluster activity, manage configuration and trace operational events through the dashboard, API and kmq CLI.
Management console
Inspect cluster health and replication, use dedicated per-protocol consoles and edit live configuration with role gating and revert support.
Channel monitoring and six interface languages.
Traces and metrics
Export traces and metrics through OpenTelemetry over OTLP. Durable counters survive restarts, while per-connector metrics reflect each protocol’s operating model.
OpenTelemetry is opt-in.
Auditable operations
Search audit events through the API, CLI or dashboard. Use the kmq CLI for messaging, diagnostics and cluster administration.
Audit logging is enabled by default.
AI Agents / Aiway
One fabric for agents, LLMs and messaging.
KubeMQ Aiway connects AI agents through an enterprise messaging foundation. Register capabilities, discover the right agent, invoke it and stream results through A2A or MCP.
Keep your agents simple
Agents remain HTTP services using JSON-RPC 2.0, with optional server-sent events. The Agent Bridge handles broker communication, so agents need no KubeMQ SDK or special runtime.
Two ways into one fabric
A2A supports agent registration, discovery and invocation. MCP gives LLM hosts access to agent orchestration and messaging through one endpoint.
Operate with control
A replicated registry, authentication, ownership rules and request limits support reliable operation across the cluster.
See every interaction
Per-agent request, error, latency and active-stream metrics, together with a live dashboard, help teams monitor their agents.
Bring your protocols.
Let’s check the fit.
Tell us what you run and where it needs to live. We’ll help assess compatibility, economics and the path to KubeMQ V3.