EYMINT
DocumentationAPI Reference
BlogDashboard
EYMINT
SectionsDocumentationAPI Reference
Go to Dashboard

For AI agents: the documentation index is at /llms.txt. Every docs page is also available as markdown by adding .md to its URL.

Getting Started

  • Keymint Documentation
  • Introduction
  • Getting Started
  • License Keys
  • Changelog

SDK References

  • Software Development Kits (SDKs)
  • Node.js SDK
  • Go SDK
  • Python SDK
  • C# SDK

Integration Guides

  • Integration Guides
  • Customer Portal for Vendors
  • Roles & Permissions
  • Radar Alert Destinations
  • Payment Provider Integrations
  • Stripe Subscription Licensing
  • Import Existing License Keys
  • Email Delivery
  • API Key Management
  • Webhook Deliveries
  • Analytics and Retention
  • Dashboard Workflows
  • Electron Licensing
  • PyQt Licensing
  • Tauri Licensing
  • Next.js SaaS Licensing

Licensing Guides

  • Licensing Concepts
  • Node-Locking & Machine Identifiers
  • Floating Licenses
  • Offline Verification
  • License Radar
  • Public Key Management and Rotation
  • Feature Flags
  • Webhooks & Events

Templates

  • Starter Templates
  • Electron License Starter
  • PyQt License Starter
  • Tauri License Starter
  • Next.js SaaS License Starter

Security & Trust

  • Security & Trust

Support

  • Frequently Asked Questions
  • Customer Portal
  • Using the Customer Portal
  • Workspace Settings and Roles

Legal

  • Privacy Policy
  • Subprocessors
  • Data Processing Agreement
  • Security Overview
  • Terms of Service
  • Service Level Agreement (SLA)
  • GDPR Compliance

Introduction

An overview of the Keymint licensing platform: how license keys, node locking, floating seats, and offline signing work together to secure your software.

Keymint is a developer-first software licensing platform. It manages the entire license lifecycle — from key issuance and customer records to hardware node locking, concurrent seat tracking, and offline cryptographic verification — behind a small REST API and native SDKs.

This page explains how the platform is structured and where to go next. To get your first license activated end-to-end, start with the Getting Started guide instead.

The License Model

Keymint organizes licensing around three concepts:

ConceptPurpose
ProductA software product you sell, identified by a product ID shown in the dashboard. Every license key and activation belongs to exactly one product.
License keyA unique key issued for a product, configured with a seat limit and optional expiration. Customers redeem the key to unlock your software.
ActivationA license bound to a specific machine. Activations are what make licenses enforceable — a key with three seats can be activated on up to three devices at once.

Products are created from the Dashboard, customer records can be managed from the Dashboard or the API, and every downstream operation — activation, checkout, heartbeat, offline signing — is performed with a scoped API key.

Enforcement Primitives

Keymint supports three distinct ways to enforce a license, and you can combine them per product:

  • Node-locked (online) licensing — the most common model. The user's application activates the key with a hardware identifier (hostId), and Keymint verifies the activation on each launch or on a schedule. See License Keys.
  • Floating licenses — a pool of concurrent sessions shared across a team or department, created as floating-type keys. Applications check out a session, then send heartbeats to keep it; sessions are released on check-in or when the lease expires. See Floating Licenses.
  • Offline verification — for air-gapped or high-security environments. Keymint signs a JWT-based license file with an Ed25519 key and an expiry, and your application verifies the signature locally with a bundled public key. Available on every plan, including Free. See Offline Verification.

The API and SDKs

All license operations go through the REST API at https://api.keymint.dev, authenticated with a Bearer API key. Keys are scoped as client (device activation/deactivation and floating sessions), read-only (reads), or admin (key management and offline signing), so a distributed application never needs to hold privileged credentials.

http
POST /key/activate HTTP/1.1
Host: api.keymint.dev
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "productId": "YOUR_PRODUCT_ID",
  "licenseKey": "A8E2K-9F1BC-3D4GH-7J2KM",
  "hostId": "mac-studio-m2"
}

Official client libraries are available for Node.js, Go, Python, and C# / .NET.

Where to Go Next

Getting Started

Configure your account, install an SDK, and run your first activation.

License Keys

How keys are created, activated, node-locked, and signed for offline use.

Floating Licenses

Enforce concurrent seat counts and heartbeat check-ins.

Offline Verification

Verify licenses locally with Ed25519-signed license files.

API Reference

The complete REST specification, error codes, and rate limits.

Integration Guides

Step-by-step guides for Electron, Tauri, PyQt, and Next.js apps.

On this page

  • The License Model
  • Enforcement Primitives
  • The API and SDKs
  • Where to Go Next