03 / Operate
Deployments and usage.
A deployment is the named Alt8Mail estate that a subscription and license attach to. It is how support, seats, renewals and release channels stay pointed at the right server.
Where to find the deployment ID
In Alt8Mail Control, open Infrastructure → License. Control creates and stores a deployment ID; copy it into the portal when adding a deployment or starting a guided purchase. The ID is stable across releases and license renewals.
Add a deployment
- 01Open Account → Deployments.
Add a name, environment, hostname and region for your own operations.
- 02Paste the Control deployment ID.
The portal binds the deployment to your organization and, when you reissue, to the signed license.
- 03Watch the first heartbeat.
A deployment becomes connected when the product reports usage. No heartbeat is required for core mail or for the license to work.
Usage token
Each deployment has a one-time usage token. Treat it like a password: it authenticates the heartbeat and can be rotated if exposed. The raw token is shown once; the portal stores only its hash.
ALT8MAIL_LICENSE_USAGE_URL=https://licenses.example.com/api/v1/usage
ALT8MAIL_LICENSE_USAGE_TOKEN=a8mu_...
ALT8MAIL_LICENSE_USAGE_INTERVAL_HOURS=24
The heartbeat sends the license ID, deployment ID, product version, active seats, licensed seats, storage/domain/mailbox/API counts and enabled-feature counts. It never sends mail, contacts, subjects or content.
Seat reporting
| Value | Meaning |
|---|---|
| Active seats | Active, non-deleted users excluding platform system administrators. |
| Licensed seats | The signed seat claim on the active license. |
| Utilization | Active divided by licensed. A warning appears at 80% and 100%. |
| Overage | Active seats above the license claim. Existing users stay active; new activations are refused until usage falls below the limit. |
Multiple deployments
A production estate may have separate production, staging and disaster-recovery deployments. Give each one its own deployment ID and license. Do not reuse a production token on staging: the deployment claim is there to keep support and seat reporting honest.
A customer with root access can always edit a local system. Binding keeps honest deployments attributed and gives support a reliable identifier; it is not a cryptographic lock on the host.