Industrial Data Integration Platform
Connect, unify and securely share industrial data
Cogent DataHub is industrial data integration software. It connects OPC UA, OPC Classic, MQTT, Modbus, SQL databases and historians through one platform, so you can aggregate data, move OPC DA to OPC UA without DCOM, keep logging through outages, and share data securely between plant and business networks.
Compare product plans & pricingYour plant data. Connected, shared, and kept moving.
Connect once. Share live data across your operation.
Plants grow one project at a time, and every pair of systems that needs to share data gets its own custom link. DataHub gives those systems one place to connect.
10 separate links in this example. Each one is built, secured and maintained on its own, and a new system usually means several more.
Find an interface and review what DataHub supports, common applications, and technical documentation.
No integrations match your search.
Select an integration
Choose one from the list to see technical details and documentation.
Connect to OPC UA servers as a client, and expose data as an OPC UA server.
Bridge OPC Classic DA data across machines and eliminate DCOM issues.
Relay OPC A&E alarm and event data across network zones.
Connect, share, and modernize OPC UA alarm and condition data.
Convert OPC DA to OPC UA (and vice versa) without replacing hardware.
Bridge OPC data between servers, PLCs, databases, files, and MQTT.
Combine data from OPC, MQTT, Modbus, Excel, and more into one dataset.
Read Modbus TCP devices and make their registers available as OPC or MQTT data.
Publish and subscribe to MQTT brokers with configurable topics and Sparkplug support.
Publish industrial data using the Sparkplug payload specification.
An MQTT broker built into DataHub, with Sparkplug support.
Send industrial data to Azure IoT Hub and Azure Event Hubs.
Send industrial data to Amazon IoT Core and Amazon Kinesis.
Log industrial data to SQL Server, Oracle, MySQL and other ODBC databases.
Send industrial time-series data to InfluxDB for analytics.
Send data to AVEVA Historian (formerly Wonderware Historian).
Send real-time data to the AVEVA PI System.
Receive streaming data from Kafka and Azure Event Hubs, or write to them (V11+).
Move data between networks over encrypted, authenticated DataHub tunnels, without DCOM.
Deploy DataHub in a DMZ to relay data between OT and IT zones.
One-direction tunnels in software, plus support for hardware data diodes (V11+).
Cache data locally during outages and deliver it when the connection returns.
Build browser-based HMI screens and dashboards from DataHub data.
View trend charts of DataHub data points.
Monitor Windows system metrics and share them through DataHub.
Run custom scripts on data changes, schedules or events.
Configure and monitor remote DataHub instances.
Six common industrial data problems, shown working with DataHub.
The device and its protocol stay the same behind the OPC DA server. DataHub changes the interface clients use: OPC DA in, OPC UA out.
Tunnels are encrypted and password protected, and endpoints can be read-only or read-write. Which side opens the connection, and which ports are open, depends on your architecture.
Shown with an external broker. DataHub can also run its own broker.
Store & forward is included with DataHub database logging. Cache size is configurable; how much can be cached depends on your configuration.
Each source and destination is configured, and available interfaces depend on the enabled capabilities.
WebView displays are built in DataHub and served by DataHub's web server.
Legacy OPC DA servers can't serve modern OPC UA clients, and replacing them is costly.
DataHub reads the OPC DA server as a client and exposes the same values through its OPC UA server.
Review implementation details for this application.
Remote teams need plant data without exposing the plant network or relying on DCOM and VPNs.
Two DataHub instances mirror data over an encrypted, authenticated tunnel across the network boundary.
Review implementation details for this application.
Cloud and IIoT platforms use MQTT, while plant systems speak OPC.
DataHub's MQTT client publishes selected OPC values as topics to your broker, where subscribers pick them up.
Review implementation details for this application.
Process values are scattered across servers, and collecting them for reports is manual.
DataHub logs selected points to an ODBC database, and caches records locally if the database is unavailable.
Review implementation details for this application.
OPC servers, Modbus devices and MQTT sources each serve different systems.
DataHub brings configured sources into one data set that connected clients can use, whatever the original protocol.
Review implementation details for this application.
People need live process displays in a browser without installing SCADA clients everywhere.
DataHub WebView serves browser-based displays with live DataHub data from DataHub's own web server.
Review implementation details for this application.
DataHub tunnels move data between instances over encrypted, authenticated connections, without DCOM. They're proxy and DMZ friendly, and the architecture decides which side opens the connection and which ports stay closed.
Swipe to explore the network architecture.
SSL/TLS-encrypted, password-protected tunnels between DataHub instances. Endpoints can be read-only or read-write, and reads and writes can use separate tunnels.
Place DataHub instances in the OT network and the DMZ, so the DMZ instance relays data to IT with no direct path between IT and OT.
Data Diode Mode (V11+) makes a tunnel discard all incoming data. It's a software control; DataHub also works with hardware data diodes, which enforce one-way flow physically.
Tunnels also detect network breaks with a configurable heartbeat (as fast as 50 ms) and recover automatically, and the security level required for a connection can be set per endpoint.
Six capabilities and what each one looks like in practice. Enable the capabilities your project needs.
Combine different data sources into one unified data set and route data between systems.
DataHub reads from OPC UA, OPC DA, MQTT, Modbus TCP, Excel and DDE sources at the same time. All data lands in DataHub's data set, where any configured destination (another OPC server, MQTT broker, historian, database or web display) can use it without knowing the original source.
Applications: Unified Namespace, multi-source SCADA feeds, data normalization before analytics.
Publish and subscribe with MQTT brokers, with Sparkplug support and an optional built-in broker.
DataHub's MQTT client publishes to and subscribes from compatible brokers, with Sparkplug support (V11 adds Sparkplug V3 and MQTT v5). DataHub can also run a broker internally.
Applications: IIoT pipelines, Unified Namespace, cloud IoT gateways, Sparkplug-aware SCADA.
| Source | Point | Value |
|---|---|---|
| OPC UA | Line01.Speed | 1250 RPM |
| OPC DA | Tank01.Temp | 72.4 °C |
| Modbus | Pump03.Pressure | 4.3 bar |
| MQTT | Plant.Energy | 124 kW |
Encrypted, authenticated tunnels between DataHub instances, without DCOM.
DataHub tunnels mirror data between instances over SSL/TLS-encrypted, password-protected connections. Endpoints can be read-only or read-write, reads and writes can use separate tunnels, and connections are proxy and DMZ friendly. Data Diode Mode (V11+) enforces one-way movement in software and is not equivalent to a physical hardware diode. DataHub also supports deployments that use compatible hardware data diodes.
Applications: Secure OT-to-IT delivery, remote plant monitoring, segmented networks.
Redundant sources and instances, automatic recovery, and store and forward during outages.
DataHub supports redundant data sources and redundant DataHub instances for high availability. Tunnels detect network breaks quickly and recover automatically, and store and forward caches data for databases, cloud connections and external historians until the connection returns.
Applications: Critical infrastructure, 24/7 operations, remote sites with unreliable WAN.
Select a failure scenario to see the Output Domain follow the available source.
Data Domain
Data Domain
The client connection stays the same. Reads continue without disruption when the active source switches.
Log process data to SQL databases and deliver it to historians, with store and forward.
DataHub logs to SQL Server, SQL Express, Oracle, MySQL and other ODBC databases, and delivers data to InfluxDB, AVEVA Historian, AVEVA PI Server and other external historians. Store and forward is included with database logging and available for external historians from V10.
Applications: Long-term archival, compliance reporting, analytics data pipelines.
HMI screens, dashboards, trend charts and system monitoring.
DataHub WebView builds HMI screens, process displays and dashboards. QuickTrend charts DataHub data for troubleshooting, and System Monitor tracks Windows host metrics alongside process data.
Applications: Operator displays, management dashboards, commissioning diagnostics.
| Timestamp | Tag | Value |
|---|---|---|
| 10:42:03 | Tank01.Temperature | 72.4 |
| 10:42:02 | Tank01.Temperature | 72.6 |
| 10:42:01 | Tank01.Temperature | 72.5 |
Start with the capabilities you need today and choose a plan that supports where your industrial data architecture is going next.
Lite and Foundation prices shown below are 12-month subscription licenses.
Core industrial connectivity, data movement, logging, and visualization for focused applications.
$328.90/ month
$3,946.80 for 12 months
Plan highlights
Expanded connectivity for MQTT, cloud, historians, secure tunneling, and web-based access.
$658.90/ month
$7,906.80 for 12 months
Plan highlights
The complete DataHub capability set for advanced, resilient, enterprise-scale architectures.
Contact us
Pricing tailored to your deployment
Plan highlights
| Capability | Lite | Foundation | Scale |
|---|---|---|---|
| DataHub features and API support | Included | Included | Included |
| OPC DA and OPC UA client + server | Included | Included | Included |
| Modbus TCP | Included | Included | Included |
| Data bridging and data logging | Included | Included | Included |
| Excel / DDE client + server | Included | Included | Included |
| InfluxDB support and DataHub WebView | Included | Included | Included |
| Secure tunneling / SkyHub / TCP | — | Included | Included |
| MQTT client and MQTT broker | — | Included | Included |
| REST, OPC Classic HDA, and ODBC historians | — | Included | Included |
| Azure Event Hubs, Kafka, and Amazon Kinesis | — | Included | Included |
| Email / SMS, web server, and camera support | — | Included | Included |
| OPC UA A&C and OPC A&E | — | — | Included |
| AVEVA Insight / Historian, AVEVA CONNECT, and OSIsoft PI Historian | — | — | Included |
| Alarm & notification and System Monitor | — | — | Included |
| Data redundancy, DataHub Historian, and audit support | — | — | Included |
Foundation includes 1 TCP connection, 20 MQTT client links, 20 MQTT broker links, and 5 DataHub XL links. Contact our team to confirm connection counts and deployment requirements.
Our engineers can help map your protocols, connection counts, redundancy needs, and add-ons to the right licensing configuration.
Subscription licenses: Each computer running DataHub needs a license for the features it uses.
Support & Maintenance: the first year is included. Renewal is annual and recommended for updates, security patches, and support.
Add capabilities later: extend your plan with add-ons and an updated license key while Support & Maintenance is active.
Perpetual licensing is available by quote.
Prices shown are US list prices in USD and are subject to change.
Evaluate DataHub, browse technical documentation, and find focused guidance for OPC, MQTT, tunneling, logging, historians, cloud connectivity, and configuration.
Evaluate DataHub with your own industrial systems.
Download Free TrialOpen product documentation and release notes.
Browse DocumentationLearn setup, configuration, and advanced features.
Watch Training VideosReview Support & Maintenance coverage and assistance.
View Support CoverageNo resources match your search
Try OPC UA, MQTT, redundancy, historian or security.
Customers on DataHub’s flexibility and the technical support behind their solutions.
the fact that we could leverage the Cogent DataHub scripting engine, OPC interfaces, and file creation abilities in a tool we had already paid for in the prior project was a bonus for the cost of this project. By being able to set triggers for just about anything, we were able to be very creative in our solution. Each time we do something new with the Cogent DataHub, we are amazed at the flexibility that it provides us to bring things together and make them work.
“Cogent DataHub has allowed us to be extremely efficient and profitable.”
“You have shown remarkable and unusual responsiveness to our needs.”
Technical and purchasing questions, answered directly.
Ask Our EngineersCogent DataHub is industrial data integration middleware that connects OPC UA, OPC Classic (DA and A&E), MQTT, Modbus TCP, SQL databases, historians and other interfaces in one unified data set. It is developed by Cogent Real-Time Systems and offered by Software Toolbox.
DataHub runs as a Windows service. It connects to the data sources you configure, brings their data into one internal data set, and makes that data available to configured destinations such as OPC clients, MQTT brokers, databases, historians, web displays or other DataHub instances.
Yes. DataHub converts between OPC Classic (DA) and OPC UA in both directions, so OPC DA servers can serve OPC UA clients without changes to field equipment.
Yes. DataHub connects to OPC DA servers locally and uses its own encrypted tunneling to move data to other machines, so remote clients don't need DCOM.
Yes. DataHub's store and forward caches data locally when a database, cloud connection or external historian is unavailable, and sends the stored values when the connection returns. It is included with database logging; store and forward for cloud connections and external historians requires V10 or later.
Yes. DataHub's MQTT client publishes to and subscribes from compatible MQTT brokers with configurable topics, and supports the Sparkplug specification. Version 11 added Sparkplug V3 and MQTT v5 support.
Yes. DataHub can run an MQTT broker with Sparkplug support, so a separate broker is not required.
Yes. DataHub tunnels are SSL/TLS encrypted, password protected and proxy and DMZ friendly. Instances can be placed on each side of a DMZ, and connections can be designed so one side has no open inbound ports. Exact firewall rules depend on your architecture.
No. Data Diode Mode is a software setting that makes a tunnel discard all incoming data, so data moves in one direction only. It is not a physical data diode, but DataHub also supports hardware data diodes through TCP emulation. Data Diode Mode requires V11 or later.
Yes. DataHub logs data to SQL Server, SQL Express, Oracle, MySQL and other ODBC databases, and delivers data to historians including AVEVA Historian, AVEVA PI Server and InfluxDB.
Yes. DataHub supports AVEVA Historian (formerly Wonderware Historian) and AVEVA PI Server (formerly OSIsoft PI) as external historians, with store and forward available from V10. Contact Software Toolbox to discuss your specific historian version.
WebView is DataHub's web HMI capability for building browser-based dashboards and operator displays that show live DataHub data.
Yes. DataHub supports redundant data sources and redundant DataHub instances for high availability.
Yes. DataHub aggregates OPC, MQTT and other sources into one data set and supports Sparkplug and an optional built-in MQTT broker, which makes it a practical way to feed a Unified Namespace.
Yes. A free trial of Cogent DataHub is available so you can test it with your own systems before you buy.
Version 11 added Sparkplug V3 and MQTT v5 support, Apache Kafka and Azure Event Hubs support, and Data Diode Mode with hardware data diode support. See the DataHub 11.1 article in Technical Resources for the latest release details.
Test DataHub with your own systems, or talk to a Software Toolbox engineer about your project.
