> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nscale.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects

> Understand how projects group and isolate your resources across Nscale services.

## What is a project?

A **project** is a logical container for your Nscale resources. It provides an isolation boundary for:

* Compute resources (instances, clusters)
* Networking (VPCs, security groups)
* Storage and other shared services

Projects help you organise workloads by team, environment (e.g., staging vs. production), or application, and make it easier to reason about where resources live.

## What lives inside a project?

When you create resources in Nscale, you place them into a project. For example:

* **Instances** – virtual machines you create from the **Compute → Instances** page
* **Kubernetes clusters** – managed clusters you create from the **Services → Kubernetes** page
* **Networks and security controls** – VPC networks and security groups associated with the project

These resources are associated with a single project at creation time so that usage, access, and configuration are grouped together.

## Creating and managing projects

You can create and manage projects directly from the Nscale Console.

At a high level:

1. From the Console, select **All Projects** in the left navigation.
2. Create a new project and give it a clear, descriptive name (for example, `team-ml-prod` or `payments-staging`).
3. Use this project when creating instances, clusters, and related resources so they are grouped together.

You can return to **All Projects** at any time to review existing projects and adjust basic details such as the project name.

## How projects show up across services

Many flows in the console ask you to choose a **project**, including:

* Creating a new **instance** from **Compute → Instances**
* Creating a new **Kubernetes cluster** from **Services → Kubernetes**

In these flows, the selected project determines **where** the new resource is created and which other project-scoped resources (like networks and security groups) it can see.

If you are unsure which project to use, align with your team’s conventions (for example, one project per environment or per team) before creating long‑lived resources.

## Notes and limitations

Projects are designed to be stable containers for your workloads. In general, resources are created into a project and managed there for their lifetime. If you need to reorganise how your workloads are grouped, plan ahead and coordinate any resource moves or recreations with your team.