Fleet Command · dashboard

Two weeks in the life of the fleet

The same telemetry the fleet keeps for itself, every machine every thirty seconds, summed across the house. Each chart is scaled to its own busiest moment, so these are the shapes of the work — when it happens, how it bunches up — and deliberately not the size of the hardware. Updated 2026-10-27.

Activity, last 14 days

Shaded: the busiest moment in each four-hour window. Line: the average across that window.

Processors

CPU threads busy across the fleet

Graphics cards

the busiest graphics card at each moment

Memory

memory in use across the fleet

Network

data arriving across the fleet

Compute jobs

jobs running on the compute lane

AI requests

requests answered by the front door

What the front door is asked for

Each lane's share of the requests answered over the same 14 days.

How it was built

Commits per week since 2026-05-31 (428 in all). Amber marks the weeks a new part of the system landed.

2026-W22: 9 commits 2026-W23: 16 commits 2026-W24: 24 commits 2026-W25: 19 commits 2026-W26: 4 commits 2026-W27: 4 commits 2026-W28: 71 commits 2026-W29: 10 commits 2026-W30: 12 commits 2026-W32: 36 commits 2026-W33: 11 commits 2026-W34: 25 commits 2026-W35: 25 commits 2026-W36: 66 commits 2026-W37: 18 commits 2026-W38: 10 commits 2026-W40: 16 commits 2026-W41: 17 commits 2026-W42: 15 commits 2026-W43: 13 commits 2026-W44: 7 commits 2026-05-31today