Skip to content
Kleis
Dark theme
Contact us
Feature tour

What Kleis does, and exactly how.

Everything on this page is built and tested in the current release. Where a capability has a limit you should know before you rely on it, the limit is written next to it.

Licenses and keys

Licenses, plans, and keys.

A product has plans; a plan decides what a license grants. You issue a license under a plan and hand its key to your customer.

Four kinds of license

Each plan states its kind and when its duration starts.

  • Perpetual: no commercial expiration. Its offline lease still expires and renews.
  • Subscription: a renewable period.
  • Trial: a duration, from issuance or from the first activation.
  • Fixed date: valid until a date you set.

Keys shown once

A key holds 128 or 256 random bits, in groups that are easy to read and type. The server keeps only a keyed hash for lookup and a short hint, so nobody, including an administrator, can read a key back.

  • Look-alike characters are interchangeable when typing, and a checksum catches mistakes before any request is made.
  • The full key never appears in a log, an audit entry, or a metric.

Policies that inherit

Key length and the maximum offline period are policies. A value is resolved from the system's allowed choices, the tenant's default, the product, the plan, and an authorized override on one license.

  • A change applies to keys generated and leases issued afterwards. Nothing already issued changes.
  • Every change is audited and kept as an immutable revision.

Device-bound, named-user, or floating

A plan sets how many devices a license may activate, can require a named user, and can make its seats floating.

Offline

Offline leases and air-gapped devices.

The device's authority is a lease: a small signed document from the server. Only a lease the client verified grants anything.

Offline leaseOfflineValid
Signed by
lease-2027-01 (Ed25519)
Trusted through
manifest 7, root root-2027
Bound to
this device's public key
Issued
2027-03-14 09:20 UTC
Offline period
14 days
Expires
2027-03-28 09:20 UTC
Day 5 of 14 without a connection9 days left
Sample data.

7 to 28 days without a connection

You choose the offline period: 7, 14, 21, or 28 days. The period runs from the time the server signed the lease, and that time is part of what is signed.

  • Restarting the application, copying its files, or rereading them changes nothing.
  • An application can ask for a shorter period than the server grants, never a longer one.

Air-gapped activation by file

A device that never connects writes a request file. Someone exchanges it for a response file on a connected machine, in the console or with a small helper program, and the device imports the response.

  • The license key is typed where the exchange happens and is in neither file.
  • Renewal and deactivation work the same way.
  • A response is usable once, on the device that asked, and a request is answered once.

Time the device cannot bend

The client anchors time to the server, measures elapsed time monotonically while it runs, and keeps a protected high-water mark. A clock set back beyond the tolerance asks for an online validation.

  • Recovering from a clock anomaly never extends an expiration.

Outages do not stop a product

If the server cannot be reached, the device keeps working on the lease it holds until that lease expires. A failure is never treated as a successful check, and it adds no extra time.

Good to knowA longer offline period also means a longer possible delay before a revocation or an entitlement reduction reaches a device that stays disconnected. A device that never connects learns of a revocation only at its next renewal by file.
Entitlements and usage

Entitlements, feature flags, and metered usage.

An entitlement is something a license grants: a feature, a number, a set of capabilities, or a quota. Plans set the defaults; a license can differ.

Entitlements of a licenseRevision 14
  • export.pdfFeatureOn
  • projects.maxLimit50
  • render.engineCapabilitystandard, gpu
  • cloud.syncFeature, online onlyOn
  • beta.timelineFeature, until 2027-06-30On
usage.reportCredits this period640 of 1,000
Offline budget in this device's lease25
Sample data.

Features, limits, and capabilities

Switch a feature on or off, set a numeric limit, or grant one or more values of an enumerated capability. Each grant can carry its own expiration.

  • Online-only entitlements are honored only shortly after the server last confirmed the license.
  • Maintenance and version eligibility are carried in the lease, so a build can refuse a version the license does not cover.

Changes that reach devices

Change an entitlement in the console or through the API. The server sends connected devices a hint, and each fetches a newly signed lease.

  • The hint itself grants nothing: only the verified lease does.
  • Offline devices keep their last verified state and reconcile when they reconnect.

Metered usage

Reserve units of a metered entitlement before the work and report what was used after it. Reservations are atomic on the server under concurrent requests, and submissions are idempotent.

  • Periods, resets, and units are defined per meter.

Offline budgets

A lease can set aside a budget of units for its device to use offline. The budget is taken out of the license's balance when the lease is issued, so budgets never add up to more than the balance.

  • On reconnecting, the device reports what it used and receives a new budget.
Good to knowA counter kept on a device cannot enforce an exact limit against a person who controls that device. Strict limits are enforced online or through budgets reserved in advance.
Seats and revocation

Seats, suspension, and revocation.

Seat limits hold under concurrent activations, and every state change of a license reaches the devices that hold it.

Floating seats

A floating license shares its seats among devices through short server leases. A seat that is not renewed frees itself.

Offline checkout

