LicenseKit
Licensing API

Stop writing the
licensing part again.

Issue keys, count seats, handle refunds, and verify offline with Ed25519 signatures. Wire your store up once and licensing runs itself — including the machine limits and the angry “I bought a new laptop” emails.

No card required · Free tier stays free · Your keys keep working if you leave

POST /v1/licenses/validate
curl https://licensekit.dev/v1/licenses/validate \
  -H "Content-Type: application/json" \
  -d '{
    "key": "ACME-K7QM2-9XTRF-B4HDW-PN3ZC",
    "product_id": "acme-studio",
    "fingerprint": "e3b0c44298fc1c14"
  }'
200 OK
{
  "valid": true,
  "in_grace_period": false,
  "license": {
    "status": "active",
    "expires_at": "2027-04-11T00:00:00Z",
    "max_activations": 3,
    "activations_used": 1
  },
  "product": { "slug": "acme-studio", "name": "Acme Studio" }
}

Sells through

  • Gumroad
  • Lemon Squeezy
  • Paddle
  • Polar
  • Stripe

How it works

Three steps, then it is somebody else's problem.

The whole integration is an afternoon. After that, the only time you open the dashboard is to look someone up.

01

Create a product

One API call, or one form in the dashboard. LicenseKit mints an Ed25519 keypair for it and gives you the public half to embed in your app.

POST /v1/products
{ "name": "Acme Studio", "key_prefix": "ACME" }
02

Point your store at the webhook URL

Paste one URL into Gumroad, Lemon Squeezy, Paddle, Polar or Stripe. Paid orders become licenses, refunds revoke them, and the buyer gets their key by email.

https://licensekit.dev/api/integrations/
  gumroad/tok_8f3a…
03

Check the key in your app

One request on launch. Or verify a signed certificate locally and never call us at all until it expires.

POST /v1/licenses/activate
{ "key": "ACME-…", "fingerprint": machineId() }

The part that matters

Your software does not go down when we do.

Every product gets its own Ed25519 keypair. We sign a license certificate; your app verifies it locally with the public key. No network call, no dependency on our uptime, no dependency on us existing next year.

  • Works on a plane

    The certificate carries its own TTL. Default 30 days, configurable per policy.

  • Works during an outage

    A failed validate call is a retry, not a lockout. Customers never see it.

  • Works if you leave

    Export your licenses and keep signing certificates with the same keypair. We do not hold your product hostage.

Client side, no network
import { verify } from "@licensekit/verify";

// The public key is baked into your binary at build time.
const PUBLIC_KEY = "MCowBQYDK2VwAyEA...";

const result = verify(certificateFromDisk, PUBLIC_KEY);

if (result.valid) {
  unlock(result.claims.license);       // no network call, ever
} else if (result.reason === "certificate_expired") {
  refreshInBackground();               // 30 day TTL by default
}

Everything else

The parts you would have built in month two.

Seats and machine limits

Node-locked or floating. Floating seats free themselves after an idle lease, so a dead laptop stops being a support ticket.

Trials and subscriptions

Perpetual, time-limited, or renewing. Grace periods let a lapsed card keep working while it is retried.

Refunds handled for you

A refund in your store revokes the license and releases its seats. You do not have to notice.

Typo-proof keys

A 30-character alphabet with no I, L, O, U, 0 or 1, plus a checksum, so mistyped keys fail instantly instead of vaguely.

Webhooks out

Signed with HMAC-SHA256 to the Standard Webhooks spec, retried with backoff for nine hours, with a full delivery log.

Activity you can search

Every validation, activation and revoke, with the machine and a hashed IP. Enough to answer a support email in one look.

Build vs buy

You can absolutely build this yourself.

Most people do. Then they discover seat counting has a race condition and refunds were never wired up.

 Rolling your ownLicenseKit
Key generation and storageAn afternoonIncluded
Seat counting without racesA week and a bugIncluded
Offline signature verificationYou will skip itIncluded
Refund and chargeback handlingNever gets builtIncluded
Rate limiting the validate endpointAfter the first abuseIncluded
Delivery retries for webhooksA queue you now runIncluded

Pricing

Priced for one person shipping software.

Flat monthly rate. No per-license fee, no per-seat fee, no percentage of your revenue.

Free

$0/mo

Enough to ship your first paid release.

Starter

$19/mo

For a shipping indie product with real customers.

Pro

$49/mo

For products where licensing is load-bearing.

Business

$99/mo

Unlimited licensing with the paperwork sorted.

FAQ

The obvious questions.

What happens to my customers if LicenseKit disappears?
Nothing immediate, by design. Offline certificates are signed with your product's own keypair and stay valid until their TTL runs out. You can export every license as JSON at any time, and the verification code is a few dozen lines you already have in your app.
Do I have to use your store integration?
No. The integration is one way to create licenses; the API is the other. Plenty of people issue keys from their own checkout and never touch the integrations page.
Can someone brute-force a license key?
A key carries about 93 bits of entropy, the validate endpoint is rate limited per IP and per license, and structurally invalid keys are rejected by checksum before touching the database. The realistic attack on any licensing system is a cracked binary, not a guessed key — which is why the offline path is signed rather than a boolean.
Is there an SDK?
The API is four endpoints and returns plain JSON, so most people paste the snippet from the docs. Copy-paste verification snippets are provided for TypeScript, Python, Go, C# and Swift.
What counts against my license limit?
Licenses that are not revoked. Revoking a refunded customer frees the slot immediately.

Ship the licensing today.

Free for 100 licenses, forever. Long enough to find out whether anyone wants to buy the thing.

Questions? The docs answer most of them.