Most local AI demos assume a simple setup: one person, one machine, one model and one request at a time.
That assumption disappears when a team starts sharing the hardware.
Now the system has to answer harder questions:
How do multiple users share compute without sharing identities or private files?
How do long-running jobs survive a browser refresh or a dropped connection?
How do you expose a virtual machine in a browser without treating it like a normal web page?
How do you keep an ARM64 appliance reproducible when models, containers, guest systems and licenses all have different boundaries?
This article documents the constraints we encountered while turning a single AI computer into a predictable, multi-user system.…