Colibri runs a 744B-parameter MoE on a 25GB-RAM consumer machine in 1,300 lines of dependency-free C.

Topping HN at 767 points, Colibri exploits mixture-of-experts structure: only ~40B params activate per token, and only ~11GB of those change between tokens. The dense part (attention, shared experts, embeddings, ~17B params at int4, ~9.9GB) stays resident while 21,504 routed experts stream from ~370GB on disk via a per-layer LRU cache plus the OS page cache. It profiles your routing patterns and auto-pins hot experts, so it gets faster with use. Throughput on a 32GB machine is around 0.1 tokens/sec, so this is an architecture demonstration, not a daily driver. The demonstration is the point: MoE weight residency is a caching problem, and caching problems have known solutions.