Discover all the Connectors

ADS

Get data from TwinCat via ADS into your MQTT broker.

ALLENBRADLEY

Connectivity for Allen Bradley ControlLogix(tm) PLCs via CIP-EtherNet/IP, Micro 850 PLCs. Accessed over a DH+ bridge. Only v1.2.

ETHERNETIP

Connectivity for Ethernet/IP devices via CIP-EtherNet/IP. Accessed over a DH+ bridge. Only v1.2.

FINS

Get data from OMRON PLC via FINS into MQTT broker.

MARIADB

Integration for MariaDB databases via MQTT. Facilitates real-time data exchange and management.

MODBUS

This APP allow you to communicate with Modbus Device via MQTT server.

MODBUSSLAVE

This app allow you to create a Modbus Slave device on your Coreflux

MONGODB

This app allow you to create a Modbus Slave device on your Coreflux

MQTTBRIDGE

This service allows you to use a MQTT Broker and synchronize it with other Brokers.

MQTTOPCBRIDGE

Synchronize data between an MQTT broker and an OPC UA server to allow OPC UA compatible devices communicate with other Coreflux assets.

MSSQL

It queries data from SQL databases, publishes results as MQTT messages to topics, and listens to incoming MQTT messages to update/insert data into the SQL database. Only v1.2.

MYSQL

Integration for MySQL databases via MQTT. Facilitates real-time data exchange and management.

POSTGRESQL

This Connector is a flux asset provided by Coreflux that enables seamless communication between Allen Bradley PLCs and your data hub.

S72

This APP allow you to communicate with Siemens devices via MQTT server.

FAQ

Frequently asked questions.
What is Coreflux?
Coreflux is an Industrial IoT platform built around a high-performance MQTT broker with built-in edge computing capabilities. Unlike traditional brokers that only route messages, Coreflux processes data where it is generated using LoT (Language of Things), a human-readable automation language. The platform connects to industrial protocols like Modbus, OPC UA, Siemens S7, and Allen-Bradley, while routing data to databases, REST APIs, cloud services, and other MQTT brokers. Coreflux runs on Windows, Linux, Docker, Raspberry Pi, and cloud environments, making it suitable for edge deployments, factory floors, and enterprise-scale IoT architectures.
What is an MQTT broker and why do I need one?
An MQTT broker is the central hub that enables devices and applications to communicate using the publish-subscribe messaging pattern. When a sensor publishes data to a topic, the broker delivers that message to every application subscribed to it. This decouples your devices from your applications, meaning you can add new sensors, dashboards, or analytics tools without rewiring your entire system. For industrial IoT, an MQTT broker is the foundation of a Unified Namespace (UNS), allowing real-time data flow between PLCs, sensors, databases, and cloud platforms.
What is the Language of Things (LoT)?
LoT is a human-readable language for IoT automation created by Coreflux. It uses near-English syntax to define logic, data structures, and integrations directly within the MQTT broker. Think of LoT as SQL for real-time MQTT data. Just as SQL transforms database records, LoT transforms live MQTT streams without deploying external services. With LoT, you can define Actions (event-driven logic triggered by time or topics), Models (structured JSON schemas), Routes (connections to databases, APIs, and industrial equipment), and Rules (access control for topics and operations).
What industrial protocols does Coreflux support?
Coreflux provides native connectivity to major industrial protocols through its Routes system. Supported protocols include Modbus TCP/RTU for sensors and legacy equipment, OPC UA for modern industrial systems, Siemens S7 for S7-300, S7-400, S7-1200, and S7-1500 PLCs, Allen-Bradley for ControlLogix and CompactLogix controllers, and FINS for Omron PLCs. These protocol connectors run inside the broker, eliminating the need for separate gateway software. Data from PLCs flows directly into your MQTT namespace and can be processed, transformed, or routed to databases in real time.
How is Coreflux different from other MQTT brokers?
Traditional MQTT brokers like Mosquitto act as passive message routers. Coreflux is an active data processing platform. It combines the MQTT broker with edge computing capabilities, so you can transform, filter, validate, and route data without external services. Key differentiators include built-in LoT runtime for automation logic, native industrial protocol support without additional gateways, direct database routes to PostgreSQL, MongoDB, InfluxDB, CrateDB, and OpenSearch, Python integration for complex calculations and external libraries, and a lightweight footprint suitable for edge devices and Raspberry Pi. This means fewer moving parts, lower latency, and simpler architecture compared to assembling separate tools for connectivity, transformation, and storage.
Can I extend Coreflux with Python?
Yes. While LoT handles most IoT automation elegantly, some tasks need the full power of a programming language. Coreflux allows you to call Python functions directly from your LoT actions. Your Python code runs inside the broker alongside your automation logic, with no external services, network calls, or containers required. Use Python for complex calculations like statistics and machine learning, regex and advanced string parsing, data validation with complex rules, and external library calls using numpy, pandas, or custom packages.
How is Coreflux different from other MQTT brokers?
Traditional MQTT brokers like Mosquitto act as passive message routers. Coreflux is an active data processing platform. It combines the MQTT broker with edge computing capabilities, so you can transform, filter, validate, and route data without external services. Key differentiators include built-in LoT runtime for automation logic, native industrial protocol support without additional gateways, direct database routes to PostgreSQL, MongoDB, InfluxDB, CrateDB, and OpenSearch, Python integration for complex calculations and external libraries, and a lightweight footprint suitable for edge devices and Raspberry Pi. This means fewer moving parts, lower latency, and simpler architecture compared to assembling separate tools for connectivity, transformation, and storage.