Features
- Resource organization — Group VMs, volumes, snapshots, and backups into logical projects
- Environment separation — Keep production, staging, and development resources isolated
- Team collaboration — Share project access with team members
- Flexible structure — Create as many projects as you need with no nesting restrictions
Supported Resource Types
Projects can contain the following resource types:| Resource Type | Description |
|---|---|
| Virtual Machines | Compute instances |
| Volumes | Block storage volumes |
| Snapshots | Point-in-time snapshots |
| Backups | Automated backup files |
| Backup Schedules | Recurring backup policies |
Project Limits
| Resource | Limit |
|---|---|
| Projects per account | No hard limit |
| Resources per project | No hard limit |
| Project name length | 255 characters |
API Endpoints
| Operation | Method | Endpoint |
|---|---|---|
| List Projects | GET | /api/v1/projects |
| Create Project | POST | /api/v1/projects |
| Get Project | GET | /api/v1/projects/{id} |
| Update Project | PATCH | /api/v1/projects/{id} |
| Delete Project | DELETE | /api/v1/projects/{id} |
Best Practices
- Use descriptive names —
prod-backend,staging-ml-pipeline,dev-frontend - One project per environment — Separate production and non-production resources
- Clean up regularly — Delete empty projects to keep your account organized
- Document with descriptions — Add descriptions to projects so team members understand their purpose