KubeMQ
Deploy

Choose your path

Pick the right way to run KubeMQ: try it on a laptop, install with kmq, Docker or Kubernetes, go air-gapped, migrate a broker or upgrade.

KubeMQ runs as one server on Docker for development and test, or as a cluster of three or more servers on Kubernetes for production. Start by trying it on your machine in 5 minutes, then pick the page for your goal.

An air-gapped install is about 60 minutes of work in two sittings, with a wait between them while KubeMQ issues your offline license file.

What do you want to do?

You want toGo toWhere it runsLicense you needTime
Try KubeMQ on your laptopTry KubeMQOne Docker serverNone: a 14-day evaluation starts on its own5 minutes
Develop or test on one serverInstall with kmq, or Install with DockerOne Docker or Podman serverTrial key (Docker), or a license key10 minutes
Run a production clusterInstall on KubernetesKubernetes, 3 or more serversTrial key (Kubernetes), then a license key30 minutes
Install with no internet accessInstall air-gappedKubernetes, 3 or more serversOffline license file60 minutes
Move from Kafka, RabbitMQ, SQS, MQTT, STOMP, Pub/Sub, AMQP or JMSMigrate from another brokerAnySame as the path you install withPer guide
Connect AI agents or an MCP (Model Context Protocol) hostKubeMQ AiwayAnySame as the path you install with10 minutes
Upgrade a running KubeMQUpgrade KubeMQWhere it runs todayYour current license15 minutes
Leave the older kubemq image or chartMove from legacy KubeMQ—Contact support—

Each license in the table is compared on Plans compared.

kmq or manual commands?

ComparekmqDocker commandsHelm commands
Runs in PowerShell, no WSL (Windows Subsystem for Linux) shellYesNoNo
Adds the license for youYesNoNo
Resumes after an interruptionYesNoRe-run the same Helm command
Best whenYou want one tool for install, license and checksYou manage containers yourselfYou manage Kubernetes with Helm or GitOps

All three paths install the same server and end in the same checks.

Every command on these pages installs the latest release. The artifact names and how to pin a release are on Requirements and supported setups.

Was this page helpful?

On this page