Deployments and deployment keys

A deployment is a release channel inside an app. New apps start with two, Staging and Production, and you can add more:

aether deployment add MyApp Beta

Each deployment holds its own release history. A common flow is to release to Staging, test on a device, then promote to Production.

Deployment keys

Each deployment has a key. Your app binary carries this key in its native configuration, and the SDK sends it on every update check, which is how the server knows which channel the device follows. Print the keys with:

aether deployment ls MyApp -k

The key identifies a channel, not a secret capability: it can only be used to poll for updates, never to publish them.

When you create a deployment, you can supply the key yourself instead of letting the server generate one:

aether deployment add MyApp Production -k <existing-key>

Pre-defined keys matter when you migrate from CodePush: shipped binaries keep polling with their old key, so reusing that key lets them reach Aether without an app store release.

History and metrics

aether deployment history MyApp Staging
aether deployment ls MyApp

History lists every release in the channel with its label, rollout state, and metadata. Metrics per release count active installs, downloads, and reported successes and failures; the update lifecycle page explains where those reports come from.

The owner can wipe a channel’s history with aether deployment clear MyApp Staging. This removes the release history; it is not a rollback.