Capital & Compute

Local AI & hardware

Memory capacity sets what a machine can load, bandwidth sets how fast it answers, and utilization decides whether owning hardware beats renting it. With DRAM in a shortage cycle the arithmetic keeps moving: a build that paid for itself last quarter may not this one, and the break-even turns on how many hours the box actually runs.

In this world
24 analyses
Field tool
Check what your hardware can run ↗

Keep diving.

The featured guide stays above; the stream below moves as new analysis is published.

What this topic covers

The economics of local inference, RAM, memory bandwidth, self-hosting and the hardware behind AI.

This topic collects 24 analyses, and they are written to be read together rather than one at a time: the featured guide sets out the shape of the problem, and the pieces below work through the individual numbers, tradeoffs and edge cases behind it. Every figure is attributed to a primary source at the point it is used and carries the date it was verified, because prices and benchmark results in this area go stale in weeks rather than years. Where a number is modeled rather than measured, the assumptions are stated so the arithmetic can be checked.

The topics on this site overlap by design. This one runs into Models & benchmarks and Compute infrastructure, and a question that starts in one usually ends in another: a pricing decision turns into a hardware decision, a benchmark result turns into a cost question. Follow the links inside the posts rather than treating these archives as separate shelves.

Check what your hardware can runWatch the RAM price indexCompare GPU street prices