Workspaces

A workspace is the top-level isolation tier in the NimbusNexus account model. Every project belongs to exactly one workspace; every user has access scoped to workspaces (and to specific projects within them). The hierarchy is workspace → project → resource.

For most accounts, a single workspace is enough. Larger organizations use multiple workspaces to separate billing, access, and resource limits at the org-unit level — e.g. one workspace per business unit, or one per legal entity. Cross-workspace traffic, IAM, and billing are all isolated by design.

Don't confuse a workspace with a DNS zone — same word in some contexts (OpenStack calls workspaces "domains"), but the product surface uses "workspace" everywhere user-facing.

What's next

Projects — the next layer down; what workspaces contain.
Users and Roles — IAM grants are scoped within a workspace.
Cross-project trusts — time-bounded permission across project boundaries inside a workspace.

No endpoints to show

The OpenAPI spec doesn't currently expose any endpoints under theworkspacestag. This is usually a manifest typo; check that the tag matches what the backend serves at /openapi/external.json.

Edit this page on GitHub