← use cases · Security & regulated teams
Air-gapped & inspectable deployments
A single ELF with no shell, no userspace, and no package manager is a small, reviewable trusted computing base.
The problem
In regulated or air-gapped environments, every component in the trusted computing base has to be justified. A full Linux image is thousands of packages you must vendor, scan, and defend — most of which have nothing to do with serving a model.
Why cllm fits
- ▸One ELF, no shell, no userspace, no dynamic linking — a minimal trusted computing base.
- ▸The entire control flow, from NIC to model, fits in one engineer’s head.
- ▸No network services beyond the HTTP/1.1 endpoints you explicitly route.
- ▸GPL source you can read in full before you trust it.
Honest caveats
- ▸No TLS yet — HTTP/1.1 only, so transport security must live in front of the kernel.
- ▸The inference path is not integrated, so this is a substrate to review, not a finished product.
- ▸Single NIC (Intel e1000) and single architecture (i386) today.