Local AI for a desk, a studio, a department.
A local machine is sized by what fits in memory, not by a headline number.
Operations per second is the number every vendor in this category leads with, and it is the least useful one. What determines whether a machine is worth having is whether the model you intend to run holds in memory at the precision you intend to run it, and how much context you can keep alive while it does.
We specify from the workload backwards: the model families in use, the precision, the context length, the number of concurrent sessions. The configuration follows from that.
Weights are parameter count multiplied by bytes per parameter: roughly half a byte at 4-bit, one at 8-bit, two at bf16. So precision moves a model across a factor of four, and the key-value cache for the context window sits on top of whatever that comes to. Choosing the machine before choosing the precision is the wrong order.
Desk
One machine under a desk or in a studio. Runs a working model set locally, with the full toolchain installed and pinned.
Individual practitioners, researchers, engineers who want the model on the same machine as the work.
Studio
A handful of nodes on a shared interconnect with common storage, presenting as one pool of capacity.
Studios, research groups, engineering teams sharing capacity across a floor.
Department
A cluster in a room with proper power and cooling, instrumented like a facility and managed like one.
Departmental IT, university groups, teams that have outgrown desks but not the building.
| Operating system | Linux or WindowsImage built to the workload, driver and accelerator stack pinned to a known-good set |
|---|---|
| Runtime | CUDA · ROCm · SYCL · Metal · Vulkan · CPUOne abstraction across the range; a model moves between Lab and Rack without porting |
| Model serving | Local, on first bootChat, embedding, vision, transcription, detection and forecasting runtimes installed and served |
| Network | Reachable without a public addressDevice-authenticated overlay; no port forwarding, no inbound exposure |
| Tenzro | Joins on first bootHardware profile detected and published to the routing layer |
| Support | Named engineering contact |