Solutions
Start with your challenge.
Find your path with KubeMQ.
From growing messaging costs to infrastructure requirements, explore how KubeMQ fits the workloads and environments your team runs.
High-Volume Messaging Cost Reduction
Grow your workloads.
Plan your messaging spend.
For teams whose message volumes are growing faster than their budgets.
KubeMQ’s fixed-cost licensing is tiered by package size, not message volume. Evaluate a package against your capacity needs, then run it on infrastructure your team controls.
- Plan licensing around a defined package.
- Choose infrastructure that fits your workload.
- Compare total operating costs using your own usage and deployment requirements.
Kafka Cost & Operations
Compare Kafka costs.
Switch with confidence.
For enterprises planning a staged move from Kafka.
An illustrative annual scenario compares $1 million in current Kafka platform costs with $200,000 for KubeMQ: an 80% difference*. These are example inputs, not a price quote or customer result. Supported applications connect through the Kafka wire protocol. Separate KubeMQ Migration Tools assess workloads, copy topic records, map consumer offsets and prepare a controlled cutover.
- Plan costs by package size. KubeMQ licensing is based on package size, not message volume.
- Move gradually, in your control. Choose which workloads move and when, with validation before each cutover.
- Let KubeMQ tools handle the migration steps. Assess compatibility, copy messages and map consumer offsets.
Kafka requires KubeMQ’s replicated storage engine used by new installations. Validate client versions, features and performance for your workloads. Total savings depend on your package, infrastructure and operating costs.
Migration requirements
Migration targets must use strict acknowledgment. Copying is resumable and at-least-once: a crash between target acknowledgment and offset-map persistence can duplicate one record per partition per crash. Cutover normally requires inactive source and target consumer groups. Plan and validate the transition for your applications.
Check Kafka compatibilityCloud Messaging Cost & Control
Put cloud messaging
back in your cost model.
For teams evaluating alternatives to usage-based cloud messaging services.
KubeMQ supports SQS/SNS and Google Pub/Sub-compatible interfaces. Evaluate existing client libraries against KubeMQ while choosing where the broker runs and how its infrastructure is provisioned.
- Compare licensing, compute, storage, networking and operations together.
- Evaluate endpoint changes and supported API behavior.
- Bring infrastructure ownership into the cost decision.
Google Pub/Sub uses an emulator-compatible interface, requires sticky routing for ordered subscriptions and an external encrypted transport boundary. SQS receipt handles are node-local; related operations must reach the serving node. SNS topic deduplication and SQS queue deduplication have distinct semantics. Validate API scope rather than assuming complete managed-service equivalence.
Messaging Consolidation
Different applications.
A common messaging foundation.
Shared management and observability
For organizations operating multiple messaging technologies across different teams.
Native protocol support lets teams assess a common platform while retaining familiar application clients. Manage protocol configuration, inspect activity and review audit events through KubeMQ’s management tools.
- Evaluate applications protocol by protocol.
- Bring operational visibility into a common console.
- Use native SDKs and messaging patterns for new services.
A shared broker does not make different protocols interchangeable. Validate each workload’s semantics and isolation requirements.
Private, Hybrid & Isolated Environments
Run where your
requirements take you.
For organizations that need direct control over data placement, access and infrastructure.
Deploy KubeMQ in your own Kubernetes environment, on-premises or in a private cloud. Use its deployment, security and management capabilities to build an operating model around your organization’s requirements.
- Control where messaging infrastructure and data reside.
- Configure authentication, access roles and audit logging.
- Assess network isolation, deployment dependencies and operational procedures.
Security and compliance depend on your deployment. Messaging authentication and authorization are configured separately from management authentication and RBAC; these controls are off by default. Configure transport and replication encryption separately, and arrange images, license keys and external dependencies for isolated environments.
Distributed & Edge Deployments
Bring messaging closer
to the work.
For applications spread across sites, facilities or edge environments.
Evaluate KubeMQ on Kubernetes infrastructure close to the applications that produce and consume messages. Combine native queues, events and request/reply patterns with protocol support such as MQTT.
- Choose deployment locations around your topology.
- Match messaging patterns to local application behavior.
- Validate capacity, connectivity and recovery under real operating conditions.
Cross-site connectivity and recovery during network interruptions must be designed and tested; deployment across sites does not imply automatic federation or disconnected recovery. MQTT retained messages are not supported, and sessions are in memory and node-local.
AI Agent Infrastructure
Connect agents
to your messaging workflows.
For teams adding agents to applications and operational workflows.
KubeMQ includes an MCP server for sending, receiving and inspecting messages. A2A support adds agent registration, discovery, request/reply and streaming responses, backed by a replicated registry.
- Give agents access to messaging through MCP.
- Coordinate agent interactions through A2A.
- Keep the messaging infrastructure in your own environment.
Configure authentication to establish agent identities and apply ownership controls.
Which challenge
are you working on?
Tell us what you run today and what needs to change. We’ll help you assess the fit and define a practical next step.
Run a 14-day Docker evaluation with kmq
Install kmq for macOS, Linux or Windows, start Docker, then run:
kmq onboard --goal evaluation --name kubemq --platform linux/amd64 --pullUse the returned installation identifier to authenticate and verify. Enter your password locally when prompted.
kmq auth setup --installation INSTALLATION_ID --username admin
kmq deploy verify --installation INSTALLATION_IDSee installation and verification steps →
Use Podman or ask a coding agent to help
For Podman, add the --runtime podman option. The server image is Linux x86-64; Apple Silicon needs x86-64 emulation in the container runtime. Coding agents can read the installed kmq command schema and skills before planning changes.
Help me deploy KubeMQ using kmq. Read https://docs.kubemq.io/deploy/cli and inspect `kmq version`, `kmq schema -o json` and `kmq skills get core`. Ask whether I want evaluation, trial or production and which runtime/context to use. Explain missing prerequisites. Inspect before changing resources. Use saved plans and explicit targets. Keep passwords, email codes and license keys out of chat, command arguments and logs; let me enter them through protected local input. Preserve existing data and installation identity. Verify license adoption, authenticated access and an exact message round trip before reporting success. If anything fails, show the actual state and a bounded recovery step.Run Docker manually
This single-line evaluation command works in macOS and Linux shells and Windows PowerShell. Replace Docker with Podman when using Podman.
docker run -d --platform linux/amd64 --name kubemq --hostname kubemq -p 127.0.0.1:8080:8080 -p 127.0.0.1:50000:50000 -p 127.0.0.1:9090:9090 -v kubemq-data:/kubemq/store europe-docker.pkg.dev/kubemq/images/kubemq-next:v3.5.0Open the local dashboard to create your administrator account. Verify the installation and send a message →
The evaluation starts on a fresh standalone data volume. Keep that volume if you later add a trial or paid license. Online evaluation needs outbound HTTPS to license.kubemq.io. By running it, you accept the evaluation terms, including required usage reporting.