Projects let you organize your DigitalOcean resources (like Droplets, Spaces, and load balancers) into groups that fit the way you work. You can create projects that align with the applications, environments, and clients that you host on DigitalOcean.
Projects are available at no cost.
Projects are available for resources in all regions, and resources from multiple regions can belong to the same project.
Projects are a high-level organizational tool designed to make it easier to focus and navigate the control panel when your infrastructure scales. Using projects lets you sort resources into groups that match what you use those resources for. You can separate resources for different applications, work for different clients, or development and production environments.
All of your resources start in a single default project. You can move resources between projects in bulk or one at a time, and you can populate new projects when you create them.
There are three types of resources:
| Project-Based Resources | Droplet-Based Resources | Independent Resources |
|---|---|---|
| Must belong to a project | Belong to projects via associated Droplet | Cannot interact with projects |
|
|
|
Project-based resources form the foundation of a project. All project-based resources must belong to a project, and you can directly assign them to one. If you create a project-based resource without a project specified, it is added to the default project.
Droplet-based resources are related to projects via the Droplet they’re associated with. You can access these resources from within a project through their associated Droplet or, in the case of floating IPs, directly from the project dashboard.
Independent resources do not interact with projects.
You cannot assign unattached volumes to a project. We plan to add support for unattached volumes in the future.
You cannot delete the default project without setting another project as the default first.
There is currently no limit on the number of projects per account, but we may implement reasonable limits in the future.
You cannot assign Kubernetes clusters (or the underlying Droplets in a cluster) to a Project.