Skip to main content
Version: Next (unreleased)

License keys

A license key authorizes one AlphaAgent Studio deployment to run. You create a key in the Console, copy its one-time License Token into your deployment, and then monitor that deployment's health and usage from the Console. This page covers creating, monitoring, editing, and revoking license keys.

What a license key is​

Each license key has two parts:

  • A License ID (aalk_…) — a public identifier, safe to share and reference in support requests.
  • A License Token — the License ID combined with a secret, shown to you once at creation. This is the value your deployment uses to activate and to sign its telemetry.

One license key authorizes one deployment. The key is the unit of your relationship with a running Studio: activation, heartbeats, and usage metering all authenticate against it.

Creating a license key​

To create a license key:

  1. Go to License Keys → Create.
  2. Provide a name/description so you can recognize the deployment later.
  3. Confirm. The Console shows the License Token with a copy button.

[Screenshot: License create screen showing the one-time token]

Copy the License Token now and store it securely. The Console treats it as a one-time reveal — copy it before leaving the screen. You hand this token to your deployment (studioctl accepts it interactively or as the LICENSE_TOKEN environment variable); see Deploy Walkthrough.

A newly created key starts as inactive. It becomes active the first time your deployed Studio activates against the Console.

Monitoring a deployment​

Opening a license key shows everything the Console knows about that deployment:

Health and heartbeats​

Once active, your Studio sends a signed heartbeat every few minutes. The Console tracks these and shows a health status:

  • Healthy — heartbeats are arriving on schedule.
  • Warning — one or two recent heartbeats were missed.
  • Unhealthy — several heartbeats in a row were missed.

A heartbeat chart shows the pattern over time, so you can correlate gaps with deployment events. Missed heartbeats reflect connectivity between your Studio and the Console; they do not by themselves disable your license.

[Screenshot: License view with heartbeat health and chart]

Usage charts​

A usage chart shows the model consumption that deployment has reported over a window of time. This is the per-license view of usage; the Billing page aggregates usage across all your keys for invoicing.

Audit trail​

The license view also shows an audit trail of significant events for the key (created, activated, delinquency changes, revoked), useful for support and compliance.

Downloads​

The license view links to available Studio releases so you can download the deployment bundle right where you manage the key. See Downloading Studio.

Editing a license key​

You can edit a key's descriptive details from the license view. The License ID never changes.

Revoking a license key​

Revoking permanently disables a deployment. From the license view, choose Revoke and confirm.

[Screenshot: Revoke confirmation modal]

What happens when you revoke:

  • The key's secret is destroyed, so the deployment can no longer authenticate.
  • On its next heartbeat, the running Studio learns it is revoked and stops serving agent traffic (it enters a disabled state). Operators can still reach diagnostic endpoints to confirm status.
  • The key's record and audit history are retained for reference.

Revocation is permanent and cannot be undone. A revoked License ID can never be reactivated — if you need that deployment back, create a new key and re-deploy. This is different from a billing freeze (see Billing), which is temporary and clears as soon as the overdue invoice is paid.

If a deployment goes quiet​

If a deployment stops sending heartbeats for an extended period (for example, the Console becomes unreachable from your network), the running Studio will eventually disable agent traffic on its own as a safety measure, and resume once connectivity and a valid heartbeat are restored. If you see unexpected Warning/Unhealthy status, check network egress from your deployment and the host clock (large clock drift can cause signed requests to be rejected). See Troubleshooting.