Cloud workspaces

ForgeDeck cloud workspaces — hosted, isolated remote dev environments.

Embed
Preview of the card
<a href="https://docs.forgedeck.net/cloud-workspaces"><img src="https://docs.forgedeck.net/_api/public/orgs/db9cb8ff-b606-46cf-bbcd-02c8f8a9a3e2/spaces/6f417400-93ca-41a8-a914-df2ae3981dc6/pages/ea8071c9-25be-4ab3-9843-113d435a1008/social-card.svg?v=3e7ae33eec8b" alt="Cloud workspaces" width="600" height="315"></a>

Cloud workspaces are hosted, isolated dev environments you can drive from the desktop app — for when you want agents running off your laptop, on a bigger box, or from anywhere.

What they are

Each workspace is an isolated, hardened container (or microVM) with your project cloned in. A cloud terminal in ForgeDeck bridges to the workspace over a secure WebSocket — the same deck UX, running remotely.

Getting one

Cloud workspaces are a paid feature (Pro and up). Create one from the Cloud tab:

  • Clone mode — point it at an https git repo.

  • Upload mode — push a local project up.

Security

Workspaces are tenant-isolated, run as a non-root user with dropped capabilities, and are reached only through an authenticated proxy — the connection uses a one-time ticket, never your long-lived session token in a URL. Inputs you submit to server-executed features are processed transiently and never stored as raw transcripts.

See Accounts & billing for plans, and Hosted MCP for the multi-tenant gateway.

Updated