minmaxkey

Docs

Docs

MinMaxKey is a self-hosted licensing & activation server for indie developers. Start with the quickstart — three steps, two minutes.

  • Quickstart — the whole loop, briefly.
  • Deploy — Docker, Compose, bare Python, env vars.
  • Dashboard — the point-and-click way: products, keys, revoke.
  • CLI — the automated way: scripted licenses, webhooks, audit.
  • Concepts — products, policies, licenses, activations, offline tokens.
  • API reference — every endpoint, auth model, error codes.
  • Webhooks — license events, signatures, the payment loop.
  • Offline tokens — what they are, the revocation trade-off, verification.
  • Self-hosting — Postgres, proxies, backups, upgrades.
  • SDKs — Python one-file client, or the Go library + single-binary CLI.

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 functional: the core API, dashboard, CLI, webhooks, Python and Go SDKs are working and tested. Version 0.2 — expect the API to stabilize before 1.0.