Organizations and projects

Organizations are the top-level container in Catalyst — billing, members, and policies attach here. An organization contains one or more regions; each region is a physically isolated unit of the Catalyst data plane (a Kubernetes cluster running a fully managed Dapr deployment).

Projects are the unit of workload isolation within a region. App IDs, components, managed services, and policies are all scoped to a project. Resources in one project cannot be accessed from another. A project maps directly to a Kubernetes namespace.

Each project also exposes a set of network details that applications use to reach it: an HTTP endpoint and gRPC endpoint for the Catalyst Dapr APIs, an ingress address for the data plane, and an egress address that Catalyst uses as the source IP for callbacks. These values are shared by every App ID in the project — see Connect to Catalyst for how applications wire them up.

For day-2 operations on projects (creating, listing, deleting), see Projects. For organization-level identity and access, see Identity and Access.