# Develop blueprints

> A blueprint defines a service users can order and what Cloud Management Platform (CMP) does at each stage of that service's life

---

Site [llms.txt](/llms.txt)

---

A blueprint is what appears in the [Catalog](/docs/cmp/use/catalog/). It describes how the service is provisioned, how it is torn down, and which operations users can run on it as [resource actions](/docs/cmp/use/orchestration/actions/resource-actions/). It can define something as simple as a single server or as involved as a multi-tier application stack.

Blueprints also connect to groups and environments, which gives you access control and [parameter](/docs/cmp/configure/order-forms-and-pricing/parameters/) inheritance. This section covers blueprint development; see Using the platform for [how to manage existing blueprints](/docs/cmp/use/blueprints/).

---

Section pages:

- [Server blueprints](/docs/cmp/developer-resources/guide/blueprints/server/): The smallest useful blueprint deploys a single server
- [XaaS blueprints](/docs/cmp/developer-resources/guide/blueprints/xaas/): Use XaaS blueprints to create Catalog entries for services Cloud Management Platform (CMP) does not natively support
- [Deployment trigger points](/docs/cmp/developer-resources/guide/blueprints/deployment-trigger-points/): Orchestration actions run your code at fixed points in an order or job, applying reusable behavior everywhere it's needed