Spin up an Omarchy sandbox in the cloud in seconds. Try the dotfiles, the install script, the tool you found on a forum. If it goes wrong, restore a checkpoint. Your laptop never knew.
2 sandbox hours a month on the free tier. No card.
A clean machine with Omarchy's terminal tools, ready for whatever you are too nervous to try at home. Develop without fear, test an install script, reproduce a bug from a clean slate.
every tierYour own setup, your tools, your dotfiles, your projects, copied from your Digital Twin. The starting point for a new agent or digital employee that should work the way you do, without being you.
with a Digital Twin, Plus and up · rolling outBefore a copy of your twin boots, every credential is removed from it. If that step fails for any reason, the copy is destroyed instead of started.
Agent and AI tool logins, git and cloud command-line credentials, SSH private keys, keyrings and password stores, browser profiles, shell histories, .env files, token and certificate files.
Your code, your configs, your installed tools, your public keys and your .env.example files. Everything a new agent needs to be useful on day one.
Give the new agent its own accounts and keys, scoped to its job. Revoke them without touching yours.
creating sandbox "bookkeeper" from a copy of milton… ✓ machine ready · Medium · 2 vCPU · 4 GB ✓ home copied · 11.2 GB ✓ credentials removed · 23 items ✓ ready · stopped omarchy@bookkeeper ~ $ ls ~/.ssh config id_ed25519.pub known_hosts omarchy@bookkeeper ~ $ gh auth status You are not logged into any GitHub hosts. omarchy@bookkeeper ~ $
A shell on the sandbox, right in your browser. The whole machine is yours: install, compile, break.
availableA tiling Hyprland session with your terminals in it, streamed to the browser. For when one pane is not enough.
comingThe complete Omarchy desktop, bar and all, in a browser tab. Test a theme, a keybinding, a whole new install.
comingSnapshot before the risky part, restore after. As many as your tier's checkpoint count; the oldest rolls off.
After 30 idle minutes a running sandbox stops, and no single run lasts past 12 hours. A stopped sandbox only costs its disk.
Its own machine and its own disk, separate from your laptop and from every other customer's sandboxes.
Install an agent inside a sandbox and let it work somewhere mistakes are cheap and a checkpoint away from undone.
Every tier includes sandbox hours, counted the same whatever the size. Past them, a running sandbox costs its size's hourly rate, prorated by the minute. Disk counts toward your tier's storage.
1 vCPU · 2 GB RAM · 10 GB disk
$0.09 per hour past your included hours
Fan and up2 vCPU · 4 GB RAM · 20 GB disk
$0.18 per hour past your included hours
Plus and up4 vCPU · 8 GB RAM · 40 GB disk
$0.35 per hour past your included hours
Pro and up| Tier | Sandboxes at once | Included hours / month | Largest size |
|---|---|---|---|
| Fan | 1 | 2 h | Small |
| Plus | 2 | 10 h | Medium |
| Pro | 5 | 40 h | Large |
| Studio | 20 | 120 h | Large |
Desktop access is priced when it ships. Full pricing.
Today a sandbox is a Linux machine with the Omarchy terminal toolset, which is what the terminal access needs. The full Omarchy install, Hyprland and all, arrives with desktop access.
Yes. Stop it and it waits, costing only its disk, until you start it again or destroy it.
Mine cryptocurrency, attack other systems, or anything else in the acceptable-use policy. The rules are the same as everywhere else here.
No. It is a copy taken when you create the sandbox. Your twin keeps following your laptop; the sandbox goes its own way.