Skip to main content

How It All Fits Together

Before diving into the individual concepts, it helps to understand how all the pieces of Amnify Deploy relate to each other. This page provides a mental model you can refer back to as you explore the rest of the documentation.

The Four Building Blocks​

Amnify Deploy is built around four entities. Each has a clear, distinct role:

EntityRoleLives in
TemplateThe what — defines what infrastructure can be createdYour GitHub repository
ProjectThe where — groups and organizes related deploymentsAmnify Deploy
DeploymentThe instance — a template applied to a specific environmentAmnify Deploy
PipelineThe sequence — orchestrates multiple deployments in orderAmnify Deploy

Entity Relationships​

Key relationships to understand:

  • One Template can be used by many Deployments across many Projects
  • One Project can contain many Deployments (but each Deployment belongs to one Project)
  • A Pipeline references existing Deployments; it does not create new ones

The Deployment Lifecycle​

When a Deployment is executed, it goes through a structured lifecycle with two required approval gates:

Both approval gates are intentional safety mechanisms. No infrastructure change is applied without a human reviewing what will happen first. See Deployment Lifecycle for the full breakdown.

Templates Live in Your Repository​

A critical aspect of Amnify Deploy is that you own your templates. They are not locked inside the Amnify platform. Your templates live in a GitHub repository under your organization's control, and Amnify Deploy syncs from that repository. You can add new templates, update existing ones, and version everything through standard Git workflows.

Continue reading the individual concept pages in order:

  1. Projects — How to organize your work
  2. Templates — Your infrastructure blueprints
  3. Deployments — Instances of templates in action
  4. Pipelines — Orchestrating multiple deployments
  5. Deployment Lifecycle — Statuses, approval gates, and the execution flow