
Licence server for software sellers
Issue signed licence keys, limit activations per machine or domain, verify offline with Ed25519 tokens and ship updates through signed channels. Self-hosted, one Node process, MongoDB.
Seat Board
Keys and policies
Perpetual, subscription, trial and floating policies with entitlements, grace periods and update rights.
Two clients racing for the last seat? Exactly one wins. Dev and staging domains never use a production seat.
Ed25519 tokens bound to product and fingerprint. Rotate keys without breaking installed copies.
Stable, beta and nightly. Short-lived signed downloads that re-check entitlement and never serve a yanked release.
Orders, renewals, cancellations and refunds, signed and idempotent. Out-of-order events wait for their order.
Validations by result, activations over time, versions in the field, renewals and refunds.
LFP-7K2QM-9XH3T-AB4VZ-0RN8C
│ └────────────────── 80 random bits + 4-char checksum, Crockford base32
└── product prefix
stored: SHA-256(pepper ∥ key) + last 5 characters
shown: once, at creation (or in your customer's email)eyJ2IjoxLCJraWQiOiJrMiIsInByZCI6ImZvcm1z…
. signature: Ed25519 over the payload
payload { v, kid, lic, prd, ent[], fp, exp, iat, grace }
checks signature · product · fingerprint · expiry (±5 min skew)Activations with seat limits
Try it: the first production domain takes the seat, the second is refused with a clear code, staging and local domains use a separate dev allowance, and the same site activating twice changes nothing.
Update channels
Upload a zip: it is hashed and signed with the product key. Clients ask /updates, get the newest release they are entitled to, a ten-minute download link and the signature to verify before installing. Yank a bad release and it stops being served, even from a link that is still valid.
stable
2.4.0
beta
2.5.0-beta.2
nightly
2.5.0-nightly
{
"update": true,
"version": "2.4.0",
"channel": "stable",
"sha256": "9c1f4b…e27a",
"signature": "m2Qx…", // verify before installing
"download_url": "/api/v1/download/…", // expires in 10 min
"signature_message": "keyquay-release:v1:forms-pro:2.4.0:9c1f…"
}Point your store at a private endpoint. Orders issue licences once, renewals extend from the right date, refunds release seats, replays do nothing.
Magic-link sign-in. Customers see masked licences, release a seat, download updates and find your renewal link.
Seat Board, validations by result, versions in the field and everything expiring in the next 30 days.
SDK snippets
Each product page generates ready-to-use code with its slug, base URL and current public keys filled in: PHP, WordPress, JavaScript, Python and Dart. They are documentation, tested against tokens this server produces.
Clients must check signature, product, fingerprint and expiry.
$r = keyquay_call('/licenses/activate', [
'product' => 'larkspur-forms-pro',
'key' => $licenseKey,
'fingerprint' => ['domain' => parse_url(home_url(), PHP_URL_HOST)],
]);
// offline check: Ed25519 over the token payload
$ok = sodium_crypto_sign_verify_detached($sig, $payload, $publicKey)
&& $claims['prd'] === 'larkspur-forms-pro' && $claims['exp'] > time() - 300;Three seeded demo licences. Validate one, or activate a fresh domain and watch the seat counter move.
LFP-98J3A-MHJ24-DRCCZ-HZQ1VPlans for vendor workspaces
These are the demo plans a Keyquay operator offers to vendor workspaces. Set your own in the config; billing runs through a simulated gateway until you connect one.
For a solo developer selling one or two products
$19/mo
For small software companies
$49/mo
For vendors with a catalogue and teams
$149/mo
No. Keyquay is honest licensing: signed keys, seat limits, signed offline tokens and signed updates. A determined user can patch any client, so the product makes the honest path easy and the dishonest one tedious, without running code on customer machines.
No. Checkout lives in your store. Your store tells Keyquay about orders, renewals, cancellations and refunds with a signed webhook, and licences follow. A simulated store is included so you can try the whole flow.
Node 20.9+, MongoDB 6+ and one process. Scheduled jobs (lease sweep, expiry, usage rollup, renewal emails) run from cron: the lease sweep every minute is required for floating seats.
Product signing keys and store secrets are sealed with it, so back it up. Rotating a signing key never breaks installed clients: the old public key stays published until its tokens expire.
Activation returns a compact token: base64url payload plus an Ed25519 signature. The client checks the signature with the embedded public key, then the product, the fingerprint and the expiry. Snippets for PHP, WordPress, Node, Python and Dart are generated per product.
Create a workspace, add a product and issue your first key in minutes.