The free Digital Twin plugin mirrors your working session to the cloud. Omarchy.Fans Cloud gives that twin a home: a machine that keeps computing when the lid is shut, checkpoints you can roll back to, and a door you can open from any browser.
Your home directory, your tmux sessions and your running work, mirrored to a cloud machine and kept in step. Close the lid and it takes over; open it and everything comes home. Snapshot it any time.
20 GB on Plus · $0.05 / GB-month overThe same twin as a cloud computer you open from any browser. Check a long build from your phone, or finish a thought on a borrowed laptop.
10 h on Plus · then $0.16 / hourA twin is not two copies fighting over the same files. It is one session with a lease that says who is allowed to change things right now. The lease flips only after a sync has been confirmed.
On lid close or shutdown the plugin pushes your session, waits for the cloud to confirm, then hands over the lease. If the push fails, the lease stays with the laptop and nothing runs twice.
Snapshot the twin at any moment, with a comment. Restore any of them later. Plus keeps 5, Pro 30, Studio 100.
When you return, the laptop pulls what changed in the cloud, confirms, and takes the lease back. Only the differences travel, over an encrypted tunnel.
While the cloud holds the lease it must renew every 15 minutes. Set a maximum of cloud hours per handoff and it will never quietly run for a week.
Start a Sandbox from a copy of your twin and a new agent begins with your tools and dotfiles, minus every credential.
Sign the twin plugin in with a device code and it uses Omarchy.Fans Cloud: no hosting account, no tunnel setup, no keepalive scripts. preview
Open the Cloud dashboard, pick your twin, press start. Your session is there, in a terminal in the browser, running on the twin's own cloud machine.
The browser terminal works now. The full Hyprland desktop streamed to the browser is on its way.
After 30 idle minutes it stops, and it never outlasts the twin's cloud-hour cap. The meter stops with it.
If your laptop still holds the lease, the dashboard says so: changes you make in the browser are replaced by the laptop's next push unless you hand the lease to the cloud first.
omarchy.fans/app · twins · milton · start ✓ running · lease: cloud · 0.4 of 10 h this month ~/work/site $ git status On branch feat/pricing Your branch is ahead of 'origin/feat/pricing' by 2 commits. ~/work/site $ npm test ✓ 48 passing (3s) ~/work/site $
When the laptop syncs back it only adds and updates. Files that exist on the laptop but not in the cloud are left alone. Deletions are yours to make, by hand, with the lease in your hand.
SSH keys, tokens, browser profiles, password stores and anything you list in the exclude file stay on the laptop. The twin gets your work, not your identity.
Our API refuses to hand the lease to the cloud unless a push was confirmed in the last 15 minutes. A half-finished sync cannot start computing.
Sync runs through an authenticated tunnel, and the twin's disk is encrypted at rest.
| Tier | Twin storage | Checkpoints |
|---|---|---|
| Fan | — | 1 |
| Plus | 20 GB | 5 |
| Pro | 100 GB | 30 |
| Studio | 500 GB | 100 |
$0.05 per GB-month of storage
$0.16 per hour the twin runs in the cloud
Storage is prorated by the hour. Running time, whether you opened the twin in a browser or handed it the lease, counts against your tier's twin hours first.
Full pricing