Licensing portal online

02 / Install

Install the enterprise release.

A valid license unlocks entitlements. The signed enterprise release supplies the private modules that implement them. Both are required.

A license is not a binary.

A Community binary with a valid Enterprise token reports binaryEdition: community and leaves paid features unavailable. Control offers Install enterprise release when the license is valid but the binary is not.

The release contract

ArtifactPurpose
alt8mail-enterprise-<version>-linux-amd64.tar.gzSigned x86-64 enterprise release archive.
alt8mail-enterprise-<version>-linux-arm64.tar.gzSigned ARM64 enterprise release archive.
.sha256SHA-256 digest checked before extraction.
.sigDetached Ed25519 signature over a8m-enterprise-release-sha256:<hex>.
enterprise-release-public.keyRelease verification key. It is separate from the license-signing key.

Guided install

  1. 01
    Upload or claim a valid license.

    Control must have an active or grace token. The install endpoint will not widen or reissue that token.

  2. 02
    Authorize the bundle.

    Control sends the license token and deployment ID to the portal. The portal checks the signature, record status and expiry, then returns a one-time, deployment-bound bundle claim.

  3. 03
    Verify before unpacking.

    Control checks the SHA-256 and the detached release signature, extracts into a staging directory and refuses unsafe paths.

  4. 04
    Switch and restart.

    The current release is copied, the enterprise binaries overlay it, and /opt/a8m/current switches only after the staging checks pass. A failed step leaves the running release untouched.

Rollback

The previous release stays on disk. If the new release fails its health checks, point /opt/a8m/current back to the prior release and restart the webmail, admin and Control services. Keep the signed token; a rollback does not require a reissue.

Air-gapped install

Download the enterprise archive and its sidecars from the portal account, transfer them to the host, verify the checksum and signature with the published public key, and use the same Control install action. The portal is not required at install time once the artifacts and token are on the host.

Operational checks

  • Control reports the enterprise binary edition and current version.
  • The license snapshot shows the expected plan and feature keys.
  • Seat metering reflects real active users.
  • Core mail, sign-in and export still work with the portal unreachable.