Features
Everything licensing needs, and nothing you have to run.
Licento handles the keys, the limits, the signatures, the downloads and the deliveries. You decide the rules.
Licences
Keys, seats and the rules behind them
Each product has plans, and each plan says how long a licence lasts, how many installations it allows, and what it unlocks. A licence is issued against a plan; the rules come with it.
- Readable keys with a prefix of your choosing, like ACME-7Q2K9-…
- Installation limits, counted per site or per machine — staging and development copies are kept out of the count, within a limit
- Suspend, revoke, renew or replace a key — every change is recorded
- Customers free a seat themselves to move to a new site
Signed answers
Answers your software can check for itself
Every activation, check and update answer is signed with Ed25519. Your software holds only the public key: it can tell a genuine answer from a forged one, and it never holds anything that could forge one.
- A signed grace period, so an installation keeps working through an outage for as long as your plan allows — and not longer
- Signing keys can be rotated: every answer names the key that signed it
- An answer that denies an entitlement is signed too, so “no” cannot be edited into “yes”
Updates
Releases that only licensed installations receive
Upload a build once. Installations with a valid licence are told a new version exists and download it over a link that expires; an installation without one is told nothing.
- Stored on your own server — no cloud storage account needed
- The SHA-256 digest of every file is signed, so your software can check a download before it installs it
- Pull a release that turns out to be broken, without deleting its history
- Storage limits per organization, and for the whole server, enforced as uploads arrive
Customer portal
Somewhere your customers can help themselves
Each organization gets a portal at its own address. A customer asks for a sign-in link, follows it, and sees their licences, where each one is installed and what it includes.
- No passwords for your customers to forget — a link that works once
- Free a seat without writing to you
- Your support address, where they will look for it
Payments
Sell directly, with delivery that does not give up
Connect your own payment account and sell from a checkout link. When the provider confirms a payment, the licence is issued and its key is emailed to the customer.
- Razorpay and Stripe Connect; the money goes to your account, not through ours
- A licence is issued once per payment, however many times the provider repeats itself
- If the email fails, it is retried — and you can send it again, or to a corrected address, from the licence
- Card details are handled by the provider and never reach this service
For developers
An API for your store, and webhooks for everything else
Issue and manage licences from your own store or back office with scoped API credentials, and hear about what happens through webhooks.
- Idempotency keys: a request retried after a timeout returns the first answer instead of issuing a second licence
- Credentials limited to the operations you choose
- Webhooks signed with HMAC-SHA-256, retried with back-off, and refused for private network addresses
- A versioned licensing API that installed copies of your software can rely on
Your team
Roles, two-factor sign-in and a record of every change
Invite your team with the role each needs. Require two-factor authentication for the roles that can do the most, and look back at who did what in the audit trail.
- Owner, admin, developer and support roles
- The password is asked for again before anything that cannot be undone
- An audit trail of licences, keys, settings and sign-ins