Licensing portal online

06 / Answers

FAQ.

Short answers for the procurement, security and operations questions that arrive before a license does.

Is Community really free?

Yes. Community includes the core workspace for up to 25 active users with no license file, no time limit and no portal dependency. Paid editions raise the seat limit and unlock private enterprise modules.

Does a license stop mail if it expires?

No. Core mail, sign-in, backups and export continue. Paid capabilities fall back to Community and the seat limit returns to 25 for new activations. Existing users above the limit are not silently deactivated.

Do I need to expose my mail server to the portal?

No. The portal issues a token and a release. Control claims them outbound. The product verifies the token locally; there is no inbound connection from the portal to your mail server.

Can I evaluate Enterprise without a card?

Yes. The 14-day trial uses the Enterprise catalog and does not require a payment method. It is one trial per organization and subject to fair-use limits.

What happens to my data if I cancel?

Your workspace is yours. Cancellation affects the commercial entitlement, not your mailbox data. Core mail and export remain available. The license falls back to Community at the end of the paid period and grace.

Can I use one license on staging and production?

No. Bind each deployment to its own license. A production token on staging makes seat reporting and support ambiguous. Use a trial or a separate staging license.

Do you support purchase orders?

Yes for Enterprise. Request a quote with your company, deployment size, billing contact and PO requirements. The operator can issue a manual invoice and provision the license after payment.

Is the enterprise release available for ARM?

Yes. The release channel publishes signed linux-amd64 and linux-arm64 bundles. The version API accepts ?arch=arm64, and the installer download includes the selected architecture.

How do I rotate the signing key?

Register the new public key under a new kid, deploy it to the signer, keep the old key in the product’s verification ring until its licenses expire or are reissued, then retire the old key. Never retire the key the portal is currently signing with.

Why does the portal ask for a deployment ID?

It ties a subscription, license, seat report and enterprise release to a named estate. That is how support knows which server a renewal belongs to and how usage is attributed.

Still blocked?

Email licensing@alt8mail.com with the organization, deployment ID and the exact state shown in Control. Do not send a license token or private key.