DEV Community

Felipe L
Felipe L

Posted on Originally published at automationscookbook.com

machine0 Launches Persistent CPU & GPU VMs via CLI

What Happened

Machine0, a YC S26 startup, launched a CLI that spins up persistent CPU and GPU VMs. The tool is lightweight and scriptable. Developers can request resources, configure environments, and keep VMs running across restarts automatically. The release targets teams needing reliable, long‑term compute for training models or inference pipelines.

The CLI hides typical cloud provider complexity. One command creates, lists, and terminates VMs. GPU‑enabled instances are supported, a key advantage for AI workloads that need sustained GPU compute.

Why This Matters for Builders

  • Persistent VMs reduce downtime – AI agents or n8n workflows keep running after a shutdown, eliminating the need to re‑bootstrap in production.
  • Scriptable provisioning – The CLI plugs into CI/CD pipelines or workflow definitions, allowing resources to spin up and tear down on demand.
  • GPU availability for inference – A single command gives access to GPU VMs, lowering the barrier to deploying GPU‑heavy inference models in real‑time AI agents.
  • Cost predictability – Persistent instances can run only during business hours or when needed, helping teams control spend while retaining reliable compute.
  • Simplified ops – Removing cloud dashboards and manual VM configuration lets ops focus on monitoring and scaling instead of provisioning.

FAQ

Q: Can I integrate the machine0 CLI with n8n workflows?

A: Yes. Call the CLI from n8n’s “Execute Command” node or embed it in custom JavaScript to manage VMs programmatically.

Q: Does the CLI support GPU‑accelerated instances?

A: Yes. The tool includes options to request GPU‑enabled VMs for training or inference tasks.

Q: How does pricing compare to other cloud providers?

A: Exact numbers aren’t disclosed, but machine0 offers persistent VM pricing that can be locked in for longer durations, potentially reducing the per‑hour cost versus spot or on‑demand instances on mainstream clouds.


Originally published on Automations Cookbook.

Top comments (0)