Projects are available at no cost.
Projects are available for resources in all regions. Projects are not region-specific, so resources from multiple regions can belong to the same project.
Every account starts with a default project, and existing customers will find their existing resources already organized into this default project. You can edit a project’s name, purpose, and description after its creation.
You can move resources into new projects in bulk when the project is created or afterward. You can also move them one at a time out of one project into a different one.
Supported resources form the foundation of a project. These include:
All supported resources must belong to a project, and you can directly assign them to one. If you create a supported resource without a project specified, it will be added to the default project.
Related resources are related to projects via the Droplet they’re associated with. These include:
You can access these resources from within a project through the Droplet-specific menu or, in the case of floating IPs, directly from the project dashboard.
Independent resources do not interact with projects. These include:
Projects are only available for the control panel, but API support is planned for the future.
You cannot assign unattached volumes to a project, but volumes support is planned for 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 reasonable limits may be put in place in the future to facilitate usability.
You cannot assign Kubernetes clusters (or the underlying Droplets in a cluster) to a Project.