Platform

Overview

Waldur organizes everything around three primitives: users, organizations, and projects. Users get roles inside organizations or projects; resources are grouped under projects; organizations carry the contractual and financial responsibility. Every other Waldur concept — marketplace orders, calls, invoices, policies, quotas — binds to one of these three.

Structure

Key concepts

Concept	One-liner	Reference
User	A person or robot account; may hold global roles (staff, support).	Glossary
Organization	A legal entity acting as a customer, a service provider, or both.	Glossary
Project	An access-controlled container for resources inside an organization.	Glossary
Role	A named bundle of permissions, scoped to an organization or a project.	Roles & permissions
Resource	A provisioned service instance (VM, HPC allocation, storage volume, ...).	Marketplace
Quota	An enforced upper bound on a measurable property within a scope.	Admin guide

Installation types

Waldur reuses the same primitives across three common installation types:

Type	Typical operator	What an Organization is	What a Project is
Cloud	Commercial or government IaaS	Customer company or agency	Tenant or environment
Academic	Single university or research infra	Department or institute	Research group, lab, course
Academic shared	Multi-institution federation	Always also a service provider	Allocation granted by a federated allocator

The role matrix for each shape — Owner, PI, Service Manager, etc. — is documented in Roles & permissions.

Related concepts

• Marketplace — how a project obtains a resource.
• Lifecycle — what happens to that resource over time.
• Billing — what the organization is invoiced for.
• Quotas — up-front bounds on usage per scope.
• Policies — automated reactions when limits are crossed.
• Identity — how users get into Waldur.
• Support — how tickets reach the right team.
• Call management — how allocations are awarded through a structured proposal process.