NOME Cloud Workspaces

A NOME Cloud Workspace is a managed Code host you don't run or maintain. NOME provisions an isolated workspace, runs your work there, and tears it down when the session ends. It's the option to reach for when you don't want to pair and keep a machine of your own online.

Cloud Workspaces use the same run contract and receipts as a local host — the difference is who operates the box.

Each Cloud Workspace session is isolated per session: separate filesystem and process space, cleaned up at the end. Tenant and org boundaries are enforced at every layer, so your code and data don't cross into another tenant's workspace.

Cloud Workspaces bill in two ways. With NOME Credits, hosted inference and managed compute are metered against your subscription. With BYOK, you attach your own provider API keys and pay the provider directly while NOME provides the workspace, memory, routing, and receipts. See BYOK & NOME Credits.

Because a Cloud Workspace is managed compute plus inference, it consumes credits while active. Sessions have a timeout and are torn down when idle or when the session ends, so you aren't billed for an idle box. Long-running work should checkpoint to a work item (which is durable shared truth) rather than rely on the workspace persisting.

Provider subscription seats do not run in a NOME-managed Cloud Workspace. The cloud Codex seat is not implemented, and NOME cloud does not store or copy ChatGPT/Codex subscription tokens. In a Cloud Workspace, use NOME credits or BYOK for inference. To use a provider seat, run it on a host where you signed in — your Mac, owner-edge, or your own VM. Use provider seats on your own trusted computer or private workspace.

Choose a Cloud Workspace for zero-maintenance, burst, or throwaway work, and when you'd rather pay credits than operate a machine. Choose your own host (This Mac, owner-edge, or your own VM) when you need your local files and toolchain, want to use a provider seat you signed into, or want to run local models with no per-token cost.