Get started

Proxus is an industrial data platform. It reads the machines of a plant, gives every value a place in one shared structure, keeps its history, acts on it, and passes it on to the people and systems that use it. One installation does the work that usually takes a collection of separate products: connectivity, edge processing, a historian, alarms, dashboards and reports, integration and AI. You run it yourself: on one server, on several sites, or next to the machines.

What Proxus does

Connect

• Reads machines. The edge gateway speaks the protocols of PLCs, CNC controls, robots, meters and sensors: OPC UA, Modbus, SNMP, MTConnect and the native protocols of Siemens, Rockwell, Mitsubishi, Omron, Beckhoff, Fanuc, Haas, Heidenhain and many more vendors. See Protocols. Devices that send their own values publish them to the gateway's MQTT broker.
• Sets machines up quickly. A wizard tests the connection and browses the device's own tag list; devices can also be imported from a spreadsheet or from Kepware.
• Works next to the machine. The edge gateway reads, processes and buffers data on site, and keeps it while the link to the hub is down.

Organize

• Gives every value a place. Each device sits in the plant's structure (enterprise, site, area, process cell), and its values are published under that place in the Unified Namespace.
• Shows what depends on what. Health Checks find broken links and wasted data, the operational graph shows what a change affects, and application templates carry a working setup to another hub.

Process and automate

• Pipelines without code. Pipelines clean, convert, window, calculate and route values from ready-made nodes, rehearsed on stored data before they go live.
• Rules and alarms. Rules watch values, device status, logs and gateway metrics, raise alarms and run actions. Anomaly detection catches values that leave their usual pattern.
• Your own code. Functions are C# code that runs on the edge gateways.

Store and analyze

• Keeps the history. Every value of a device that delivers to the Proxus historian (new devices do by default) is stored with its time, with no separate archive product to license. Trend it, compare it with earlier periods and export it in the Trend Workspace.
• Dashboards and reports. Dashboards and reports draw on the history and the plant model, and scheduled delivery e-mails them.

Monitor and respond

• Watches the plant live. The Operations Center, the Topology and the device page show what needs attention, and alerts are taken, followed and closed with a note.
• Tells people. Notification channels send messages by e-mail, SMS, WhatsApp, Microsoft Teams, Slack, Telegram and other services.

Share

• Sends data on. Outbound targets deliver values to SQL databases, time-series databases, message brokers such as Kafka and MQTT, cloud services and REST APIs.
• Opens it to software. A REST API, a telemetry API, MQTT topics and an MCP server for AI agents.

AI

• Copilot. Copilot answers questions about the plant in plain language, finds why a device stopped, summarizes a shift, and prepares changes and actions that run only after you approve them. It sees only what the user may see.

Secure and run

• Permissions and records. Roles and UNS permissions limit who sees and changes what, down to one site or line, and the audit trail records who changed what and when.
• Runs where you need it. Docker on one server, or Kubernetes with high availability.

Who it is for

Start here

Learn how it fits together

The Concepts section explains the building blocks: the hub and its edge gateways, how a value travels from a machine to a report, devices and tags, the Unified Namespace, and when to use a pipeline, a rule or a function.