Before deploying Proxus, ensure your environment meets the following minimum requirements. Proxus is built on .NET 10 and is optimized for high-throughput industrial environments.
Operating Systems
Proxus is designed for cross-platform compatibility, with a primary focus on Linux for stability and performance.
| Platform | Supported Versions | Recommendation |
|---|---|---|
| Linux | Ubuntu 22.04+, Debian 11+, RHEL 9+ | Ubuntu 24.04 LTS |
| Windows | Windows Server 2022+, Windows 11 | Windows Server 2022 |
| Container | Docker 24.0.0+, Docker Compose v2 | Official Docker Images |
[!TIP] For production environments, we strongly recommend using the Official Docker Images to ensure consistent dependency management and simplified updates.
Hardware Requirements
Proxus consists of two main components with different resource profiles.
Edge Gateway
The Edge Gateway is lightweight and designed to run on factory-floor hardware, including ARM64 devices like Raspberry Pi.
| Resource | Minimum | Recommended |
|---|---|---|
| CPU | 2-Core (x86_64 or ARM64) | 4-Core |
| RAM | 4 GB | 8 GB |
| Storage | 16 GB SSD | 32 GB SSD (High Endurance) |
Central Server
The Central Server handles the UI, centralized configuration, and high-performance data storage. It uses a dual-database architecture:
- PostgreSQL: Manages system entities, configurations, and metadata.
- ClickHouse: Stores high-frequency time-series telemetry and system logs.
| Resource | Minimum | Recommended |
|---|---|---|
| CPU | 4-Core (x86_64) | 8-Core+ |
| RAM | 8 GB | 16 GB - 32 GB |
| Storage | 100 GB NVMe | 500 GB+ NVMe (RAID 10 recommended) |
[!IMPORTANT] Storage performance is critical for the Central Server when handling high-frequency telemetry. NVMe SSDs are highly recommended for the database partitions.
Network and Connectivity
Proxus uses a Hub-and-Spoke architecture with a high-performance messaging system as the primary communication backbone.
Required Ports
Ensure the following ports are open in your hardware or software firewalls.
| Port | Protocol | Usage | Direction |
|---|---|---|---|
| 4222 | TCP | Message Bus Client/Server | Bi-directional |
| 8080 | TCP | Management Console (UI) | Inbound (Central) |
| 1883 | TCP | MQTT Bridge (Embedded Broker) | Inbound (Edge) |
| 8883 | TCP | MQTTS (Secure Bridge) | Inbound (Edge) |
| 5432 | TCP | PostgreSQL | Internal (Central) |
| 8123 | TCP | ClickHouse HTTP API | Internal (Central) |
Connectivity Requirements
- Leaf Node: Edge Gateways must have stable TCP access to the Central Server's messaging port (4222). Proxus uses Stream Persistence for guaranteed delivery.
- Time Sync: All nodes (Edge and Central) must use NTP for time synchronization to ensure accurate telemetry timestamps.