EMQX Cloud IoT & Region Updates
EMQX Cloud rolled out a NATS Gateway for MQTT devices (no glue code), added Google Cloud Tables, a London region on AWS/GCP, and a SQL query visualizer to streamline IoT‑to‑cloud workflows. The update targets simplified device‑to‑analytics pipelines for streaming data. (emqx.com)
Internet of Things platforms move sensor messages from devices to databases, and EMQX Cloud’s latest update adds more ways to do that without custom bridge code. (emqx.com) EMQX Cloud said on March 31, 2026 that it added a NATS gateway, support for EMQX Tables on Google Cloud, a London region for Dedicated Flex on Amazon Web Services and Google Cloud, and an “Explain Query” tool in its Tables Data Explorer. (emqx.com) Message brokers are traffic hubs for machine data: Message Queuing Telemetry Transport is common on constrained devices, while NATS is popular in cloud-native services. EMQX’s cloud docs say the new gateway lets NATS clients connect to EMQX Cloud and exchange messages with Message Queuing Telemetry Transport clients. (docs.emqx.com) The company said that setup removes the need for separate translation services between device traffic and back-end applications. EMQX’s documentation says the gateway supports publish-subscribe, request-reply, and queue-group patterns, with transport options including Transmission Control Protocol, Transport Layer Security, WebSocket, and secure WebSocket. (emqx.com) (docs.emqx.com) EMQX Tables is the company’s built-in time-series database, a storage system tuned for timestamped readings such as temperature, location, or machine status. EMQX Cloud docs say it is optimized for high-throughput, low-latency ingestion and analysis of Message Queuing Telemetry Transport data and is powered by GreptimeDB. (docs.emqx.com 1) (docs.emqx.com 2) Until now, EMQX had been expanding Tables region by region: a February 2026 update added Oregon and Frankfurt on Amazon Web Services, and the March 31 update added Google Cloud support plus London on both major clouds for Dedicated Flex deployments. (emqx.com 1) (emqx.com 2) The query visualizer addresses a different bottleneck: figuring out why a Structured Query Language query runs slowly. EMQX said “Explain Query” shows execution plans inside the Tables Data Explorer so users can inspect scans, filters, and other steps before tuning a time-series query. (emqx.com) The product push fits EMQX’s broader shift from managed broker to data platform. In September 2025, the company said EMQX Cloud was evolving into a “unified Message Queuing Telemetry Transport data platform,” and in December 2025 it opened EMQX Tables to all cloud users after a public preview that drew more than 100 teams. (emqx.com 1) (emqx.com 2) EMQX also tied this release to billing and networking changes, adding annual subscriptions for Network Address Translation gateway and internal endpoint services in Dedicated Flex. Its cloud docs say the Network Address Translation gateway is required for some public-network access features, including extended authentication and data integration. (emqx.com) (docs.emqx.com) Taken together, the update narrows the gap between device messaging, cloud transport, and query tooling inside one managed service. EMQX is betting that fewer moving parts — from NATS ingress to Google Cloud storage to query debugging — will keep more Internet of Things workloads inside its platform. (emqx.com) (emqx.com)