Locci Box

Modern software teams are running more untrusted code than ever before. AI agents write code and run it. CI pipelines execute scripts from dozens of contributors. SaaS platforms let customers upload and run their own logic. Developer tools evaluate arbitrary snippets in real time. Every execution is completely isolated at the hardware level. No shared kernel. No shared memory. No shared anything. Each box is its own computer created for one task, destroyed when it is done. Every one of these scenarios shares the same hidden risk: that code runs somewhere shared. A misconfigured script leaks environment variable. A runaway process consumes resources meant for another tenant. A malicious payload escapes its container and touches the host. These aren't edge cases they're the inevitable consequence of shared execution environments at scale. Existing solutions force a painful tradeoff: - Docker containers are fast but share the same kernel. A container escape is a full host compromise. - VMs are secure but slow to boot seconds, not milliseconds and expensive to run at scale. -Serverless functions abstract the problem away but lock you into one cloud provider and one runtime model. - DIY sandboxing takes months to build correctly and even longer to maintain. Teams end up either accepting the risk, over-engineering a brittle internal solution, or avoiding the feature entirely. There has been no simple, API-first, hardware-isolated execution layer built for developers. Until now. Locci Boxb is a B2B execution infrastructure platform. It provides a dead-simple REST API and CLI that lets any application, agent, or pipeline spin up a hardware-isolated microVM, run code inside it, get the output, and destroy the VM all in under 100 milliseconds. App was made with IBM BOB and Lovable