Skip to content
LicentiaEU Software licensing control plane
Log in Start for free

Product journey

How it works

From product configuration to a verified result, each part of licensing has one clear responsibility.

A license moves through six deliberate steps

You configure a product and define license facts and entitlements. LicentiaEU then produces a signed artifact for delivery to your software or end user.

A supported verifier checks that artifact and reports trusted facts. Your application interprets those facts and decides what happens next.

  1. 01

    Configure product

    Set its identity, tier, and verification model.

  2. 02

    Define license

    Add the facts, bindings, validity, and entitlements the license should carry.

  3. 03

    Issue signed artifact

    Review the draft and issue an immutable signed license.

  4. 04

    Deliver artifact

    Provide the license to the customer’s software or end user.

  5. 05

    Verify

    Validate structure, canonical representation, signature, and relevant facts.

  6. 06

    Interpret verified facts

    Apply access, feature, grace, and user-experience policy in your application.

Responsibilities

Issuance, verification, and enforcement are different

Issuance

Turns reviewed license data into a signed artifact and records the operation.

Verification

Proves artifact integrity and returns facts and diagnostics; it does not define every product decision.

Enforcement

Lives in your software, where verified facts become access rules and user-facing behavior.

Request and response models

Choose where verification results go

Model availability depends on the selected tier. The panels reflect the models configured by the Control Plane; dedicated artwork for Models II–IV is still pending.

Model I

Direct Online Verification

Client sends request (incl. License) to LicentiaEU Verifier. Response returns to client.

  • Issuer → Client: License (XML)
  • Client → LicentiaEU Verifier: Request incl. License
  • LicentiaEU Verifier → Client: Response (JSON/XML)
Model II

Direct Response + Info to Organisation Server

Client receives response directly. LicentiaEU Verifier also forwards response to Org Cloud Server.

  • Issuer → Client: License (XML)
  • Client → LicentiaEU Verifier: Request incl. License
  • LicentiaEU Verifier → Client: Response (JSON/XML)
  • LicentiaEU Verifier → Cloud Server (Org): Response (JSON/XML)
Model III

Response to Organisation Server (conceptual routing)

Conceptually, verification response is routed via Org Cloud Server. For LicentiaEU this is technically the same as Model I.

  • Issuer → Client: License (XML)
  • Client → LicentiaEU Verifier: Request incl. License
  • LicentiaEU Verifier → Cloud Server (Org): Response (JSON/XML)
  • Cloud Server (Org) → Client: Response
Model IV

Org Server Entitlement (Client collects entitlement from Org Server)

Client verifies via LicentiaEU but uses Org Cloud Server as entitlement decision point.

  • Issuer → Client: License (XML)
  • Client → LicentiaEU Verifier: Request incl. License
  • LicentiaEU Verifier → Cloud Server (Org): Response (JSON/XML)
  • Client → Cloud Server (Org): Entitlement Request
  • Cloud Server (Org) → Client: Entitlement Response

Technical details

Signed and deterministic

Canonical XML and Ed25519 signatures allow compatible verifiers to reproduce the same integrity checks. Signed workflows and audit records make issuance and verification activity easier to diagnose.

Input
License artifact
Checks
Schema, canonical form, signature
Output
Verified facts and diagnostics

Ready to issue your first license?

Create an account and configure your product.

Start for free