# Environments and promotion

> Every organisation has production and staging, and admins can add up to 20 more. Each environment has its own network, config and secrets on every server; you promote the exact image digest from one to the next, and can require passkey approvals before changes reach it.

URL: https://unrent.dev/docs/environments/

## Approval floors

An admin can set an environment to need 0, 1 or 2 approvals. Deploys, config changes and rollbacks there then wait until that many approvers approve the job with a passkey. A job nobody approves within 10 minutes expires.

## Promote by digest

On a service, **Promote** shows the image digest that is live, the target environment’s approvals, and which config names differ (values are never shown). Confirming deploys that digest to the same service in the target environment, with the target’s own config. Nothing is rebuilt.

## Run a service on several servers

In the **Placement** tab, add servers: 1 to 10 per service. Deploys, config changes, rollbacks, restarts, stops and starts then roll out one server at a time. After each server, the new release must report running within 150 seconds; any failure halts the rollout and the remaining servers keep their release.

Secrets are sealed to each server. When you add a server, the tab asks for secret values once and seals them to every server.

> A service linked to a database stays on that database’s server.