LicenseKit Docs

LicenseKit helps software and digital-IP teams turn commercial events into enforceable product access.

Bring your IP, connect the systems where you sell it, then use LicenseKit to issue licenses, enforce runtime access, and produce customer/order-linked compliance evidence.

What You Can Do Here

• get to first successful license validation
• choose a licensing model for your product, plugin, model, data set, firmware unlock, or on-prem deployment
• connect Stripe, HubSpot, Pipedrive, Zoho CRM, or a custom API workflow
• keep customer, order, subscription, license, device, seat, and feature context linked
• implement runtime activation, validation, metering, offline issuance, and floating leases
• use reporting and exports for customer visibility, compliance, support, renewals, and settlement evidence
• confirm scopes, envelopes, signatures, and machine-readable reference assets

Browse By Section

• Start Here
• Licensing Models
• SDKs
• Runtime Integration
• Reporting
• CRM And Commerce Integrations
• Integration And Automation
• Deployment
• Operations
• Reference

Product Shape

LicenseKit is not a CRM, storefront, or billing engine. Stripe, HubSpot, Pipedrive, Zoho CRM, or your own system can stay the commercial source of truth.

LicenseKit owns the post-sale access layer:

• products and policies
• customers, orders, and subscriptions as linked external facts
• licenses, seats, devices, features, versions, and usage
• signed runtime responses
• audit trails, activity feeds, reports, and frozen exports

Machine-Readable Assets

These stay outside /docs on purpose:

• /openapi.yaml
• /llms.txt
• /llms-full.txt
• /scope-to-operation.json
• /error-codes.json
• /report-kinds.json
• /sdk-matrix.json

Current Posture

The current backend posture is suitable for active development and live trial usage. Do not describe it as broadly production-proven at scale without new evidence.