> ## 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.

# Introduction to Amnify Deploy

**Amnify Deploy** is the infrastructure provisioning module of the Amnify platform. It enables your team to provision, manage, and tear down cloud resources across **Azure**, **AWS**, and **GCP** using a visual, guided interface, without writing infrastructure code directly.

***

## What Problem Does It Solve?

Provisioning cloud infrastructure traditionally requires deep expertise in Infrastructure-as-Code (IaC) tools, familiarity with cloud provider APIs, and careful coordination across teams. This creates bottlenecks: developers wait for infrastructure teams, and project managers have no visibility into what is deployed or where.

Amnify Deploy removes these bottlenecks by:

* Providing a **self-service experience** so developers can provision infrastructure on their own
* Giving project managers and product owners **full visibility** into what is deployed and its current state
* Enforcing **built-in approval gates** so no infrastructure change goes unreviewed
* Providing an Amnify-managed template catalog while allowing your organization to **own and version custom infrastructure blueprints** through your GitHub repository

***

## Key Capabilities

| Capability                         | Description                                                                                                                                                                        |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Comprehensive template library** | Amnify provides a production-ready library of templates for Azure, AWS, and GCP, covering infrastructure, data, application, and combination use cases — ready to use from day one |
| **Multi-cloud support**            | Deploy to Azure, AWS, and GCP from a single interface                                                                                                                              |
| **Approval workflows**             | Every deployment goes through a plan-and-approve cycle before any change is made                                                                                                   |
| **Pipelines**                      | Orchestrate multiple deployments in a defined sequence with a single trigger                                                                                                       |
| **Full execution history**         | Every run is logged, tracked, and available for review                                                                                                                             |
| **Flexible customization**         | Extend the provided library or author entirely new templates, with direct support from the Amnify team when needed                                                                 |

***

## How It Works

Amnify Deploy is built around four building blocks that work together:

```mermaid theme={null}
flowchart LR
    AC["Amnify Template Catalog"]
    GH["Your GitHub Repo<br/>(Custom Templates)"]
    P["Projects<br/>(organize)"]
    D["Deployments<br/>(instances)"]
    PL["Pipelines<br/>(sequences)"]

    AC -->|admin sync| P
    GH -->|sync| P
    P --> D
    D --> PL
```

1. **Templates** come from the Amnify-managed catalog and, when configured, your organization's GitHub repository. Customer-owned templates are shown before Amnify templates in Browse Templates. Platform admins sync Amnify-managed catalog changes from the admin panel; organization owners/admins sync customer templates from the selected GitHub source.

2. **Projects** are organizational containers. They group related deployments together — for example, all infrastructure for a specific product, environment, or team.

3. **Deployments** are instances of a template applied to a specific cloud environment with specific variable values. A single template can be deployed many times across different projects, regions, or cloud accounts.

4. **Pipelines** chain multiple deployments together and execute them in a defined order, useful when infrastructure components depend on each other and must be provisioned in sequence.

***

## Who Is This For?

**Developers** use Amnify Deploy to provision the infrastructure their applications need without waiting for an ops team, understand exactly what will be created before any change is applied (via the plan approval step), and track execution logs and debug failures directly in the interface.

**Product Owners and Project Managers** use Amnify Deploy to get visibility into what infrastructure exists and its current state, understand deployment history and who triggered each change, and coordinate multi-step infrastructure rollouts using Pipelines.

***

## Where to Go Next

<Columns cols={2}>
  <Card title="New to Amnify Deploy?" href="/cspm-deploy/concepts/overview">
    Start with [Core Concepts](/cspm-deploy/concepts/overview) to understand the key building blocks, then follow the [Quickstart Guide](/cspm-deploy/getting-started/quickstart) for your first deployment.
  </Card>

  <Card title="Ready to get hands-on?" href="/cspm-deploy/getting-started/prerequisites">
    Go directly to [Prerequisites](/cspm-deploy/getting-started/prerequisites) to make sure your environment is set up, then jump into the [How-To Guides](/cspm-deploy/guides/creating-deployments).
  </Card>
</Columns>