Cloud-Dependent
Every message depends on a remote connection.
EMQX EDGE
Unify industrial data locally across factories, devices, systems, and remote sites—and bridge it reliably to cloud, analytics, and AI.
curl -fsSL emqx.sh/edge | bashCloud & Data Platform
Edge Data Sources
Trusted across the EMQX ecosystem
Why EMQX Edge
Edge sites need a local MQTT data backbone and reliable synchronization—even when the cloud connection drops.
Explore the documentationEvery message depends on a remote connection.
Local operations continue while data synchronizes upstream.
Capabilities
01 / CONNECT
Connect devices, gateways, and applications through a high-performance MQTT broker built for constrained edge environments.
$ nanomq_cli pub -t "topic" \
-q 2 -u nano -L 100 \
-m test -h broker.emqx.io \
-p 1883
$ nanomq_cli sub -t t -q 1 \
-h broker.emqx.io -p 188302 / PROCESS
Coming soonIntegrate with eKuiper to filter, aggregate, transform, and route MQTT data before it consumes bandwidth or reaches cloud systems.
03 / STREAM
Turn selected MQTT topics into persistent local streams. Query history by time range and replay data for troubleshooting, analytics, and recovery.
04 / BRIDGE
Synchronize curated local topic trees with central MQTT platforms through resilient, multiplexed data bridges.
Deployment
A compact C runtime for Linux, Windows, and Docker across x86, ARM, and RISC-V targets.
Explore deployment optionsRun on armhf and arm64 Linux gateways close to devices and production lines.
Deploy on x86_64 industrial PCs for higher connection and message volumes.
Use the official image for repeatable deployments across edge fleets.
Benefits
Keep local message dispatch below 5 ms for responsive shop-floor and automation control loops.
Handle more than one million messages per second with an asynchronous actor architecture built for multi-core systems.
Start with a boot footprint as low as 200 KB and use less than 10 MB of memory under load.
Queue and retransmit messages automatically through intermittent cellular and satellite WAN.
Protect local data with TLS/SSL, multiple authentication methods, and fine-grained access control lists.
Manage through a built-in web dashboard, REST APIs, and native Prometheus telemetry metrics.
EMQX Edge decouples local operations from unreliable upstream networks and synchronizes data when connectivity returns.
Broker messages locally with low latency.
Keep local devices and applications connected.
Cache upstream messages at the edge.
Reconnect over TCP or QUIC and retransmit automatically.
Use cases
Give each production line a shared local data backbone. Bring MQTT data and EMQX Neuron feeds into one edge broker.
Explore manufacturingKeep a site-level namespace running locally, and synchronize selected MQTT topics with enterprise historians.
Explore unified namespaceKeep in-vehicle messaging local and bridge telematics upstream over intermittent cellular connections.
Explore connected vehiclesBring meter, inverter, EV charging, and substation data together near the assets that produce it.
Explore smart energyKeep power, cooling, and equipment telemetry moving locally, then publish it to cloud analytics.
Explore data centersPreserve operational telemetry from oil rigs, wind turbines, and mining equipment across high-latency satellite links.
Explore edge computingUnified namespace
EMQX Neuron connects industrial assets. EMQX Edge creates a local UNS and keeps it available. EMQX Enterprise or cloud unifies data across sites, applications, analytics, and AI.
Sensors · Gateways · Machines
Modbus, OPC UA, S7 to MQTT
Connect · Process · Stream · Bridge
EMQX Cloud · AWS · Azure
FAQ
EMQX Edge is a lightweight, high-performance MQTT data backbone for the industrial edge. It connects local MQTT data, integrates with eKuiper for processing, persists selected topics with MQTT stream, and bridges data to enterprise or cloud MQTT platforms.
EMQX Neuron connects industrial equipment through protocols such as Modbus, Siemens S7, and OPC UA, then converts its data to MQTT. EMQX Edge receives that MQTT data and brokers, processes, persists, and bridges it across the site and to the cloud.
EMQX Edge supports MQTT 5.0 and MQTT 3.1.1, including all three MQTT quality of service levels (QoS 0, 1, and 2), topic aliasing, user properties, and shared subscriptions.
Yes. Local MQTT communication continues independently. Bridge caching stores configured upstream messages and retransmits them when connectivity returns, while MQTT stream can preserve selected topic data for local queries.
Both are lightweight MQTT brokers. EMQX Edge adds a multi-threaded actor architecture, built-in MQTT stream persistence and queries, eKuiper integration, MQTT over QUIC bridging, and a built-in dashboard, REST API, and Prometheus metrics for industrial edge deployments.
EMQX Edge runs on Linux, Windows, and macOS across x86, ARM, and RISC-V architectures, with an official Docker image for container deployments.
Deploy in minutes with the Linux quick install, downloadable packages, or Docker.