This article walks you through everything you need before your first devices appear on the dashboard: the equipment the agent runs on, the network it needs, and the order in which to set the platform up.
Setup order
Create an organization and invite your employees.
Create a site and assign a responsible person and technicians.
Install the Miner Agent on a dedicated device at the farm and activate it.
Run a network scan and confirm the discovered devices.
Assign owners, configure pools and set up reports.
What equipment you need
To run Monitoring at the farm you need a dedicated device with the agent installed:
Mini PC / single-board computer — Intel NUC, Beelink, any x86_64 mini PC.
Industrial PC — for high-temperature or dusty environments.
Dedicated server or virtual machine — if the site already has server infrastructure.
Raspberry Pi 4/5 (64-bit ARM) is supported. Raspberry Pi 3 and older (32-bit ARM) is not supported.
The agent runs as a background service (systemd) and needs no monitor or keyboard.
Hardware requirements
Parameter | Minimum | Recommended |
OS | Linux (any distribution with systemd) | Ubuntu 22.04 LTS / Debian 12 |
Architecture | x86_64 (AMD64) | x86_64 (AMD64) |
CPU | 1 core | 2+ cores |
RAM | 256 MB | 512 MB+ |
Disk | 500 MB of free space | 1 GB+ (DB backups and logs) |
Privileges | root (service installation and startup) | — |
The agent uses minimal resources: up to 100 parallel HTTP requests while scanning, up to 50 while collecting telemetry. The local database is SQLite.
Network requirements
Parameter | Description |
Local network access | The agent must be on the same network as the ASIC devices. HTTP/HTTPS on ports 80/443. |
Internet access | gRPC over port 443 (TLS) to the Monitoring cloud. This is the only outbound connection. |
Bandwidth | Minimal. Telemetry is sent as gRPC messages every 5–15 seconds. |
Static IP | A static IP or a DHCP reservation is recommended. |
ICMP (ping) | Better left unblocked. Can be turned off with |
DNS | Required to resolve the Monitoring address. |
Uninterruptible power supply
We strongly recommend connecting the device running the agent through a UPS. A UPS with 10–15 minutes of runtime is enough for a clean shutdown during a power outage (apcupsd or nut).
Database integrity — a sudden power loss corrupts the SQLite file. Backups run every 24 h and the last 7 are kept.
Continuity of monitoring — while the agent is down, no alerts are sent.
Automatic restart —
systemd Restart=alwaysbrings the agent back up on its own once power is restored.
Related articles