A window per VM
Every machine runs in its own process and window, with its own desktop shortcut. Close the window and the VM keeps running; open it again in an instant.
Console & per-VM windows →Real VMs in one app, and your AI agent can drive them too through built-in MCP. Also on Windows and Linux.
AI-first, by design
Most VM tools bolt automation onto the side. SlateVM puts a Model Context Protocol server inside the layer that owns the virtual machines, so an agent gets the same authority as the app: create, start, see, type, click, run, diagnose, and clean up — through 46 structured tools that behave the same on every host operating system.
Example agent request
“Create an Ubuntu VM with 4 CPUs and 8 GB RAM, install my project, run the tests, fix anything that fails, and leave the machine running for me.”
create → install → see → act → verify → hand off
Hosts and guests
| Host | macOS guests | Linux guests | Windows guests |
|---|---|---|---|
| Mac · Apple silicon | ✓ | ✓ | ✓ |
| Windows · x64 & ARM64 | — | ✓ | ✓ |
| Linux · x64 & ARM64 | — | ✓ | ✓ |
macOS guests require a Mac host. Windows hosts need Windows 10 or 11 Pro, Enterprise, or Education.
The experience
Every machine runs in its own process and window, with its own desktop shortcut. Close the window and the VM keeps running; open it again in an instant.
Console & per-VM windows →SlateVM uses each host’s own virtualization — macOS virtualization on a Mac, the built-in hypervisor on Windows, and the kernel hypervisor on Linux — for direct, fast VMs.
Platforms & engines →Unattended Linux and Windows installs go from ISO to a ready desktop with an SSH-ready account — no clicking — so an agent can start working the moment the VM boots.
See workloads →Made for real work
Reproduce a customer environment, validate installers, isolate a development stack, run tests in a clean machine, or hand an agent a disposable computer — on a Mac, a Windows PC, or a Linux workstation.
AI control runs only on your machine, over a local channel, and each AI client must be approved once before it can act.
Each VM is its own bundle, its own process, and its own isolated guest — scoped access, clean stop and delete, and recoverable state.
Releases are verified before they install, and every platform ships the same version, so your fleet of machines stays consistent.