Workspaces
The unit of isolation — one company or team, one brain, one region.
A workspace is one company's (or team's) brain. Everything — ingested data, memories, agents, API keys — belongs to exactly one workspace, and nothing crosses between them.
- Members have a role:
admin,member, orviewer. Admins connect sources, manage visibility groups, and can manage every API key. - Visibility groups (Engineering, Finance, …) are named sets of members. Admins attach groups to sources to restrict who — and which keys — can see that data.
- API keys belong to the workspace and act as their own agent principal — not as the person who created them. A key created by a member is still capped at that member's current access, and is revoked if they leave.
- Region is fixed at creation: US or EU. See Regions.
The workspace is implicit in every API call: a key can only ever reach the workspace it was created in, so there is no workspace id in API paths.