ORVYN Cloud
Close the laptop.
The mission keeps running.
ORVYN Cloud runs missions on isolated cloud workers with their own workspace, Cloud Browser and Live Desktop — so long jobs finish overnight and report back verified.
Local to cloud
Start on your machine. Hand off in one step.
Missions keep their context when they move, so nothing starts over.
- 01
Start locally
Begin a mission in the ORVYN app next to your files, terminal and Docker.
- 02
Hand off
Switch execution to Cloud. The workspace, plan and history move to a fresh worker.
- 03
Walk away
The worker keeps going — tests, load checks, browser runs — while your laptop is closed.
- 04
Review
Come back to a verified result, evidence and a pull request, or a clear question if it needs you.
Local or cloud?
Choose per mission, not per account.
Most people use both: local for work that needs their machine, cloud for work that needs time or isolation.
| Capability | Local (Windows app) | Cloud worker |
|---|---|---|
| Your files, tools and Docker | Included | Limited |
| Keeps running with the laptop closed | Not included | Included |
| Isolated machine per mission | Not included | Included |
| Cloud Browser and Live Desktop | Included | Included |
| Many missions in parallel | Limited | Included |
| Connected servers via Secrets Vault | Included | Included |
Included IncludedLimited Limited or on requestNot included Not included
Cloud workers
What every worker gives a mission.
Its own sandbox
One mission per worker with its own filesystem and processes. Nothing leaks between missions or tenants.
A persistent workspace
Files, dependencies and history survive restarts, so an eight-hour job does not start over at hour six.
Browser and desktop
A Cloud Browser for web checks and a Live Desktop for anything visual, both watchable and controllable.
Long-running missions
Load tests, large refactors and migrations run for as long as they need, within your budget.
Parallel capacity
Run several missions at once on separate workers and review them in one list.
Reports back
A notification when the mission is verified, blocked, or waiting for your approval.
A night on a worker
What “long-running” looks like.
An example mission — “Harden checkout under load” — handed to a cloud worker at 22:11.
22:10 · Started locally
ORION reproduces slow checkout requests against the staging database.
22:11 · Moved to cloud-worker-1
You close the laptop. The worker picks up the plan, workspace and history.
23:48 · Tests and fixes
312 tests run, three failures traced to a connection pool and fixed.
02:05 · Load test
A load test against staging passes the latency target you set.
06:40 · Ready for review
Pull request opened with the evidence attached. Nothing deployed without you.
Questions
ORVYN Cloud questions
What is an ORVYN cloud worker?
A cloud worker is an isolated machine that runs one ORVYN mission with its own workspace, Cloud Browser and Live Desktop. It keeps running when your computer is off.
Do I need the Windows app to use ORVYN Cloud?
No. You can create an account and run missions on cloud workers directly. The Windows app adds local execution next to your own files and tools.
Can a mission move from my computer to the cloud?
Yes. Switch the mission’s execution to Cloud and it continues on a worker with the same plan, workspace and history.
Are cloud workers shared between customers?
No. Each worker runs one mission in its own sandbox, and tenant data stays within that tenant’s boundary.
How do cloud workers reach my servers?
Through resources you connect in ORVYN. Credentials stay in the Secrets Vault and are used by reference inside the runtime; the model never receives them.
Stop prompting.
Start delegating.
Give ORVYN the goal and stay focused on what matters.