On this page
Projects
A project is an isolated environment that holds its own resources, quotas and members. Use separate projects to keep teams, clients or environments such as production and staging cleanly apart.
Everything you create in the console (instances, networks, volumes, secrets, load balancers and so on) belongs to exactly one project. Resources in different projects are isolated from one another, and each project carries its own quotas and its own billing profile.
You switch the active project from the selector in the console; new resources are created in whichever project is active. A project can be enabled or disabled, and can only be deleted once it no longer holds active resources.
Key concepts
Project — An isolated tenant that owns resources, quotas and members.
Active project — The project new resources are created in; chosen with the console's project selector.
Creator — The user who created the project; holds ownership of it.
Billing profile — The per-project billing context, viewable from the project's actions.
Status — Whether a project is enabled or disabled.
Before you start
- A verified account in good standing.
- A clear idea of how you want to separate work (by team, client or environment).
Step by step
- Open Projects
Go to Projects to see every project you belong to, with its status and a tag marking the current one.
Screenshot — The Projects table with the Create project buttonThe Projects table with the Create project button - Create a project
Choose Create project, give it a name and a short description. Default security groups are set up for it automatically.
Screenshot — The Create project dialogThe Create project dialog - Switch to it
Click the project row (or use the project selector) to make it active. The console reloads in the new project's context.
- Create resources
With the project active, any instance, network or other resource you create belongs to it.
- View billing or members
Use the project's actions menu to open its billing profile, view members, invite people or manage application credentials.
Screenshot — The project actions menuThe project actions menu - Disable or delete
Disable a project to pause its use, or delete it once it is empty. The console checks for active resources before allowing deletion.
Examples
patrii project list patrii project switch staging
Limits & specifications
Project actions:
| Action | What it does |
|---|---|
Switch | Makes the project active for new resources. |
View members | Shows who belongs to the project and their roles. |
Invite | Adds a person to the project with a role. |
Billing profile | Opens the project's billing context. |
Disable | Pauses the project without deleting it. |
Delete | Removes the project once it holds no active resources. |
Best practices
- Separate production and staging into different projects so quotas and blast radius stay contained.
- Give each project a descriptive name and description so teammates understand its purpose.
- Confirm which project is active before creating expensive resources.
- Delete empty projects you no longer need to keep the list tidy.
FAQ
Why can't I delete my project?
Do resources move between projects?
I created a resource in the wrong project.
Learn more
Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.