> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-4-2/discover/what-is-connectware.md). # What Is Connectware? 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](/2-4-2/connectors/shop-floor-connectors.md). 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](/2-4-2/data-flows/rule-engine.md) 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](/2-4-2/tools/cybus-connectware-extension-vs-code.md), which provides schema validation and autocompletion, and with [Cybus Connectware GPT](/2-4-2/tools/cybus-connectware-gpt.md), which generates them from natural-language prompts. ## Next Steps * [How Connectware Works](/2-4-2/discover/how-connectware-works.md): a walkthrough of Connectware's data model, from YAML configuration to live data flowing to your applications. * [Choose Your Deployment Platform](/2-4-2/deployment/choose-your-deployment-platform.md): decide between Kubernetes and Docker for your first installation. * [Connect Your First Machine](/2-4-2/discover/connect-your-first-machine.md): install a sample service against a simulated machine and watch live data arrive. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cybus.io/2-4-2/discover/what-is-connectware.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.