Licensing and serial keys

Turn licensing on in the product form and set its policy. The key is issued from the policy as it was when the order was placed, so editing the product later never changes what you already sold.

Validity

Perpetual, a number of days after purchase, or a fixed date.

Activation limit

How many machines, domains or people may use one key at once.

Binding

What an activation is tied to: a machine, a domain, a named person, or a seat in a floating pool.

Entitlements

Feature names signed into the validation answer, so one build can unlock Basic or Pro.

Offline grace

How long your software may run without reaching Sellstamp.

Your software calls the activation and validation endpoints with the key. On plans that include it, the answer is signed with Ed25519, and a verifier in your language checks it against a public key you embed at build time. For a product with licensing on, the dashboard generates an integration guide from that product’s own policy. Machines with no internet access activate with a request file and a response file.

If you already have keys, from a publisher or another system, import them into a pool under Products → Serial pools and attach the pool to a product. Each sale hands out the next unused key.

• A customer can release one of their own devices from their order page, if you leave that on.
• On a key bound to people, the buyer adds and removes colleagues by email themselves.
• Seat increases and tier upgrades change the existing key rather than issuing a second one. An upgrade is an ordinary order.
• Revealing a key or resetting its activations in the dashboard asks you to confirm your identity again.