Proxus is an Industrial IoT platform that connects machines, organizes their data, and makes it useful — in dashboards, automation rules, integrations, and AI workflows.
If you are new here, this page shows you what the platform does, who it is built for, and the fastest path to a working setup.
What Can You Do With Proxus?
| Capability | What It Means | Learn More |
|---|---|---|
| Connect | Read data from Siemens, Modbus, OPC UA, Allen-Bradley, and 15+ industrial protocols | Protocols |
| Contextualize | Organize raw PLC tags into a Unified Namespace (UNS) based on ISA-95 | Unified Namespace |
| Automate | Detect conditions and trigger alerts or actions at the edge, even during network outages | Rules Engine |
| Script | Deploy custom C# functions to Edge Gateways for transformations and calculations | C# Functions |
| Visualize | Build dashboards, browse live data in UNS Explorer, and monitor health in Operations Center | Visualization |
| Integrate | Send data to ClickHouse, PostgreSQL, Azure IoT Hub, MQTT brokers, and more | Integrations |
Who is Proxus For?
OT Engineers
Connect PLCs and sensors without custom middleware.
IT Architects
Expose industrial data through standard REST, MQTT, and SQL paths.
Operations Managers
See process status without waiting for a separate reporting project.
Developers
Extend the platform with C# functions at the edge.
Data Scientists
Query operational history through SQL or REST.
System Integrators
Roll out one design across multiple sites.
Go to Learning Paths and pick the path that matches your role. Each path guides you step-by-step through the docs you need.
Why Proxus?
Industrial transformation projects often fail when systems are hard to connect or hard to change. Proxus reduces that friction:
- Unified Namespace: Model data hierarchically instead of as flat tag lists. Every consumer reads from the same structure.
- Stateless Edge: Keep configuration on the Central Server so gateways are replaceable in minutes, not days.
- Hybrid Intelligence: Use visual rules when they are enough, or C# when you need custom logic.
- Vendor Agnostic: Bridge OT protocols (Siemens, Modbus, OPC UA) with IT standards (MQTT, SQL, REST) in one platform.
Getting Started in 3 Steps
Deploy the Platform
Install Proxus using Docker Compose for a single-server setup, or use Kubernetes HA for production environments that need failover and rolling updates.
Connect Your First Device
Register an Edge Gateway, create a Device Profile, and start reading data — either from a real PLC or the built-in simulator.
See Your Data
Open the UNS Explorer to see live, organized data flowing through the system. Then build your first dashboard.
Quick Start Guide
Deploy Proxus, connect a simulator, and verify data flow in under 30 minutes.
Kubernetes HA Deployment
Deploy Proxus with HA PostgreSQL, replicated ClickHouse, NATS JetStream, active-active UI, and singleton gateways.
Learn the Fundamentals
Before diving into configuration, understand the core concepts that power the platform:
Hub & Spoke Topology
How one Central Server coordinates distributed Edge Gateways, with a real multi-site scenario.
Unified Namespace
The ISA-95 hierarchy that makes all industrial data accessible and meaningful.
Stateless Edge
Why gateways hold no state and how that simplifies large deployments.
Architecture Overview
The complete data flow pipeline from shop floor to dashboards.
Explore Further
| Topic | Purpose |
|---|---|
| Learning Paths | Role-based guided journeys through the docs |
| Glossary | Standard definitions for all Proxus terminology |
| Troubleshooting | Start here when something is not working |
| Configuration Reference | Complete reference for Proxus-config.toml |