Browser server on exe.dev
exe.dev VMs boot in ~2 seconds from an image that already includes Chrome headless-shell and every Chrome library dependency — the least setup of any platform here. The whole API is SSH.
Prereqs (human)
Section titled “Prereqs (human)”- An SSH keypair
ssh exe.dev— interactive signup (email + region)- Personal plan $20/mo (2 vCPU / 8 GB pooled across up to 50 VMs); trial terms vary — check on signup
Two ways to use it
Section titled “Two ways to use it”A. Everything-cloud (recommended — no tunnel, no latency)
Section titled “A. Everything-cloud (recommended — no tunnel, no latency)”Run the agent, vibium, and Chrome all on the VM:
ssh exe.dev new --name vibium-box # VM ready in ~2sssh vibium-box.exe.xyz# on the VM: claude/codex are preinstalled; add vibiumnpm install -g vibiumvibium go https://example.com # everything local to the VMThere is no client↔browser network hop at all — BiDi round-trips are loopback. This is the “no speed of light penalty” topology.
B. Split (browser on the VM, vibium on your laptop)
Section titled “B. Split (browser on the VM, vibium on your laptop)”ssh vibium-box.exe.xyz -- bash -s -- --service < deploy/cloud-computers/install-chrome.shssh -N -L 9515:127.0.0.1:9515 vibium-box.exe.xyz &vibium start http://127.0.0.1:9515Teardown
Section titled “Teardown”ssh exe.dev rm vibium-boxFlat-plan VMs bill while idle (no scale-to-zero), so delete or downsize boxes you’re done with.
Caveats
Section titled “Caveats”- Confirm VM arch on first login (
uname -m): vibium ships linux-x64 and linux-arm64 npm packages, but the exeuntu image is multi-arch — make sure the right one landed.