EMQX
EMQX is the world's most scalable and reliable MQTT platform, designed for high-performance, reliable, and secure IoT data infrastructure. It supports MQTT 5.0, 3.1.1, and 3.1, as well as other protocols like MQTT-SN, CoAP, LwM2M, and MQTT over QUIC. EMQX enables you to connect millions of IoT devices, process and route messages in real time, and integrate with a wide range of backend data systems. It's ideal for applications in AI, IoT, Industrial IoT (IIoT), connected vehicles, smart cities, and beyond.
Starting from v5.9.0, EMQX has unified all features from the previous Open Source and Enterprise editions into a single, powerful offering with the Business Source License (BSL) 1.1.
If you want to understand why we made the change, please read this blog post.
Please go to the License section for more details about BSL 1.1.
Key Features
EMQX delivers a powerful set of capabilities for modern connected systems:
Comprehensive Protocol Support
- Full MQTT v5.0, v3.1.1, and v3.1 support.
- MQTT over QUIC: Leverage the benefits of QUIC for faster connection establishment, reduced head-of-line blocking, and seamless connection migration.
- Support for other IoT protocols like LwM2M, CoAP, MQTT-SN, and more through gateways.
Massive Scalability & High Availability
Powerful Rule Engine & Data Integration
- SQL-based Rule Engine to process, transform, enrich, and filter in-flight data.
- Seamless data bridging and integration with 50+ cloud services and enterprise systems, including:
- Message Queues: Kafka, RabbitMQ, Pulsar, RocketMQ, etc.
- Databases: PostgreSQL, MySQL, MongoDB, Redis, ClickHouse, InfluxDB, etc.
- Cloud Services: AWS Kinesis, GCP Pub/Sub, Azure Event, Confluent Cloud, and more.
- Webhook support for easy integration with custom services.
- Reliable message queuing for asynchronous and decoupled communication.
- Extends MQTT with durable message storage, configurable queue lifecycle, TTL, and size limits, ensuring messages are preserved until consumption.
- Supports load-balanced consumption and optional last-value semantics, allowing queues to retain only the most recent message for each topic when needed.
- Drag‑and‑drop canvas to orchestrate real‑time data pipelines with zero code, using nodes for rules, integrations, and AI tasks.
- Schema Registry: Define, store, and manage data schemas to ensure consistency.
- Schema Validation: Validate incoming data against registered schemas to maintain data integrity.
- Message Transformation: Convert data between different formats and structures to facilitate seamless integration.
- Native AI processing capabilities for IoT data streams.
- Integration with popular AI services.
- Support for AI-driven decision making at the edge or in the cloud.
Advanced Observability & Management:
Extensibility
- Plugin architecture for extending functionality.
- Hooks for customizing behavior at various points in the message lifecycle.
Unified Experience:
- With the BSL 1.1 license (from v5.9.0), all features, including those previously exclusive to the enterprise edition, are available to all developers.
Quick Start
Try EMQX Cloud
The simplest way to set up EMQX is to create a managed deployment with EMQX Cloud. You can try EMQX Cloud for free.
For comprehensive guidance, see the EMQX Cloud Documentation.
Run a single node using Docker
docker run -d --name emqx \
-p 1883:1883 -p 8083:8083 -p 8084:8084 \
-p 8883:8883 -p 18083:18083 \
emqx/emqx-enterprise:latest
Next, please follow the Install EMQX Using Docker guide for further instructions.
Run EMQX cluster on Kubernetes
Please refer to the official EMQX Operator documentation for details.
Download EMQX
If you prefer to install and manage EMQX yourself, you can download the latest version from the official site.
For more installation options, see the EMQX installation documentation
Documentation
Contributing
Please see our contributing guide.
For more organised improvement proposals, you can send pull requests to EIP.
Resources
Build From Source
The default branch master tracks the latest development.
Stable releases are tracked by release-XY branches, such as release-62 for version 6.2.N.
- EMQX 5.4 and newer can be built with OTP 25 or 26
- EMQX 5.9+ can be built with OTP 27
- EMQX 6.1+ can be built with OTP 28
Build and run a release locally:
git clone https://github.com/emqx/emqx.git
cd emqx
make
_build/emqx-enterprise/rel/emqx/bin/emqx console
Build packages in _packages dir:
- Build a portable (for host OS/arch) tar.gz package:
make emqx-enterprise-tgz
- Build an RPM/DEB (depending on host OS) package:
make emqx-enterprise-pkg
- Build a Docker image:
PROFILE=emqx-enterprise make docker
Version Schemes
EMQX versions follow the Major.Minor.Patch scheme (e.g. 6.1.2).
GA Releases
General Availability releases, listed on the official download catalog page.
- Major (
5, 6): incremented for significant architectural changes that may
require special upgrade procedures or introduce backward-incompatible changes.
- Minor (
6.0, 6.1, 6.2): new features and improvements. Each minor line
has a dedicated release-XY branch (e.g. release-62 for the 6.2.N series).
- Patch (
6.1.0, 6.1.1, 6.1.2): cut from the matching release-XY
branch, containing bug fixes and low-risk improvements.
Rolling upgrade between adjacent minor versions is supported — see the
upgrade path matrix below.
Non-GA Releases
Non-GA builds are published as tarballs, packages, and Docker images available for
download, but are not listed on the official download catalog page.
-alpha.N (e.g. 6.2.0-alpha.1): early preview of a new minor line. Only
cut for the first release of a minor (e.g. 6.1.0, 6.2.0).-beta.N (e.g. 6.2.0-beta.1): feature-complete preview of a new minor
line. Only cut for the first release of a minor.-rc.N (e.g. 6.1.2-rc.1): release candidate. May be cut before any
release version — either a new minor (X.Y.0-rc.N) or a patch (X.Y.Z-rc.N).-patch.N (e.g. 6.1.2-patch.1): on-demand bug fix build produced for
paying customers between regular patch releases.
Rolling Upgrade Paths Since 5.0
Below are the matrices of supported rolling upgrade paths since 5.0.
Tables are split for readability; the late-v5 versions (5.8 – 5.10) appear in both.
- Version numbers end with
? e.g. 7.0? are future releases.
- ✅: Supported, or planed to support.
- ⚠️: Supported, but with limitations.
- ❌: Not supported.
- 🔄: Tentative full support for future versions.
See release notes for detailed information.
Within v5 (5.0 – 5.10)
| From\To |
5.1 |
5.2 |
5.3 |
5.4 |
5.5 |
5.6 |
5.7 |
5.8 |
5.9 |
5.10 |
| 5.0 |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
⚠️[1] |
❌[2] |
| 5.1 |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
❌[2] |
| 5.2 |
|
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
❌[2] |
| 5.3 |
|
|
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
❌[2] |
| 5.4 |
|
|
|
✅ |
✅ |
⚠️ |
✅ |
✅ |
✅ |
✅ |
| 5.5 |
|
|
|
|
✅ |
⚠️ |
✅ |
✅ |
✅ |
✅ |
| 5.6 |
|
|
|
|
|
✅ |
✅ |
✅ |
✅ |
✅ |
| 5.7 |
|
|
|
|
|
|
✅ |
✅ |
✅ |
✅ |
| 5.8 |
|
|
|
|
|
|
|
✅ |
⚠️[3] |
⚠️[3] |
| 5.9 |
|
|
|
|
|
|
|
|
✅ |
✅ |
| 5.10 |
|
|
|
|
|
|
|
|
|
✅ |
- [1] Old limiter configs should be deleted from the config files (
etc/emqx.conf and data/configs/cluster-override.conf) before upgrade.
- [2] Pre-5.4 routing table will be deleted. Upgrade to 5.9 first, then perform a full-cluster restart (not rolling) before upgrade to 5.10 or later.
- [3] Opentelemetry headers configuration support was introduced in 5.8.7. This release date is later than 5.9.0 and 5.10.0.
5.8 versions running 5.8.7 or later require a rolling upgrade to version 5.9.1 or 5.10.1.
Alternatively, remove the header configuration for OpenTelemetry integration during the upgrade.
- [4] Durable session states will be lost after upgraded from v5 to v6. After clients reconnect, the sessions created in the new nodes will appear to be clean.
Into v6 and v7 (5.8 – 7.0?)
There is no 6.4 release. The 6.x line ends at 6.3, and 7.0 follows it.
| From\To |
5.8 |
5.9 |
5.10 |
6.0 |
6.1 |
6.2 |
6.3 |
7.0? |
| 5.8 |
✅ |
⚠️[3] |
⚠️[3] |
⚠️[4] |
⚠️[4] |
⚠️[4] |
⚠️[4] |
🔄 |
| 5.9 |
|
✅ |
✅ |
⚠️[4] |
⚠️[4] |
⚠️[4] |
⚠️[4] |
🔄 |
| 5.10 |
|
|
✅ |
⚠️[4] |
⚠️[4] |
⚠️[4] |
⚠️[4] |
🔄 |
| 6.0 |
|
|
|
✅ |
✅ |
✅ |
✅ |
🔄 |
| 6.1 |
|
|
|
|
✅ |
✅ |
✅ |
🔄 |
| 6.2 |
|
|
|
|
|
✅ |
✅ |
🔄 |
| 6.3 |
|
|
|
|
|
|
✅ |
🔄 |
| 7.0? |
|
|
|
|
|
|
|
✅ |
- [4] Durable session states will be lost after upgraded from v5 to v6 or later. After clients reconnect, the sessions created in the new nodes will appear to be clean.
License
Important License Update
Effective from version 5.9.0, EMQX has transitioned from Apache 2.0 to the Business Source License (BSL) 1.1.
License Requirement for Clustering (v5.9.0+)
Starting with EMQX v5.9.0, due to the license change and the unification of all features, deploying an EMQX cluster (more than 1 node) requires a license file to be loaded.
Please refer to the following resources for details on license acquisition, application, and the specifics of the BSL 1.1.
EMQX is an MQTT broker and messaging platform for IoT: it connects millions of devices, routes messages in real time, and bridges them into backend data systems. Aimed at AI, IoT, IIoT, connected vehicles and smart cities.