SoftActivate Licensing Server
SoftActivate Licensing Server is the self-hosted deployment of SoftActivate Licensing. It runs the same licensing service on your own infrastructure: the same activation protocol, the same client SDK, and the same management console. Every certificate and key stays in your custody, with no dependency on anyone's cloud.
What's in the box
One container image carries everything: the licensing services, the management console, a TLS-terminating web server, a job scheduler, and an embedded database (with an external-database escape hatch for teams with their own database estate). A small setup generator asks a dozen questions and emits a complete install kit. You run one command and log in.
What you'll need
- A container host (Docker or Podman) with about 4 GB of memory for the appliance, on x86-64 or arm64.
- A hostname your products will reach, and a TLS answer: bring your own certificate, let the server obtain one automatically, or use an internal CA (configuration).
- About ten minutes. The reference install, from nothing to an activated license, is quick (install).
Constraints
- You custody the keys. The certificate hierarchy that signs your licenses lives on your server, protected by a passphrase you set. Its backup is your responsibility; a database dump alone is not a backup.
- Payments and air-gap don't mix. Selling through your own Stripe or PayPal account (payments) requires reachability from the payment processors, so a fully air-gapped deployment forgoes payments.
Start here
- Install: the generator, the install kit, first boot.
- First admin and sign-in: the built-in console login, or bring your own identity provider.
- Certificates and keys: the local PKI and your products' trusted root.
- Differences from the cloud: a one-page orientation for readers of the SoftActivate Licensing docs.