Linux built for the browser
Our clean-room AcmeX86 runtime boots x86-64 Alpine with Node, Python, compilers, package tools, and Pi. The browser acts as the machine host.
AI workspace · x86-64 Linux
ACME OSThe browser is the computer.
Work in browser-native files and AI, then boot a complete 64-bit Linux machine on the same live workspace. No server-side VM. Nothing to install.
$ uname -m
x86_64
$ mount | grep workspace
acme-workspace on /workspace type 9p (rw)
$ pi "build and test this project"
OPFS↔Linux↔AI
✓ mounted live ✓ local-first ✓ no install
One working surface
One workspace.
Two ways to work.
Start with browser-native files and AI. Open Linux when the job needs a shell, package manager, compiler, Python, or Node. The workspace is mounted—not copied—so switching tools never starts a sync.
AcmeX86 · Linux 6.12
Mounted files, not a boot-time copy
Your OPFS workspace appears live at /workspace over virtio-9p. Browser edits and Linux writes meet on the same persistent files.
AI lives beside the machine
Run Qwen or Gemma locally with WebGPU, or bring an OpenRouter key. Browser AI Chat and Pi inside Linux share the same narrow model bridge.
Normal sockets and a faster file lane
WISP carries ordinary Linux TCP and UDP. For bounded public downloads, acmefetch moves the file through the gateway and OPFS without paying for TLS inside the emulator.
Fast networking
Use Linux sockets when semantics matter.
Skip the emulation tax when they don’t.
ACME OS chooses an explicit path for each kind of traffic. It does not disguise a browser fetch as a complete Linux network stack.
01
Transparent path
WISP for standard Linux networking
curl, wget, apk, Git, SSH, and application sockets use guest TCP/UDP over one same-origin WebSocket. HTTPS remains end-to-end between Linux and the destination.
Linux socketWISPInternet
02
Accelerated path
acmefetch for fast public files
Downloads up to 8 MiB can bypass emulated TLS and per-packet processing. The gateway retrieves the file, the browser commits it to OPFS, and Linux reads it from the live mount.
GatewayOPFSLinux file
Clear trust boundary: WISP keeps HTTPS plaintext inside the guest. The accelerated path terminates target TLS at the gateway, so it is opt-in and intended for public artifacts.
How it works
The browser is the hypervisor boundary.
It owns credentials, persistent files, AI, and network adapters. AcmeX86 supplies the CPU and devices. Linux sees a normal x86-64 machine and your workspace as a mounted filesystem.
Browsertrusted host
WorkspaceOPFS files
AI runtimeWebGPU / OpenRouter
NetworkWISP + file fast path
9p mountmodel IPCpackets + files
AcmeX86Wasm host
CPUx86-64 execution
DevicesPCI + virtio
Disksparse ext4 overlay
Linux ABIserial + virtio
Linuxx86-64 guest
bash node python gcc git pi
Clear boundaries
The guest gets tools.
The browser keeps control.
Stays in the browser
- OAuth and provider credentials
- OPFS workspace (mounted into Linux)
- Local model weights
- Disk manifests and snapshots
Runs inside Linux
- Shell commands and build tools
- Python and Node processes
- Pi’s coding-agent loop
- Project tests and generated output
Your browser. A complete workspace.
Open ACME OS.
Boot Linux in place.
Nothing installs and nothing uploads by default. Your workspace, Linux disk overlay, snapshots, and local model state persist in this browser profile.
Start Linux