Fleet Node
A Fleet Node connects a remote miner network to Proto Fleet. It runs beside the miners, discovers and controls them locally, and keeps an outbound connection to Fleet.
Use a Fleet Node when the Fleet host cannot reach a miner network directly. Each miner is assigned to one Fleet Node after pairing.
Install the service, confirm its identity, and connect it to Fleet.
Install an exact release without changing the node’s identity.
Revoke access, remove the service, or prepare the host for reuse.
Check enrollment, service health, connectivity, and discovery.
How it works
Fleet sends discovery, pairing, telemetry, and control work over the node’s outbound connection. The node runs that work against its local miners and returns the results. You do not need to expose the Fleet Node or miner network to inbound internet traffic.
If Fleet becomes unavailable, miners continue running with their last configuration. Commands and telemetry through that Fleet Node resume after the connection returns.
Supported hosts
Fleet Node supports Linux hosts with:
systemdamd64orarm64architecture- Root access or
sudo - Outbound HTTPS access to GitHub releases and the Fleet server
- Network routes to the miners it will manage
The host does not need Docker. The installer creates a dedicated fleetnode service account and installs the boot-managed service.
What to expect
- The Fleet Node stores its enrollment identity on the host.
- Fleet shows whether the node is online, stale, awaiting confirmation, revoked, or requires an update.
- The service starts at boot and restarts after an unexpected process exit.
- Fleet Node does not update itself or follow a release channel. An operator chooses and installs each exact release.
- Multiple Fleet Nodes can connect to one Fleet deployment. Keep their miner assignments separate.
Continue to install and enroll a Fleet Node.