machine0 launches persistent CPU/GPU VMs from the CLI
Launch HN: machine0 (YC S26) – Persistent CPU and GPU VMs from the CLI
machine0 (YC S26) offers persistent NixOS and Ubuntu VMs with dedicated CPU/RAM, static IPs, and per-minute billing, all managed via CLI commands with JSON output. VMs can be suspended to stop billing, snapshotted, and cloned. Optional GPUs include H100, H200, L40S, and MI300X. With 99.99% uptime across four regions, it's designed for long-running tasks, reproducible builds, and autonomous agents.
Every VM gets a public IP and HTTPS at `<vm>.mac0.io`.
- zodiac
Does snapshot/suspend/resume keep processes/RAM alive - or do you need to re-start processes/reload stuff into RAM? How does that work under the hood (CRIU?) and how fast is it?
- atechboy
> People run a pilot agent that scopes work and delegates it to sub-agents, each on its own VM: shape a project with the pilot, and the workers implement it and open PRs. One customer runs hundreds of machines at once, spun up and torn down from the CLI.
Are people spawning VMs for every tool call? If so, would love to understand why so, and why containers are not a good fit?
- bobbylarson
The Profiles idea is the interesting part. Injection at creation is the easy half; the hard half is revocation mid-session. If a credential in a profile rotates or gets pulled while a box is up for days, does the running VM keep the old value until restart? For long horizon agents that window is where the risk actually lives.
- kam
NixOS 25.11 was EOL a month and a half ago. Where's NixOS 26.05?
- averylostnomad
When you say suspendible, do you mean that I could make a VM, configure it by installing packages and libraries, then pause it?
And resume it later with the full disk ready to go? No billing during the inbetween time?
That’d be huge, but seems wild. How can you economically keep the storage between active sessions?