Distributor vs. Chariot: Which MQTT server is right for you?
When building out your MQTT architecture in Ignition or across an industrial enterprise, you’ll need an MQTT broker — also called an MQTT server — to manage the flow of data between devices and applications.
Cirrus Link offers two MQTT server options:
- Distributor, a module that runs within Ignition
- Chariot, a standalone MQTT server for larger, more distributed environments
But how do you choose the right one?
In this guide, we’ll break down the differences between Distributor and Chariot so you can select the best fit for your architecture.
What is an MQTT server?
First, a quick refresher: An MQTT server (or broker) is the central component of the MQTT publish/subscribe architecture.
It acts as a traffic controller for MQTT messages, routing data between data producing devices (like sensors or PLCs) and subscribing or data consuming applications (like SCADA, cloud services, or databases).
Cirrus Link MQTT servers: An overview
Cirrus Link’s MQTT solutions are built specifically for industrial use, and both Distributor and Chariot use the same core engine — designed for critical real-time applications
What is Distributor?
Distributor is an MQTT server module for Ignition. It allows MQTT clients (like MQTT Transmission or Edge devices) to connect and exchange data managed within an Ignition environment.
Distributor is ideal for:
- Simpler deployments
- Hub-and-spoke architectures
- Customers already using Ignition who want a tightly integrated broker
What is Chariot?
Chariot is a standalone MQTT broker that runs independently of Ignition. It’s built for large-scale, high-performance deployments across plants, systems, and enterprise layers.
Chariot is ideal for:
- Large or growing IIoT environments
- Distributed architectures with thousands of clients
- Customers who need a broker that operates independently from their SCADA or HMI
Key differences: Distributor vs. Chariot
Here’s a quick visual comparison to help you decide:
|
Feature |
Distributor |
Chariot |
|
Runs inside Ignition |
✅ |
❌ |
|
Standalone deployment |
❌ |
✅ |
|
Suitable for large-scale clients |
⚠️ Limited |
✅ Yes |
|
Number of connections supported |
Moderate |
Unlimited* |
|
Built-in web interface |
❌ |
✅ |
|
Debug & monitoring tools |
Basic (via Ignition) |
Advanced via Chariot MQTT Client (free) |
|
Licensing |
Module purchased to Ignition Gateway |
Perpetual One-time license |
|
Best for |
Ignition-focused setups |
Distributed, large scale systems |
When to use Distributor
Choose Distributor if:
- You’re already using Ignition and want to keep everything in one platform
- You’re deploying MQTT in a up to 250 client setup
- You need a simple way to deploy and manage MQTT inside your Ignition project
Distributor is easy to configure and maintain for SCADA engineers familiar with the Ignition ecosystem.
When to use Chariot
Choose Chariot if:
- You need an MQTT broker decoupled from your SCADA platform
- You have a large scale of sites, edge devices, and consumers across a network
- You’re preparing for enterprise-scale OT/IT convergence
- You want advanced monitoring, UI controls, and future-proof scaling
Chariot gives you flexibility to deploy MQTT messaging across industrial networks without being tied to any single platform — including Ignition.
Can I use both?
Yes — and many customers do.
For example, you might:
- Use Distributor for local plant-level MQTT messaging inside Ignition
- Use Chariot as a centralized broker at the enterprise level to aggregate and route data to analytics platforms, data lakes, or cloud apps
This hybrid approach allows for local control and global visibility using a unified MQTT Sparkplug architecture.
Final thoughts
Both Distributor and Chariot offer powerful MQTT broker functionality.
The right choice depends on your architecture size, performance needs, and system design philosophy.
If you’re not sure which one fits your needs, we’re here to help.
Contact us to discuss your architecture
Try Chariot for free
Explore MQTT solutions for Ignition