Licensing portal online

Security and trust

Licensing with a
visible trust boundary.

The portal is a commercial system, not a second copy of your mail server. It stores the minimum needed to sell, issue and support a license — and tells you exactly where the product does not depend on it.

CORE MAIL Never gated

Mail delivery, sign-in, backups and export do not require the portal or a network call.

The boundary

Offline by design.
Explicit by policy.

A license is a signed entitlement document, not a remote switch. The safest design is to make that obvious to your security reviewers.

01

Signed offline token

The product verifies an Ed25519 signature locally with a compiled-in public key. A token contains the license ID, plan, seats, features, deployment, issue and expiry dates.

02

No mail content

The portal stores organization, contact, deployment, subscription, license and usage-count data. It does not need mail, contacts, subjects, attachments or mailbox contents.

03

Grace before fallback

Paid licenses can carry a grace period. After expiry, paid capabilities fall back to Community while core mail continues. Existing users are not silently removed.

04

HSM-ready signing

The portal signs through a file, command or isolated HTTP signer. Production is designed for KMS/HSM custody; the private key never belongs in the product or a release bundle.

05

Signed releases

Enterprise archives publish a SHA-256 checksum and a detached signature from the release key. Control verifies both before installing and keeps the prior release for rollback.

06

Honest revocation

A portal-side revocation blocks future downloads and publishes the license ID to an Ed25519-signed list. An already-installed offline token remains valid until its signed expiry unless a revocation-aware release verifies that list. We do not pretend otherwise.

Data map

What the portal knows.

Enough to operate the commercial relationship. Nothing that makes it a shadow mail archive.

StoredPurpose
Organization and contact detailsLicensing, support and billing
Deployment ID and usage countsSeat attribution, overage and support
Subscription, invoice and tax identifiersPayment and renewal
License claims and audit eventsIssuance, reissue, revocation and support
Not storedMail, contacts, subjects, bodies, attachments or mailbox contents

For your review

Questions we expect.

Can the portal disable our mail server?

No. Core mail, sign-in, backups and export do not call the portal. An expired or invalid license falls back to Community paid capabilities; it does not stop mail delivery.

Where does usage telemetry come from?

The product heartbeat is opt-in. It sends a license ID, deployment ID, version, active seat count, licensed seat count and enabled-feature counts. It never sends mail, contacts, subjects or content.

How is the signing key protected?

Production can use an isolated signing service backed by KMS/HSM or a vendor command. The portal receives signatures, not key material. Development file keys are never used for customer licenses.

Can we use an air-gapped deployment?

Yes. Download the signed token and enterprise release from the portal, transfer them to the deployment and use Control to install. Usage reporting remains optional.

What about tax and invoices?

Stripe handles self-service payments and can handle tax IDs and invoices. Enterprise procurement can be quoted with a purchase order and manual invoice route.

Need a security pack?

Ask for the boundary,
not a badge.

We can provide the data map, subprocessor list, signing and release model, and deployment guidance for your review. We do not claim certifications we do not hold.