Projects are the top-level organizational unit in Uncloud. Every resource — Droplets, Apps, Volumes, Databases — belongs to a project. Each project maps directly to a Kubernetes namespace, providing strong isolation between workloads.

​
How Projects Work

When you create a project, Uncloud:
  1. Generates a unique project ID (e.g., proj_a1b2c3d4)
  2. Creates a corresponding Kubernetes namespace
  3. Scopes all subsequent resources to that namespace

​
Default Project

On first launch, Uncloud creates a default project (proj_default). All resources created without specifying a project are placed here.

​
Resource Scoping

All API endpoints automatically scope resources to the active project. This means:
  • GET /api/v1/droplets returns only droplets in the current project
  • POST /api/v1/apps creates the app in the current project
  • Resources in different projects are completely isolated

​
Project Settings

Each project can have its own settings, configured independently from global settings:
  • Resource quotas (CPU, memory, storage limits)
  • Default regions
  • Networking policies
  • Backup policies

​
Kubernetes Namespace Mapping