Two weeks in the life of the fleet
The same telemetry the fleet keeps on itself — every machine, every thirty seconds — added up across the house. Each chart is scaled to its own busiest moment, so you are looking at the shape of the work (when it happens, how it bunches up) and deliberately not the size of the hardware. Updated 2026-10-27.
What the fleet got up to, last 14 days
Shaded: the busiest moment in each four-hour window. Line: the average across that window. Flat stretches are spare capacity, not a broken chart.
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 gets asked for
Each lane's share of the requests answered over the same 14 days — in other words, what the house actually wants from its AI.
- Chat53%
- Speech to text42%
- Text to speech5%
- Imagesnone in this window
How it was built, a week at a time
Commits per week since 2026-05-31 (428 in all). Amber marks the weeks a new part of the system landed.