Docs
Beta · biscuit · v0.0.1Projects
A Project is a dedicated Linux VM plus the filesystem on that VM.
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 on the left, the center thread and the right-hand VM switch with it.
- The website creates your default Project on first account visit. Extra Projects come from Orca Cockpit IDE. The /access page is a read-only list.
- Sizes you may see: t3.micro, t3.small, t3.medium, 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. Chat in the IDE can ask to create another machine so you are never stranded in a thread that cannot run.
Website vs desktop
/access is a read-only list of Projects. The website creates the default Project; stop and remove from Orca Cockpit IDE (the API path is still POST/PATCH/DELETE /api/workspaces). Provisioning is performed by our infra webhook, not by AWS keys in this Next.js app.