Licensing infrastructure that stays out of the way

License your software.Keep control.

Entyra connects identities, keys, devices, sessions, and entitlements in one control plane. Your customer relationships stay yours.

Start building See the integration

No global end user accounts. No credit card to start.

app.entyra.dev

Live request

Authorization trace

Allowed in 14 ms

POST /v1/authorizereq_01K4F

Identity resolved
idn_01K2P8
4 ms
License active
lic_01K2Q1
8 ms
Device trusted
Windows x64
11 ms
Policy allowed
product.access
14 ms

Decision

{
  "allowed": true,
  "identity": "idn_01K2P8",
  "entitlements": {
    "product.access": true,
    "device_slots": 3
  },
  "expires_in": 3600
}

Identity realm: primaryEnvironment: productionPolicy: default_access

Flexible licensing

Keys, trials, subscriptions, device limits, and perpetual access use the same model.

Isolated identity realms

Every developer owns a separate identity boundary for each customer ecosystem.

Authorization in one call

Resolve session, license state, entitlements, and policy without stitching services together.

Every decision explained

Request logs, audit events, and webhook delivery trails stay attached to the real action.

One authentication pipeline

Every way in reaches the same source of truth.

License-only software and full customer accounts should not require separate systems. Entyra resolves both through the same session, entitlement, and policy model.

01
Credential
Key, password, OAuth, or external identity
02
Identity
A durable principal inside one isolated realm
03
Session
Product, environment, device, and license context
04
Decision
Entitlements and policy resolve to a clear result

Tenant isolation

We authenticate developers. You own everyone else.

Customer identities belong to your organization and your realms. The same email can exist in two products without creating an accidental connection between them.

No shared identity graph across developers
Development and production stay separated
Organization roles live in Entyra, not Clerk
Soft deletion and audit history preserve context

A small integration. A complete control plane.

Start with one authentication call. Add customer accounts, device binding, usage limits, and offline verification when the product needs them.

Create a development workspace

main.cppproduction ready

auto session = client.auth().license(key);

if (!session) {
  show_error(session.error());
  return;
}

if (session->has("product.access")) {
  launch();
}

SDKs

C++, C#, Rust, Python

Response

One session model

Runtime

Online or hybrid

Development starts here

Build the access layer your product will not outgrow.

Start building