A tour of the Proto Fleet app, section by section. The left nav mirrors the top-level pages in the UI: Dashboard, Miners, Groups, Racks, Activity, and Settings.
Your fleet at a glance. The dashboard has two sections: Overview and Performance.
Overview summarizes current state:
Performance shows trends over a time window you choose (use the duration selector at the top of the section):
Some devices don’t report every metric, so a panel may be partially empty depending on your hardware mix.
The full list of paired miners. Use it to:
A group is a logical collection of miners — think “Bitmain S19s”, “Customer A”, or “Test bench”. Groups are flexible: a miner can belong to multiple groups, and you can apply settings or actions to an entire group at once.
Open any group to see its dedicated overview: health, performance trends, and the list of miners it contains.
A rack represents the physical layout of your fleet — rows, columns, and slots. Unlike groups (which are logical), each miner lives in exactly one rack slot. Racks are the fastest way to find “the miner in row 3, slot 7” when you need to walk over and look at it.
A chronological log of what’s happened across your fleet — pairings, firmware pushes, configuration changes, errors, and more. Use it to retrace what changed when something starts misbehaving.
Fleet-wide configuration lives under Settings. Most operators only need to touch a few of these after initial setup.
Fleet name, display preferences, and other basic options.
Authentication configuration — password policies and how users sign in.
The default pool configuration applied to new miners. Edit here to change what the fleet uses going forward; existing miners keep their current settings unless you re-apply.
Invite team members, assign roles, deactivate users, and reset passwords. Each team member gets their own login.
Upload firmware images and manage what’s available to push to miners. Also where you delete old firmware you no longer need.
Automate recurring actions on your fleet — scheduled reboots, sleep windows, and power target changes.
Create API keys for programmatic access (dashboards, integrations, scripts). Each key is tied to a user and can be revoked at any time. See the API Reference for available endpoints.