Projects and VMs

1:1 on purpose

Each Orca Cockpit Project is exactly one dedicated Linux VM plus its filesystem. There is no shared pool of anonymous VMs behind a single chat. When you switch Projects, Ask / Plan / Agent and the VM view switch with it.

• The website creates your default t3.large Project on first account visit. Extra Projects are created on /access (create / start / stop / retire).
• Sizes you may see: t3.small (optional extra, 2 vCPU · 2 GiB) and t3.large (default, 2 vCPU · 8 GiB, first included in the $50 plan). Add-on prices are stubs until Checkout is live.
• Status: queued → provisioning → ready (URL) or error.
• Ready Projects typically open over HTTPS noVNC for this soft launch.

Why the VM exists

Mule builds, Maven, and OAuth consent need a real machine. The laptop app is the companion IDE; the Project is where code and browser handoffs live. Banking, government, and enterprise benches keep client Anypoint work off a personal laptop image.

Website vs desktop

/access is the Projects control plane: create, start, stop, and retire. JSON still uses workspaces / workspaceId so existing desktop clients keep working. Provisioning is performed by our infra webhook, not by AWS keys in this Next.js app.