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 Project on first account visit. Extra Projects are created on /access (create / start / stop / retire).
• Locked sizes: t3.medium (7-day trial), t3.large (included in $149 starter), t3.xlarge (+$50), t3.2xlarge (+$150). EE +$35 requires t3.large or larger. Salesforce +$50, Postman +$25, GitHub +$25. Checkout is not 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.