Workspaces

A workspace is the unit of isolation. Data, agents, workflows, members, and billing all belong to exactly one.

What is scoped to a workspace

Everything you build, everyone who can see it, and every key that reaches it. Two workspaces share nothing, which is what makes a workspace a safe boundary between production and everything else.

Regions

A workspace is created in a storage region and stays there. The region cannot be changed afterwards, so create the workspace in the region your compliance requirements name.

When to create a second one

Create one when the isolation is the point: a separate environment, a customer whose data must not sit beside another's, or a team with its own billing.

Do not create one just to organise work. Projects inside a workspace do that, and they keep the data model shared.

Switching

The SDK reads FRONTAL_WORKSPACE, and every call accepts an explicit workspace that overrides it. Being explicit in deployed code is worth the extra argument.