Webinar
EMQX Fleets: Managing Millions of Devices as One Fleet | Register Now →
Now in Private Beta on EMQX Cloud

Build Agents That Live Where Your Data Lives

EMQX Agents is the event-driven agent runtime on EMQX Cloud, natively wired to your MQTT broker, time-series tables, and device fleets. Describe what you want; deploy a production-grade agent in minutes.

Contact Us

Most AI Agents Stop at the Screen. Yours Acts on the Physical World.

When an agent acts on the physical world, every decision carries weight: a wrong command moves a real motor, a missed alert costs real money. That's the bar Physical AI has to clear, on every run.

The Stack

One Platform. Four Layers. The Operating System for Agentic IoT.

Each layer is a managed service on EMQX Cloud. Together they close the loop from event to decision to action.

Brain

EMQX Agents

Private Beta

Decides what to do next. Reasons over events, history, and device state, then acts. Use it with any one of the layers, a few of them, or all three.

MQTT Trigger · Broker

factory/+/temperature · Real-Time

Agent Loop

Reason · Call Tools

Decide · Act

Tables

Query History

7-Day Baseline

Fleets

Device State

dev-0042 · Shadow

Broker

Publish Command

cmd/maintenance

Generally Available
Nervous System

EMQX Broker

Where every event happens, in real time. The world's most scalable MQTT broker.

Generally Available
Memory

EMQX Tables

Where the past is recorded and queried. A managed time-series store for telemetry.

Private Beta
Actuators

EMQX Fleets

Knows device state and changes it. Manage shadows, groups, commands, and OTA jobs.

The Loop

From Message to Decision to Command. Natively Inside EMQX Cloud.

No webhooks. No glue code. The full loop runs on one platform.

Why EMQX Agents

Three Things Only EMQX Agents Can Do.

01

Native MQTT Event Ingress

Agents subscribe to topics as a first-class trigger. The deterministic preprocessor (built on EMQX's Rule Engine) filters, debounces, and batches at million-message scale before any LLM is called.

02

A Closed Loop with Tables and Fleets

Agents read 7-day baselines from EMQX Tables, inspect shadows in EMQX Fleets, request human approval, and publish commands back through the broker. Read, decide, act, observe. All on one platform.

03

Pre-Built for Industrial Workflows

Templates and Skills ship with the platform: alarm triage, predictive maintenance, OTA rollout guard, shadow reconciliation, UNS assistant. Start from a template, not from a blank prompt.

How It Works

From Idea to Running Agent in Three Steps.

1

Describe.

Type your goal in plain English. A meta-agent drafts your system prompt, trigger, tool grants, and skills.

Describe.

› Page on-call when robot-arm telemetry stalls for more than 30 seconds.

Trigger
factory/+/robot/+
Tools
broker · tables · humans
Skills
sparkplug-b, incident-triage
2

Refine.

Edit the generated spec inline. Swap tools, tighten guardrails, dry-run against a real topic before going live.

Refine.
Trigger
factory/site-a/+/robot/+
Debounce
30 s
Budget
$2 / Run · $50 / Day
Approval
PagerDuty · oncall-l1
Dry Run · Ready
3

Deploy.

Promote to staging, then production. Every run is traced, costed, and replayable.

Deploy.
RunStatusDurationCost
3a32c351Succeeded12.7 s$0.22
4379a5edSucceeded9.7 s$0.22
5beb2855Succeeded10.9 s$0.22
Capabilities

Built for Production Agents on Physical Infrastructure.

Trigger intake, MCP tools, skills, sandboxing, guardrails, and traces — one runtime for agents that act on real systems.

Trigger Intake
Live

Topic Filter

factory/+/robot/+

Live
Schema

robot.telemetry.v2

Debounce

30 s per device

Batch

site · line · model

Validate Payload

Reject malformed events before the agent loop starts.

Turns high-frequency MQTT telemetry into one clean agent run with validated context.

Connectors

Power Your Agent with MCP Connectors.

Connectors are typed MCP tools your agent calls to act on the world. Native to EMQX Cloud, and any MCP server you bring.

Safety & Governance

Agents That Can Publish to a Topic Should Not Be Able to Publish to Any Topic.

Every EMQX Agent has its own identity, an explicit topic allowlist, a per-tool permission scope, and hard budget caps. High-risk actions route through human approval before they touch a device.

Topic Allowlist (Publish / Subscribe, Separated)
Per-Table and Per-Group Scopes for Reads
Blast-Radius Caps on Batch Commands
Required Dry-Run on First Execution
Per-Invocation and Per-Agent Cost Caps
Maintenance-Window Enforcement
Full Audit Trail per Run
Agent · Predictive-Maintenance-EU
Production
Subscribe

factory/+/telemetry

Publish

factory/+/cmd/maintenance

tables.read
telemetry · last 30d
fleets.scope
group:turbines-EU
Approval
Required · Blast > 10
Budget
$5 / Run · $200 / Day
Observability

Every Run, Fully Traced.

See the trigger, the context fetched, every LLM call, every tool call, and every device ack, for any run. Replay it, eval against it, ship the next version with confidence.

Run
Succeeded

3a32c351

Input Tokens

13

Output Tokens

561

Cached

16,105

Cost

$0.22

Use Cases

Where Teams Are Using EMQX Agents.

Manufacturing

Line-level anomaly triage and shadow reconciliation across thousands of PLCs.

Energy & Utilities

Turbine baseline drift, predictive maintenance, and KPI-gated OTA rollouts.

Mobility & Fleets

Vehicle telemetry triage, recall-safe firmware rollouts, geofence rules.

Smart Infrastructure

HVAC autotuning, occupancy-aware control, human-approved building automation.

FAQs

Everything you need to know about EMQX Agents.

Join the EMQX Agents Private Beta

Cohorts onboard weekly with hands-on support from the engineering team. Tell us a little about your use case and we'll be in touch within two business days.

Contact Us
Full feature access during the beta, at no cost.
Direct line to the team building the product.
Templates and sample datasets to demo in minutes.