About Keymint
Licensing infrastructure for teams that ship software.
Keymint exists so developers can sell installed software without rebuilding license keys, hardware activations, floating sessions, and offline verification from scratch.
Why it exists
License enforcement becomes a product unless you contain it.
Most software teams start with a simple key check. Then customers need device resets, activations, expiration dates, trials, floating seats, offline files, support evidence, and API keys with the right permissions.
Keymint packages those licensing primitives into a REST API, native SDKs, and a vendor dashboard so your product code can make clear access decisions without owning the whole licensing system.
Principles
Designed around real licensing decisions.
A small API surface
Licensing should be understandable from the endpoint names: create a key, activate a host, lease a floating seat, sign an offline file.
Device context matters
A license decision is stronger when it can account for a stable hostId, allowed hosts, activation limits, and release flows.
Security claims must be specific
Keymint docs describe scoped API keys, Ed25519 offline JWTs, HMAC-SHA256 floating heartbeats, and hashed license key storage.
Developer surface
The platform stays close to the integration.
The docs center on the primitives developers actually wire into products: activation, floating checkout, heartbeat, checkin, and offline signing.