machine0: CLI tool to create and manage persistent NixOS and Ubuntu VMs

What it does

machine0 is a command-line tool for creating and managing virtual machines running NixOS or Ubuntu. Users provision VMs via CLI commands, configure them using Nix flakes or Ansible playbooks, and operate them through a JSON-compatible interface. The service provides persistent VMs that remain running unless explicitly stopped, with static IP addresses, HTTPS endpoints, and optional GPU access. VMs can be snapshotted and cloned to create golden images.

Who it is for

The platform targets developers and teams running long-lived compute workloads that benefit from a programmatic interface. It emphasizes support for AI agents and tools using the CLI or Model Context Protocol (MCP). The service appeals to users already invested in NixOS or those preferring reproducible infrastructure through infrastructure-as-code approaches. Workloads range from development environments to GPU-accelerated computation.

Pricing

Per-minute billing with hourly rates starting at $0.013/hour for CPU-only VMs and $0.836/hour for GPU configurations. CPU instances range from 1 vCPU with 1 GB RAM at $9/month (~$0.013/hour) to 60 vCPU with 240 GB RAM at $2,711/month (~$3.714/hour). GPU options include RTX 4000 Ada, L40S, RTX 6000 Ada, MI300X, H100, and H200 configurations. Suspended VMs incur only image storage fees at $0.078/GB/month. Minimum account top-up is $5 with unused credits refundable.

How it stands out

machine0 emphasizes native NixOS support as a differentiator, enabling deterministic builds and one-command rollbacks. The platform provides dedicated resources with no shared-tenancy concerns on premium instances, static IPs without NAT or tunnels, and deep integration with MCP servers and agent workflows. Snapshot-and-resume functionality allows users to freeze VM state and stop billing, then restore environments later. Support for high-end GPUs and up to 60 vCPUs across five geographic regions addresses compute-intensive use cases.

What a founder should check

A competitor should verify the competitive positioning against existing VPS providers (AWS, Linode, DigitalOcean, Hetzner) on price-per-compute and GPU availability, particularly for AI workloads. Second, assess switching costs by understanding how lock-in through NixOS flakes and MCP integrations affects customer retention and whether those abstractions provide genuine portability. Third, examine the pricing sustainability model—whether per-minute billing maintains margins against competitors offering larger monthly commitments, and whether the focus on agents using CLI creates network effects that are defensible or easily replicated.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.