# Understand a deployment from creation to retirement

Canonical: https://savrn.com/cloud/deployments

SAVRN Cloud · Coming soon. Public documentation and a browser simulation are available; connected services are not yet available.

A deployment is the execution resource behind a workload, with a configuration and a lifecycle that need to be visible. SAVRN Cloud’s preview lets operators explore those states using local records. A ready label in the demonstration describes a simulated state. Connected deployment control is Coming soon.


## Inspect the concrete configuration

Open a sample deployment to review its model, provider, region, resource choice and recorded ceiling. Configuration and logs provide different views of the same object. The planned connected record would also identify exact artifacts and runtime revisions, allowing a team to determine what is actually serving a project instead of relying on a reusable display name.

## Distinguish draining from deletion

Draining requests changes admission while an allocation remains present. Restarting represents a different lifecycle action. Deleting a local allocation requires its exact name and retains the record for inspection. These preview distinctions model an operational concern: stopping new work does not necessarily terminate the underlying resources or end every associated charge.

## Use health and usage as separate evidence

The console includes a demo health check, sample metering and manifest export. Each is labeled as a local simulation. In a connected service, a health observation would need a timestamp and a defined test; usage would need its own measurement and reconciliation. A successful check cannot substitute for evidence that the intended model revision processed a real request.

## Make changes recoverable

The planned lifecycle should connect an operator’s requested change to observed execution and a recorded result. A release needs a clear rollback target, and retirement needs confirmation that relevant resources have stopped. Candidate promotion in the preview demonstrates how a reviewed artifact can become associated with a deployment while preserving a separate record of the approval decision.

## What you can explore today

Create, drain, restart and delete synthetic deployments; inspect their local configuration, logs and sample usage.

## Before this service launches

Real lifecycle operations require provider reconciliation, observed runtime state, access controls and tested recovery procedures.

## The customer outcome

The intended outcome is a deployment history that helps operators explain configuration, availability, change decisions and resource retirement.

## Related documentation

- [Deployment lifecycle](https://savrn.com/cloud/docs/inference-deployments)
- [Storage, networking and cleanup](https://savrn.com/cloud/docs/compute-storage-network-cleanup)
- [Promote, deploy and roll back](https://savrn.com/cloud/docs/lab-promote-deploy-rollback)
- [Inspect deployments](https://savrn.com/cloud/console/#/deployments): Explore the lifecycle of a sample allocation.