> For the complete documentation index, see [llms.txt](https://docs.infraglide.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraglide.com/templates-and-reference-architectures/library.md).

# InfraGlide Template Library

**Templates** (Blueprint Library) ship ready-made reference architectures you can turn into a draft pipeline in one step. Open **Build & Deploy → Templates**.

***

### What Ships in the Library

Templates are **static client bundles** (TypeScript data under the app), not rows loaded from a templates database table. The library combines AWS, GCP, and Azure catalogs into `ALL_TEMPLATES` (on the order of **70+** designs).

#### Categories

* End-to-End
* Networking
* Compute
* Data & ETL
* Storage & CDN
* Security & IAM
* Observability

Filter by provider (**All / AWS / GCP / Azure**) and category in the UI.

#### Representative examples

**AWS:** Three-Tier Web App, Serverless API, Multi-AZ VPC Network, S3 Data Lake + Glue ETL, ECS Fargate Microservices, IAM Least-Privilege Baseline, CloudFront + S3 Static Site, EKS Production Cluster, Aurora + Lambda API, and more.

**GCP:** GKE + Cloud SQL + GCS, Cloud Functions + Firestore, BigQuery Data Warehouse, VPC + Subnets + Router & Firewall, Workload Identity + IAM, Dataproc / Bigtable / AlloyDB patterns, CDN + Load Balancer, and more.

**Azure:** AKS + Azure SQL + Blob Storage, Azure Functions + Cosmos DB, Hub-Spoke VNet + NSG, Azure Data Factory + Data Lake, App Service + SQL + Redis, VM Scale Set patterns, Event Hubs pipelines, and more.

Browse the Templates page for the full live list — names evolve as templates are added.

***

### Using a Template

1. Select the target **Workspace / Sandbox** in the header (required).
2. Open **Templates** and pick a card.
3. Confirm in **Use template** — InfraGlide creates a pipeline with `status: "draft"` and `isTemplate: false` (a real editable pipeline, not a linked template instance).
4. You land in the Pipeline Designer with components preloaded.
5. Attach a credential, fill required fields, **Save**, **Preview**, **Deploy**.

***

### Generate with AI

The Templates page also offers **Generate with AI**, which calls Jane to synthesize a template-like design from a natural-language description and provider. That path creates a design for the current session; it is not the same as saving a shared org template library entry.

See [Jane AI Overview](/jane-ai-copilot/overview.md).

***

### Tips

* Match the template’s provider to an allowed org provider and a credential in that Sandbox.
* Treat templates as starting points — always Preview before Deploy.
* For existing Terraform, prefer **Import Terraform** / Template Converter instead of forcing a mismatched blueprint.

***

### See also

* [Custom Organization Templates](/templates-and-reference-architectures/custom-templates.md)
* [Quickstart Guide](/getting-started/quickstart.md)
* [Designer Interface Overview](/visual-canvas-and-pipeline-designer/interface-overview.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.infraglide.com/templates-and-reference-architectures/library.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.