Skip to main content

​
Build the broker topology around your data

System Connectors define how your Coreflux broker participates in a wider MQTT system. Use them to bridge selected topics to another broker, or make Coreflux consume and produce Sparkplug B traffic.
Think of System Connectors as the roads around the broker. Bridges connect MQTT brokers, and Sparkplug connectors define how industrial MQTT traffic enters and leaves the system.
For high-availability Coreflux clustering (multi-node broker failover), see High-Availability Clustering (beta). That feature is broker configuration, not a System Connector.

​
When to use System Connectors

Use this category when you need to:
  • synchronize topics with another MQTT broker;
  • decode Sparkplug B payloads into readable JSON;
  • publish as a Sparkplug edge node; or
  • make Coreflux the Sparkplug Primary Host Application.

​
Choose a System Connector

MQTT Bridge

Synchronize selected MQTT topics with another broker.

Sparkplug B

Decode Sparkplug traffic or publish Coreflux metrics as an edge node.

Sparkplug Host

Make Coreflux the Primary Host for a Sparkplug namespace.
Choose the connector by the role Coreflux needs to play.

​
Compare System Connectors

A SPARKPLUG_HOST connector and a SPARKPLUG_B connector in DECODE or BOTH mode cannot run together on the same broker. Both consume the complete spBv1.0/# namespace. You can combine one Host connector with separate ENCODE-only connectors.

​
Next Steps

Choose a Sparkplug role

Compare decode, edge-node, and Primary Host responsibilities.

High-Availability Clustering

Run multiple Coreflux brokers as a fault-tolerant cluster (beta).
Last modified on October 21, 2026