Synadia MQ Gateway · Public preview
Re-point your MQTT (3.1.1 and 5.0) and AMQP 1.0 clients at Synadia MQ Gateway, and every message becomes a NATS message. No extra broker to run.
Already using NATS’s built-in MQTT listener? See what the gateway adds.
web shopamqp
Routed orders: sent
transfer → orders region=EU amount=1200
NATS subject
orders.EU
Example playground output
Companies running vehicles, chargers and energy infrastructure on NATS
Your PLCs, vendor devices and AMQP applications connect to MQ Gateway instead of a broker of their own. They keep their protocol and client libraries.
Without MQ Gateway
Each has its own users, storage and cluster, and bridges carry messages between them.
With MQ Gateway
Every client lands on NATS, so there is one set of users, one store and one cluster.
Clients on 3.1.1 can connect straight to NATS with no gateway. Add MQ Gateway for MQTT 5 and AMQP 1.0, or if you need more control over how MQTT runs in production.
| What you need | Built-in listener | MQ Gateway |
|---|---|---|
| MQTT 5 clients | Refused at connect | 3.1.1 and 5.0 on the same port |
| AMQP 1.0 and JMS | None | Yes, with some JMS limits |
| Storage control | Streams the server creates and manages for itself | You bind topics to your own streams, with your own retention, replicas and limits |
| A reliable publish is refused | MQTT 3.1.1 has no reason codes | MQTT 5 devices get a reason code |
| When a NATS server restarts | MQTT clients on that server disconnect and reconnect. Sessions survive in JetStream | Most devices stay connected. Only the gateway’s NATS connections move |
| Hub and leaf sites with JetStream domains | All MQTT state is pinned to one domain | Each binding can name its own domain |
| Sparkplug B, retained messages, wills, sessions, WebSocket, TLS, accounts | Yes | Yes |
If every device speaks MQTT 3.1.1, the server’s default retention suits you and your devices can reconnect during NATS upgrades, the built-in listener is often enough.
The gateway stores nothing itself. Messages, sessions and permissions all live in NATS.
Over MQTT or AMQP, with the library it already uses
The topic orders/EU becomes the subject orders.EU
Using your NATS users and permissions
On topics you bind, before the client is acknowledged
As an MQTT topic, AMQP address or NATS subject
Messages flow both ways: a NATS service can publish to MQTT and AMQP clients too.
Straight answers on what it is, how it works, and what it doesn’t do.
Mqg-QoS header. Other Mqg-* headers set the content type, correlation ID and properties that MQTT 5 and AMQP clients see. Request and reply works in both directions too: a NATS request reaches MQTT 5 clients with a Response Topic and AMQP clients with a reply-to address, and a NATS service can answer requests from either.Works with OSS NATS. Re-point your clients, no Synadia Platform required.
How to get started
Sign up for a trial
Submit the form to request your free 30-day trial.
Get your trial license
Receive an email with links to the licensed build and your trial license JWT.
Install the gateway
Download the mq-gateway archive for your platform, or pull the licensed container image.
Start the gateway
Put the JWT in a file, then start mq-gateway with --license.file, --mqtt or --amqp, and your NATS server URL.
Explore the docs
Try the playground, then read how bindings, streams and buckets fit together.
View docsMQ Gateway is a standalone product. Contact us for pricing.
News and content from across the community