Recommended structuring patterns

STACKIT Resource Manager provides a clear way to organize and manage cloud services. The hierarchy is where you apply and inherit key policies (IAM roles, organizational rules) and manage access, settings, and compliance.

You can choose different patterns to structure your resources. The best pattern depends on team structure, application complexity, and environment requirements.

The following table lists common patterns and use cases.

Pattern	Use cases
Org → Folder(env) → Project(app)	Multi-environment (dev/staging/prod) SaaS applications
Org → Project(monolith)	Small, exploratory, or low-footprint applications
Org → Folder(team) → Project(app/service)	Large enterprises separating teams and services

Pattern explanations and setup

Org → Folder (Environment) → Project (Application)

Use when you need clear separation of environments (dev, staging, prod). Policies and access controls applied at the folder level secure all projects in that environment.

• The organization is created automatically with your customer account.

• Create separate Folders for each environment (dev-folder, staging-folder, prod-folder).

• Create Projects inside the relevant environment Folder for each application (for example, app-api-project in prod-folder).

Org → Project (Monolith)

Use for a a smaller, self-contained application that does not require complex environment or team segmentation. It provides the simplest hierarchy for quick setup.

• The Organization is created automatically with your customer account.

• Create a single Project under the Organization to contain all resources for the application.

Org → Folder (Team) → Project (Application/Service)

Use for large organizations with multiple independent teams. By assigning a Folder to each team, you can delegate IAM permissions and manage budget or billing per team.

• The Organization is created automatically with your customer account.

• Create separate Folders for each team (team-a-folder, team-b-folder).

• Create Projects inside the team’s Folder for each application or microservice the team owns.