minmaxkey

Docs

Docs

MinMaxKey issues license keys for the software you sell and checks them when customers run your app. Start with How it works — the whole loop on one page, two minutes.

  • How it works — the whole mental model, start here.
  • Deploy — one container, Docker / Compose / bare Python.
  • Use it — the dashboard and the CLI, the same actions two ways.
  • Sell with Stripe — buy → key emailed → refund → revoked.
  • Email delivery — Resend in two minutes, Postmark, or classic SMTP.
  • Add it to your app — the code your app embeds (Python, TypeScript, Go).
  • Integration recipes — copy-paste licensing for Electron, VS Code, Tauri, Unity, Godot, Python.
  • License UX patterns — what to show your users when something goes wrong.
  • Offline tokens — what they are and the honest trade-off.
  • Webhooks — server-to-server license events for your backend.
  • API reference — every endpoint, auth model, error codes.
  • Self-hosting — Postgres, proxies, backups, upgrades.

Design principles

  1. One container, two minutes. The pitch is the product. If it needs a second service, we'd rather cut the feature.
  2. Small feature list. Keys, machines, seats, webhooks. Enterprise licensing is a solved problem elsewhere — we're the opposite of that.
  3. Offline by default. Every activation yields a signed token; the server is for enforcement and orchestration, not for every app launch.
  4. Honest security posture. Public keys ship in client binaries; offline revocation is eventual. We document the trade-offs instead of hiding them.

Status

Early but completely functional: the core API, dashboard, CLI, webhooks, Python and Go SDKs are working and tested. Version 1.0.0-rc — the API is stable from here.