Workspaces and environments

Workspaces

A workspace is one canvas with its own members, quotas, private network and activity log. Use one per project or client. Workspaces (g w) lists yours.

Duplicate copies a workspace’s nodes and links. Data in databases and storage, code history, domain names and secrets (Git tokens, webhook secrets) are not copied.

Environments

An environment is a copy of a workspace for sandbox, QA or production, with its own resources, quotas and members. Each app follows its own branch.

1. Open Workspace settings → Environments (owners only).

2. Pick a preset or type a name. Presets set the branch each app follows:

   Environment	Branch
   sandbox	develop
   qa	release
   prod	main

3. Create environment. The copy is staged; press Deploy in it to start it.

Environment variables are copied, so review them (you probably want different keys in production). Domains, ports and volumes are not copied.

Move a tested build forward with Promote: see Promoting between environments.

Quotas

Workspace settings can cap the workspace at a number of apps, memory, CPU and storage (blank means no cap beyond your plan). Usage bars at the top show what’s used, and a lighter segment shows what your staged changes would add. They turn amber at 80% and red at 100%.

Quotas are checked when you press Deploy: planning and staging are never blocked, but a deploy that would go over is refused, and nothing is deployed.

Activity

Activity lists who changed what and when: deploys, edits, links, sign-ins to shells, approvals, and actions taken by tokens and AI agents. Owners can see it. Secret values are never logged, only key names.