Settings & Keys

Settings & Keys lives in the OTA Updates area of the dashboard, under Configure.

At a glance#

What it does#

Settings holds the account-level controls for OTA: the keys that sign your bundles, the tokens that let you test an unreleased bundle on a device, and your bundle and storage usage.

Signing keys#

Bundles can be signed with an ed25519 key pair so a device will only apply a bundle it can verify came from you. This page lists your public keys — name, public key, when it was created, and whether it has been revoked — and lets you register new ones or revoke a compromised one. Generate a key pair with the CLI (scalebun ota generate-key-pair) and register the public half here; the private half stays with your build pipeline.

Test tokens#

A test token lets an internal build pull a specific unreleased bundle without publishing a real release. You issue a token with a time-to-live (30 minutes up to a full day), hand it to the in-app test panel, and the device switches to the target bundle until the token expires. Revoke a token to cut off access immediately. This is how you validate a bundle on a real device before it reaches any channel.

Usage and quotas#

The usage panel shows your totals — bundles stored, patches generated, total storage in bytes, and releases published this month — so you can see where you stand against your plan before a publish is refused.

Where update policy lives#

Update policy — the target app version, rollout percentage, whether an update is mandatory, and the release note — is set per release when you publish or promote it, not globally here. Install mode (apply immediately, on next restart, or on next resume) is likewise a property of the release. Settings governs the account; the release governs the rollout.

Where the data comes from#

Served by

• Ota

Related#

• Guards & Targeting

• OTA Updates overview