For the complete documentation index, see llms.txt. This page is also available as Markdown.

What Is Connectware?

The configuration-as-code platform for connecting industrial machines to IT applications through a single Unified Namespace.

Connectivity in Connectware is organized into services. Each service is defined in a YAML service commissioning file that declares its connections, endpoints, mappings, and any optional runtime resources — containers, files, or servers — needed to reach a machine or system. When you enable a service, Connectware creates and manages those resources automatically and publishes the data on structured MQTT topics that your applications subscribe to.

One Data Foundation for the Whole Enterprise

Factory environments run machines from different eras and vendors, each with its own protocol and data format. The result is data silos: OT systems that cannot reach IT applications without costly point-to-point integrations that are hard to scale and maintain across sites.

Connectware provides a Unified Namespace (UNS): a shared MQTT-based data layer for MES, SCADA, analytics, and AI applications. All connectivity is defined in service commissioning files that declare what to connect, what data to read, and how to route it. Connectware creates and manages the underlying connections, subscriptions, and topic routing from that definition.

Diagram showing Connectware between shop floor devices and IT applications, providing a single Unified Namespace
Connectware sits between your shop floor and your IT applications, providing a single Unified Namespace for both

Connect, Transform, and Scale

Connect machines and systems using OPC UA, Modbus/TCP, Siemens S7, Kafka, MQTT, HTTP/REST, and many more connectors. Devices publish through Connectware to a structured MQTT topic hierarchy — the Unified Namespace — that applications subscribe to instead of connecting to devices directly.

Transform data in real time as it flows through Connectware. The Rule Engine filters, normalizes, enriches, and computes derived values before the data reaches downstream systems.

Scale across sites with GitOps. The same service commissioning file runs from a single edge device to a multi-cluster production deployment, protected by role-based access control, mTLS-encrypted communication, Single Sign-On, and Multi-Factor Authentication.

Author service commissioning files faster with the VS Code Extension, which provides schema validation and autocompletion, and with Cybus Connectware GPT, which generates them from natural-language prompts.

Next Steps

Last updated

Was this helpful?