Run Train at Home on several Macs: the hosted fleet hub

Installing subnera fixes the biggest gap for one Mac: seeing its real queue position and phase without staring at a frozen official UI. Once you're running Train at Home on more than one machine, a second problem shows up — checking each Mac's menu bar one at a time doesn't scale. subnera hub is the answer to that: one live dashboard for the whole fleet.

What it actually is

subnera hub is a hosted web app at app.subnera.com↗. There is nothing to host or maintain on your side. Each enrolled Mac's subnera sends periodic status reports to it over HTTPS, and the service stores them so the dashboard can show your fleet.

What it shows

• A live fleet dashboard: phase (queued, registering, working, off…), queue position, layer, tokens/h, network speed and last-seen time for every enrolled Mac, updated as it happens.
• A machine page: host facts, history over 6 hours, 24 hours or 7 days, recent remote commands, and live miner logs streamed to your browser — the same log the queue-position guide shows you how to read by hand, just without the terminal.
• Remote commands, only where a Mac allows them: start, stop or restart the official app, reap orphan workers, switch the auto-restart watchdog on or off, and start or stop log streaming.
• Alerts over Telegram, email or webhook when a machine goes offline, gets stuck, is kicked during work, loses its queue place, has a slow network, or is blocked from updating — the full list is in the alerts guide. You get one alert per problem, with a cooldown, and a recovery message when it clears. These are subnera hub's own read of your machines' reports — useful early warnings, not an official Macrocosmos status.
• Official-app update tracking, so you can see which Macs are on which version.
• Earnings: earned, pending and next payout, by day, month, quarter, year or machine, with CSV and JSON export. The figures come from public Macrocosmos data — see the rewards and payouts guide for what the earnings side actually does.
• Shared pools, and English and French interfaces.

Getting it running

1. Go to app.subnera.com↗ and create an account, with a password or a passkey.
2. Create a pool. A pool is the group of Macs you see together on one dashboard.
3. In the hub, generate a one-time enrollment token.
4. On each Mac, open subnera's menu → Remote Dashboard Settings… and paste the token. The Mac appears in the fleet within seconds.
5. Optional: tick Allow remote control on that Mac if you want remote commands to work there.

What is sent, and what is not

Enrolling a Mac is opt-in and reversible: without it, subnera sends nothing to the hub, and by default only reads local files plus one anonymous daily update check (which you can turn off). Once enrolled, the menu bar app sends periodic reports over HTTPS to the hosted service, which stores them. Fleet data therefore does leave the Mac. A report contains:

• status: phase, layer, tokens per hour, queue position and network speed;
• the machine name;
• the public hotkey;
• the official app's version;
• CLI log lines, only while a live log stream is requested.

Wallet private keys are never read or sent. The machine key is stored in the macOS Keychain, and the hub keeps only a hash of it.

Remote control, by design

Remote commands come from a fixed list of 9: start, stop or restart the official app, reap orphan workers, switch the watchdog on or off, control log streaming, and similar. There is no shell and no remote code, and a command cannot update the app. The same read-only boundary the network guide describes for subnera applies here: nothing touches Train at Home's own local control port.

Remote control is off by default. Each Mac must enable Allow remote control locally, and can take it back at any time. Every command is recorded on the Mac and in the hub, with who sent it. A Mac executes a command on its next report, a few seconds later.

Pools: personal and shared

Every account can keep its own Macs in a pool of its own. If you're managing machines with other people, you can use a shared pool and lend one of your Macs into it — it keeps reporting under its own name, shows who lent it, and can be moved back to your own pool at any time. Members of a pool have one of four roles — viewer, member, admin or owner — that control what they can do, from read-only access up to managing other members.

Checklist

1. Create an account at app.subnera.com↗ and a pool.
2. Generate an enrollment token in the hub.
3. On each Mac, paste it into subnera's Remote Dashboard Settings… menu.
4. Tick Allow remote control only on Macs where you actually want remote commands.
5. Set up an alert channel (Telegram, email or webhook) so you hear about a stuck or offline Mac before you'd notice by checking manually.

If you're only running one Mac, none of this is necessary — the optimal setup guide and subnera alone cover you. For the failure modes subnera hub's alerts are built to catch, see the troubleshooting guide.