How Clumio fits into your cloud environment
Clumio runs as a hosted service alongside your cloud accounts rather than inside them. You onboard an account or project, and Clumio discovers the resources it contains in the regions you have enabled. Each tenant is associated with a control plane — the regional Clumio service that hosts your portal, your API access, and your configuration. A control plane maps to a set of data-plane regions: the regions where your resources live and where their backups are taken and stored. The control plane you choose therefore determines which regions you can protect, where your backed-up data resides, and which API base URL your clients call. Because protection is driven by configuration rather than installed agents, adding resources to an existing account does not require new infrastructure — Clumio discovers them and applies the protection you have defined.The protection lifecycle
Most work in Clumio follows the same four stages.- Connect. You onboard a cloud account or project and Clumio gains scoped, least-privilege access to it.
- Protect. You decide what to protect and how. A protection group selects resources, either explicitly or by tag, and a policy defines the backup frequency, retention, and storage tier. Rules let a single policy serve several cases.
- Monitor. Clumio records backup tasks and raises alerts. Reports and audit records show what was protected and what changed.
- Restore. You choose a recovery point and a target, and restore the whole resource or a subset of it — to the original account and region, or another one.
Ways to work with Clumio
Developer tools compares these and links to each.
Where to go next
- Core concepts — the vocabulary used throughout this documentation.
- Protection model — how policies, groups, and rules compose.
- Support matrix — which workloads and versions are covered.
- Choose a developer tool — portal, REST API, SDKs, or Terraform.
- Protect an AWS account — a guided first backup and restore.