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

# Projects

A **Project** is an organizational container in Amnify Deploy. Its sole purpose is to group related Deployments together so they are easy to find, manage, and understand at a glance.

Think of a Project as a folder or workspace for your Deployments. It holds all the infrastructure deployments that belong to a common theme — whether that is a product, a team, a customer, an environment (staging, production), or any other grouping that makes sense for your organization. Projects do not execute infrastructure or manage cloud credentials; those responsibilities belong to Deployments and Integrations respectively.

***

## Project Properties

| Property           | Description                                                                                     |
| ------------------ | ----------------------------------------------------------------------------------------------- |
| **Name**           | A short, descriptive name (e.g., "Platform Team — Production")                                  |
| **Description**    | An optional longer explanation of the project's purpose                                         |
| **Tags**           | Key–value metadata pairs for categorization and filtering (e.g., `team: platform`, `env: prod`) |
| **Cloud Provider** | The cloud provider this project is associated with (Azure, AWS, or GCP)                         |

***

## When to Create Separate Projects

Common patterns:

**By environment** — one project per environment makes it immediately clear what is running in production versus staging:

* `My App — Production`
* `My App — Staging`

**By team** — each team manages their own infrastructure in isolation:

* `Platform Team`
* `Data Engineering`
* `Frontend Services`

**By customer or tenant** — for organizations that provision infrastructure per customer:

* `Customer A Infrastructure`
* `Customer B Infrastructure`

**By cloud provider** — if your deployments span multiple clouds, a project per provider keeps things organized:

* `Azure Resources`
* `AWS Resources`

***

## Projects and Deployments

Each Deployment belongs to exactly one Project. When you create a Deployment, you choose which Project it belongs to. You can view all Deployments inside a Project from the Project detail page.

Projects do not enforce technical constraints on their Deployments. They are purely an organizational tool.

***

## Tags

Tags are optional key–value pairs you can attach to a Project. They are useful for filtering (quickly find all projects tagged `env: production`), cost tracking (tag with a team or billing code), and recording any project-level metadata your team finds useful.

Tags are free-form — you define the keys and values that make sense for your organization. The format shown in examples throughout this documentation (`key: value`) is a convention, not a required syntax. Use whatever format works for your team.

***

## Next Steps

* [Templates](/cspm-deploy/concepts/templates) — learn about the blueprints that power your Deployments
* [Deployments](/cspm-deploy/concepts/deployments) — understand what a Deployment is and how it works
* [Managing Projects guide](/cspm-deploy/guides/managing-projects) — step-by-step instructions for creating and editing projects