# Key concepts

> The core concepts behind Cloud Management Platform (CMP), and the external systems it integrates with

---

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

---

## Core concepts

| Concept | Description |
| --- | --- |
| Resource handlers | A resource handler is a connection to a cloud platform or virtualization technology, such as AWS, Azure, GCP, or VMware. Each resource handler provides CMP with visibility and control over resources on that platform. |
| Environments | An environment is a logical grouping of resources within a resource handler, such as an AWS region or a VMware cluster. Environments define which VM images, networks, and configuration options are available when users place orders. |
| Servers | A server is CMP's record of a compute resource, either a virtual machine or a physical server. Servers can be provisioned through CMP or discovered automatically by scanning a connected resource handler. Each server belongs to one environment and one group, and can be managed, tracked, and acted on throughout its lifecycle. |
| Groups | Groups organize users and facilitate access to environments, blueprints, and resources. Roles and quotas are applied at the group level to control what members can see, use, and request. |
| Catalog | The catalog is the self-service portal where users browse and order blueprints. Administrators can control which blueprints appear in the catalog. |
| Blueprints | A blueprint defines a repeatable, orderable service. Blueprints include build steps, management actions, and teardown logic, and are ordered by users through the catalog. |
| Orchestration | Orchestration allows administrators to automate actions at defined trigger points, such as during provisioning, on a schedule, or in response to an event. Actions can run plugins, remote scripts, webhooks, or integrate with external systems. |
| Networks | Networks define the subnets and VLANs available to servers in CMP, derived from your resource handlers. They can be assigned to environments to control network options during provisioning. |

## External integrations

CMP integrates with a range of infrastructure technologies for provisioning, orchestration, and self-service operations.

| Integration type | Description |
| --- | --- |
| Configuration managers | Install software and manage server configurations using tools such as Ansible, Puppet, or Chef. |
| Container orchestrators | Manage containerized workloads, such as Kubernetes pods and services. |
| IT service management (ITSM) | Integrate with ServiceNow to enable catalog-driven ordering and approval workflows. |
| Load balancers | Configure load balancer resources as part of an application deployment. |
| IP address management (IPAM) | Automatically assign IP addresses using an integrated IPAM solution such as BlueCat, Infoblox, phpIPAM, or SolarWinds. |
| Data protection | Connect CMP to an existing data protection solution, such as Veeam, Cohesity, Rubrik, Azure Backup, or CommVault, to automatically enroll servers in protection plans during provisioning. |