Issue licenses.Validate them anywhere.
The License Server issues RS256-signed JWT license tokens with a configurable time to live, gives you an API key, and exposes a public JWKS endpoint your software calls to validate them. It is the licensing layer for plugins, desktop tools, and any API or app access you need to gate, built into the platform that already handles the selling.
RS256 JWT license tokens with a TTL
Each license is issued as an RS256-signed JWT with claims like jti, sub (the user), product and instance ids, and an exp expiry, carrying a configurable time to live that defaults to one hour.
Because the token is signed and self-describing, your software can read what it permits and when it expires without a round trip for every check, then call renew when the TTL is up.
That gives you real expiry control over who can run your software, tied to the access they actually paid for.
An API key, validation endpoints and public JWKS
An encrypted API key authenticates the clients and integrations that talk to your licensing, and a set of endpoints handles the lifecycle: validate to check a token, bind to tie a license to a device or instance, renew to refresh it when the TTL is up, and heartbeat to keep a live session honest.
For stateless checks, a public JWKS endpoint publishes your signing keys, so any service can verify a license token's signature without holding a shared secret.
It is the standard way modern systems validate tokens, which means your software, your plugin, or a third party integrating with you all check licenses the same trusted way.
License software, plugins and API access
Use it to license a desktop application, a plugin or extension, an SDK, or any API or app access you want to put behind a paid subscription.
Because licensing lives on the same platform that sells subscriptions, access stays in step with payment. An active subscription means a valid license, and a lapsed one means the token stops renewing.
You get a clean separation: the platform handles who paid, the License Server handles whether the software runs.
What the License Server does
The pieces of a real licensing system, built in.
RS256 JWT tokens
Issue RS256-signed JWT licenses with a configurable TTL, so access expires when it should.
Encrypted API key
An encrypted API key authenticates the clients and integrations that call your licensing.
JWKS and endpoints
A public JWKS plus validate, bind, renew and heartbeat endpoints cover the full lifecycle.
Software and plugins
License desktop apps, plugins, extensions and SDKs from one place.
Tied to subscriptions
Licenses follow the subscription, so an active plan means a valid token.
Gated API access
Put any API or app access behind a license your callers must validate.
License Server questions
How tokens, keys and validation fit together.
Add a licensing layer to your software
Issue RS256 JWT licenses with a TTL, authenticate calls with an API key, and validate against a public JWKS endpoint, all tied to your subscriptions. See the plans, or book a call and we will walk through your licensing setup.