Conference
Meet EMQ at SPS 2026: Real-Time Data for Industrial AI →

EMQX EDGE

Industrial edge
MQTT backbone

Unify industrial data locally across factories, devices, systems, and remote sites—and bridge it reliably to cloud, analytics, and AI.

QUICK INSTALL
curl -fsSL emqx.sh/edge | bash
Local latency
< 5 ms
Concurrent edge connections
100K+
Multi-core throughput
1M+ msg/s
Memory footprint under load
< 10 MB

Trusted across the EMQX ecosystem

  • Westwell
  • UISEE
  • ZEEKR
  • NIO
  • Geely

Why EMQX Edge

Cloud-only messaging leaves the edge exposed

Edge sites need a local MQTT data backbone and reliable synchronization—even when the cloud connection drops.

Explore the documentation

Cloud-Dependent

Every message depends on a remote connection.

Cloud broker
Unreliable WAN
Edge devices & PLCs

Edge-First

Local operations continue while data synchronizes upstream.

Cloud & data platform
EMQX Edge (Local UNS)
Local devices & apps

Capabilities

Connect, process, stream, and bridge edge data

01 / CONNECT

Run full MQTT at the edge

Connect devices, gateways, and applications through a high-performance MQTT broker built for constrained edge environments.

  • MQTT 5.0 & MQTT 3.1.1 compliant
  • MQTT over QUIC & Sparkplug B aware
  • TCP, TLS, and WebSocket connectivity
Explore MQTT connectivity

02 / PROCESS

Coming soon

Process streams where they happen

Integrate with eKuiper to filter, aggregate, transform, and route MQTT data before it consumes bandwidth or reaches cloud systems.

  • SQL-based stream processing through eKuiper
  • Windowed aggregation and payload normalization
  • Local actions, alerts, and MQTT republishing
SELECT
device_id,
temperature,
humidity
FROM mqtt_stream
WHERE quality = 'good'
AND temperature > -50
AND temperature < 200;

03 / STREAM

Persist edge data with MQTT stream

Turn selected MQTT topics into persistent local streams. Query history by time range and replay data for troubleshooting, analytics, and recovery.

  • Non-intrusive capture keeps live forwarding fast
  • Ring-buffer batching and Parquet persistence
  • Time-range queries through dashboard and REST API
Explore MQTT stream

04 / BRIDGE

Bridge edge data to any MQTT cloud

Synchronize curated local topic trees with central MQTT platforms through resilient, multiplexed data bridges.

  • Bidirectional bridges to MQTT cloud platforms
  • MQTT over QUIC with fast reconnection and TCP fallback
  • Selective forwarding, topic mapping, and QoS control
Explore data bridging

Deployment

Put a reliable MQTT backbone at every edge

A compact C runtime for Linux, Windows, and Docker across x86, ARM, and RISC-V targets.

Explore deployment options
  • Edge gateway

    Run on armhf and arm64 Linux gateways close to devices and production lines.

  • Industrial PC

    Deploy on x86_64 industrial PCs for higher connection and message volumes.

  • Docker

    Use the official image for repeatable deployments across edge fleets.

Benefits

Engineered for demanding edge environments

Ultra-low latency

Keep local message dispatch below 5 ms for responsive shop-floor and automation control loops.

High throughput

Handle more than one million messages per second with an asynchronous actor architecture built for multi-core systems.

Ultra-Lightweight

Start with a boot footprint as low as 200 KB and use less than 10 MB of memory under load.

Network resilient

Queue and retransmit messages automatically through intermittent cellular and satellite WAN.

Secure by design

Protect local data with TLS/SSL, multiple authentication methods, and fine-grained access control lists.

Easy to operate

Manage through a built-in web dashboard, REST APIs, and native Prometheus telemetry metrics.

Edge resilience

Keep local data moving—even when the cloud cannot

Explore data bridging

EMQX Edge decouples local operations from unreliable upstream networks and synchronizes data when connectivity returns.

  1. 01

    Broker messages locally with low latency.

  2. 02

    Keep local devices and applications connected.

  3. 03

    Cache upstream messages at the edge.

  4. 04

    Reconnect over TCP or QUIC and retransmit automatically.

Use cases

One edge broker. Many distributed architectures.

Factory-floor data hub

Give each production line a shared local data backbone. Bring MQTT data and EMQX Neuron feeds into one edge broker.

Explore manufacturing

Site-Level UNS

Keep a site-level namespace running locally, and synchronize selected MQTT topics with enterprise historians.

Explore unified namespace

Connected vehicles

Keep in-vehicle messaging local and bridge telematics upstream over intermittent cellular connections.

Explore connected vehicles

Smart utilities

Bring meter, inverter, EV charging, and substation data together near the assets that produce it.

Explore smart energy

Data centers

Keep power, cooling, and equipment telemetry moving locally, then publish it to cloud analytics.

Explore data centers

Remote edge sites

Preserve operational telemetry from oil rigs, wind turbines, and mining equipment across high-latency satellite links.

Explore edge computing

Unified namespace

One data backbone. A distributed UNS across every site.

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.

FAQ

Frequently asked questions

Build your edge MQTT data backbone today

Deploy in minutes with the Linux quick install, downloadable packages, or Docker.