Gemini Executive Synthesis

machine0 – CLI for persistent NixOS (& Ubuntu) VMs.

Technical Positioning

A modern VPS provider with first-class NixOS support, emphasizing 'entire OS as code' and reproducible environments.

SaaS Insight & Market Implications

machine0 targets the growing demand for reproducible, declarative infrastructure. Its first-class NixOS support differentiates it from generic VPS providers, appealing directly to DevOps teams and developers prioritizing Infrastructure as Code (IaC). The ability to define the entire OS as code, manage lifecycle via CLI, and provision with Nix flakes or Ansible addresses critical pain points around environment consistency, auditing, and rapid rollback. Usage-based pricing by the minute is competitive. This product holds significant B2B SaaS potential for development, testing, and production environments where immutable infrastructure and precise state management are paramount. The integration with AI agents for provisioning further aligns with current industry trends.

Proprietary Technical Taxonomy

Raw Developer Origin & Technical Request

Hacker News Jun 16, 2026

Show HN: machine0 – Persistent NixOS VMs You Control from the CLI

Hi HN! Excited to launch machine0, a CLI that makes it easy to create, provision and snapshot persistent NixOS (& Ubuntu) VMs.You can think of machine0 as a modern VPS provider. VMs stay on unless switched-off (with 99.99% uptime), they have static IPs and HTTPS endpoints, 1-60 vCPU, up to 240GB RAM and optionally GPUs. The CLI provides commands to manage lifecycle, snapshots and also provision the VMs using Nix flakes or Ansible playbooks. VMs are priced by the minute of usage.What makes machine0 unique is that it has first class support for NixOS! In a nutshell, NixOS lets you define your entire OS as code (think Terraform but for your Linux). A flake declares your system state (packages, services, firewall rules, users...) and pins all dependencies via a lockfile. Given the same flake.nix and flake.lock, `nixos-rebuild switch` always produces the exact same system.The NixOS ecosystem is mature, and flakes are expressive: at the system level you can define packages, what's in /etc, firewall rules, users & groups etc. At the user level, you can define your shell, aliases, tmux and vim config. Having your entire environment defined as code makes it easy to audit what's installed and how things are set up. You can rollback by reverting the last commit. And agents can write the code for you and test it against disposable machine0 VMs.If you'd like to dive right in, these commands will get you started: npm install -g @machine0/cli
machine0 new my-vm --image nixos-25-11 # create a new nixos VM
machine0 provision my-vm ./flake#my-profile # provision it using a nix flake
machine0 ssh my-vm # ssh in
machine0 stop my-vm # stop the VM
machine0 images new my-vm my-snapshot # create a snapshot
machine0 new my-clone --image my-snapshot # create a new VM from the snapshot

- Demo of installation + NixOS provisioning via Claude Code:

Documentation: docs.machine0.io/introduction/over... machine0 NixOS flakes: github.com/fdmtl/machine0-ni... you're in the habit of using VMs, or want to know what the NixOS fuss is about, would love for you to give machine0 a try!

View Raw Source

Developer Debate & Comments

farfatched • Jun 15, 2026

> Every VM gets its own static IPHow does this interact with per-minute pricing?If I have a machine that's on for 1 minute per month, do I retain an IPv4 address for the whole month?Or is it IPv6-only?I recall exe.dev addressed this by not having static IPs, and instead only allowing SNI/SSH proxying to hosts.

discova • Jun 15, 2026

Any good starter material out there for NixOS?

GeoffNN • Jun 15, 2026

Very cool! I'll definitely check this out for auto-research like experiments, esp. with GPUs

Bnjoroge • Jun 15, 2026

Very cool. I have something similar set up for my homelab where I launch nixos incus containers. Been great for offloading stuff from the my agents

dmmalam • Jun 15, 2026

Looks cool. Can I run on other clouds.

Pet_Ant • Jun 15, 2026

I wonder how easy this would be to port to Guix?

EnigmaCurry • Jun 15, 2026

I'm happy to see this, and I have lots of thoughts about this. Building declarative services on Nix is a far superior way of distributing Linux to VMs than most any other way I've tried. I am working [1] on very similar things, but I've been leaning more on the self-hosted path, my VM template targets libvirt and Proxmox VE with a single CLI api. I even have an experimental branch that targets DigitalOcean. For VMs especially, I want my OS to be immutable. My VMs should contain no state other than my application state. Upgrades should be a full image replacement and reboot.So in my template, I have created the VMs with two disks: first one is for NixOS and is built from an image, and it is read-only. The second is mounted to /var and is used for all system configuration as well as application state. If I have multiple VMs, they can all share the same base image (thin provisioned). That's the mode that I want for my deployments of services, immutable and as stateless as possible. For agent use, its different, you actually want a mutable NixOS root so that the agent can do what it wants.I built three modes: immutable, semi-mutable, and mutable. mutable removes the read-only lock on the root, and just lets you manage the VM as a pet. semi-mutable adds an ephemeral overlayfs that gets wiped the next time you upgrade the base image. So that gives you kind of the best of both worlds: an immutable read-only base image and the ability to "nix profile add" whatever you (or your agent) wants, but with the contract that these imperatively installed things will disappear the next time you upgrade. Are you planning on adding a LICENSE to your machine0-nixos repo?[1] https://github.com/EnigmaCurry/nixos-vm-template

nc • Jun 15, 2026

I’ve been using machine0 for hosting openclaw and a couple of web apps i’ve been working on. Great product super easy to use with claude code.

JeanEdern • Jun 15, 2026

How does machine0 handle NixOS state drift and recovery in practice—for example, if a VM is manually modified outside the flake, can I detect or reset that drift, and how do snapshots interact with flake-based provisioning?

setheron • Jun 15, 2026

Big fan of exe.dev so the added Nix seems like a solid value add.exe.dev is great but lurking in my mind is: "how will I replicate this if I ever need to move to AWS etc.." for all the service composition.Site looks great too

Frequently Asked Questions

Market intelligence mapped to machine0 – CLI for persistent NixOS (& Ubuntu) VMs..

What problem does machine0 – CLI for persistent NixOS (& Ubuntu) VMs. solve?

Based on our AI analysis of the original developer request, its primary technical positioning is: A modern VPS provider with first-class NixOS support, emphasizing 'entire OS as code' and reproducible environments.

Are engineers actively discussing machine0 – CLI for persistent NixOS (& Ubuntu) VMs.?

Yes, we have tracked 32 direct responses and active debates regarding this specific topic originating from Hacker News.

What are the foundational technologies related to machine0 – CLI for persistent NixOS (& Ubuntu) VMs.?

Our proprietary extraction maps machine0 – CLI for persistent NixOS (& Ubuntu) VMs. to adjacent architectural concepts including NixOS VMs, CLI, VPS provider, static IPs.

Engagement Signals

Upvotes

Comments

Cross-Market Term Frequency

Quantifies the cross-market adoption of foundational terms like CLI and RAM by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.