A device can check a floating seat out for a stretch offline. The seat stays reserved for the whole grant, so it cannot be handed to someone else while the first device can still use it.

Suspension and revocation

Suspend, reactivate, renew, or revoke a license. Each change raises the license's authority revision, is audited, and is announced to connected devices by a signed status notice.

  • A disconnected device stops when it reconnects, or when its lease ends, whichever comes first.

Releasing a device

A device deactivates itself to free its seat. An administrator can release a device that is gone, and a plan can let customers release their own.

  • A forced release is audited, and the console shows how long the released device may keep working on the lease it holds.
Customers and governance

Customers, roles, audit, and export.

Kleis is multi-tenant: each vendor works in its own tenant, with its own team, customers, and records.

Customers and a customer portal

Keep a record per customer with your own reference. Give a customer a sign-in that shows only their licenses and activations, lets them release their own devices where the plan allows, and exchange files for an air-gapped device.

  • A customer sign-in never sees a license key or another customer.

Five roles and multi-factor sign-in

Owner, Administrator, LicenseManager, Support, and ReadOnly. Every role above ReadOnly signs in with an authenticator app. The permission is checked again by every operation, not only by the navigation.

Audit log

Every administrative action is recorded in the same transaction as the change: who, what, when, and on which record. Entries name a key by its hint, never the key.

Export

Download your tenant's data as one JSON document, optionally limited to a date range. The same export is available through the API, in pages.

Integrations

Administration API, credentials, and webhooks.

Your back end can do everything the console does for licensing: define the catalog, issue and change licenses, read activations and usage, and manage its own credentials.

DeliveriesSecret version 2
EventStatusAttemptsAnswer
license.issuedDelivered1200
activation.createdDelivered1204
entitlement.changedPending2503
license.revokedDelivered1200
Sample data.

Administration API

A JSON API under /v1/admin with an OpenAPI description. A service credential fixes the tenant and the role; nothing in a request can select another tenant.

  • Lists page by keyset: no row is returned twice while the list changes.
  • Errors are structured and name the parameter that was wrong.

Idempotent creation

Send an Idempotency-Key with a request that creates something. A retry after a timeout returns the first answer instead of issuing a second license.

Service credentials

Create and revoke credentials in the console or through the API. Each carries one role, never higher than its creator's, and its secret is shown once.

Signed webhooks

Register HTTPS endpoints for the events of your tenant. Each delivery is signed with HMAC-SHA-256 over its identifier, timestamp, and body, retried with increasing delays, and listed with its status.

  • Rotate an endpoint's secret without losing an event: each delivery names the secret version that signed it.
  • Kleis refuses to deliver to an address inside its own network.
SDKs

Client SDKs for .NET and for native code.

The clients verify leases with the same rules and the same test fixtures, so a lease means the same thing in every language.

C# client

For desktop, command-line, and worker applications on .NET 10. It activates, keeps the lease current in a background loop, and answers entitlement checks from memory with no I/O.

  • Tested on Windows, Linux, and macOS. State is protected with DPAPI on Windows and the Secret Service on Linux, with an owner-only key file as the fallback.

ASP.NET Core

Registration from configuration, validation of options at startup, a health check, and authorization policies that require an entitlement on an endpoint.

Native C and C++

A C++20 static library behind a C header, built with CMake and vcpkg. It activates, validates, meters usage, and handles air-gapped files.

  • It has no push channel: it learns of a change at its next heartbeat or validation.

Hardware-backed device keys on Windows

By default the device key is a software key. On Windows a host can ask for a non-exportable key in the platform crypto provider, which keeps it in the TPM, and the client reports which protection is in use.

  • Where no TPM is available the client falls back to a software key.
Good to knowA software device key can be copied together with the client's state by the device's own user. The server still counts that as one activation and one seat.
Operations

Self-hosting, signing keys, and observability.

Kleis is three services on PostgreSQL: the API devices talk to, a worker for events and webhooks, and the console.

Self-hosting

Docker Compose files for a local stack and for production, with separate database roles for migration, the API, the console, and system administration. Runbooks cover backup and restore, secrets, and recovery.

Vault-backed signing

Leases can be signed through HashiCorp Vault Transit, so the private key never reaches the host process. Root keys sign the trust manifest offline with a command-line tool, and the manifest is imported.

  • Signing keys rotate through the manifest; a compromised key is revoked there.

Observability

The services export metrics, traces, and logs over OpenTelemetry. A Collector feeds Prometheus, and Grafana dashboards and alert rules ship with the deployment files.

  • Metric labels are bounded: no key, tenant, license, or device identifier is ever a label.

Tenant isolation

The tenant of a request comes from the verified sign-in or credential, never from a parameter. PostgreSQL row-level security enforces it under a database role that cannot bypass it.

See it from the device's side.

The life of a license, online and offline, step by step.

The connection to the console was lost. Reconnecting…

The connection could not be restored. Nothing you had not saved was sent.

Reload the page