Variables and redeploying

An app's Variables page holds its settings and its secrets. Open the app and select Variables. Any member can read the page. Only an owner or admin can change anything.

Setting a variable

Field	Meaning
Name	Letters, digits, and underscores. It can't start with a digit
Value	The value your containers receive
Secret	The platform encrypts the value and never shows it again, not even to an admin. Replace it if you lose it
Share with every application in the organization	Makes the variable organization-wide. A name set on the application overrides an organization-wide name
Deliver as a secret file	Only for a secret. It mounts the value under `/run/secrets` and sets `KEY_FILE` instead of `KEY`. Leave it off unless your container already reads `KEY_FILE`

Setting a name that already exists records a new version. The old version stays for any revision that froze it. The In scope table lists each name with its kind (Config, Secret, or Secret file), scope, version, and update time. It never lists a value.

Turning a plain variable into a secret warns you. Its earlier versions still hold the old value in the clear. Rotate the value at its source, then set it again. You can't save a secret as a plain variable.

Delete removes a name from the next deploy. Running revisions keep the value they built with. Setting the name again brings it back.

A revision freezes its variables

A revision freezes the variables that are current when it deploys. So a change to a variable doesn't reach a revision that already runs.

Redeploy with no new build

When a running revision went out with older variables, the page shows a redeploy box. It lists each stale revision. Select Redeploy with these variables beside one.

The platform makes a new revision that copies the old one: same name, same images, same compose file. It starts as already built, so nothing rebuilds. The platform then makes it active and restarts the services with the saved values.

The same checks as a normal deploy still apply. A revision can refuse for lack of credit, or because your account tier rules it out. The page shows the reason.

The access gate and the pool label use the same redeploy when you save a change to a running application. See Access gate and Pool domain.

Tools for assistants

A Model Context Protocol (MCP) client with an owner or admin token can do the same things:

Tool	What it does
`redeploy_deployment`	Redeploys a running revision on its built image so it picks up the saved variables
`create_deployment` with `sourceSequence`	Makes a new built revision from an earlier one. It becomes active only when you call `set_current_deployment`
`stop_deployment`	Stops the deployment with a given name, as `sc stop` does

stop_deployment takes the organization slug, the application slug, and the deployment name. It tears down the stack, moves the revision back to built, and keeps the images. A zero credit balance never blocks a stop. It fails when the name is unknown, or when nothing runs under that name.