Proxus is built on a distributed Hub & Spoke architecture designed for the Industrial IoT.
High-Level Topology
- Central Core (The Hub): The single source of truth for configuration, management, and long-term data persistence.
- Edge Gateways (The Spokes): Autonomous execution units deployed near the machinery to collect, process, and buffer data.
Central Core
The Central Core is the brain of the platform.
- Management Console: A unified web interface to manage thousands of gateways, devices, and rules.
- Orchestrator: Handles the lifecycle of Edge actors.
- Persistence Layer: Entity database for configuration and metadata, high-performance telemetry store for time-series data.
Edge Layer
The Edge Gateway is the muscle of the system. It runs on industrial PCs or servers physically located on the factory floor.
Gateway Types
- System Gateway: Always co-located with the Central Core. Handles internal system tasks.
- Remote Gateway: Deployed to remote sites or factory lines. Connects to your PLCs.
Edge Orchestration
Edge Gateways are stateless by design. They receive their workload configuration from the Central Core over a reliable messaging backbone. If a gateway fails, you simply replace the hardware and connect it; it will pull its full configuration automatically.
Critical Capabilities
Stateless Design
Gateways pull full configuration from Central Core automatically.
Store and Forward
Data buffered locally during network outages. Zero data loss.
Low Latency
Local processing in under 10ms. No cloud roundtrip required.
Bandwidth Optimization
Send only changes and aggregates. Reduce data costs by 90 percent.
Local Logic
Rules and C# functions run locally for instant response.
Embedded MQTT Broker
Accept device telemetry locally without external dependencies.
Data Flow Pipeline
Ingest
Gateway connects to assets via Native Industrial Protocols (Siemens, Modbus, AB, etc.) or the Embedded MQTT Broker.
Normalize
Raw signals converted to Proxus Transport format with UTC timestamps and Data Quality indicators.
Contextualize
Data mapped to Unified Namespace hierarchy using ISA-95 standard.
Process
C# User Functions execute custom logic at the edge for transformations.
Route
Dispatcher routes to Rule Engine for alerts and to Outbound Integrations.
Persist
Data transmitted to Central Core for storage and visualization.
Security & Reliability
All Edge Gateways initiate outbound-only connections to the Central Core via TLS 1.3. This ensures that your PLCs remain isolated from the corporate network while still providing real-time data.