Skip to main content

Licensing

Summary​

Platform maintains license validity and capacity independently from plan packaging. Source includes an older client-license record and a richer tenant/client license evaluation model; their long-term consolidation is transitional.

Audience​

  • Platform and customer administrators
  • Implementation, support, development, architecture, and product teams

Purpose​

Licensing communicates whether a tenant/client license is valid and within configured capacity without disclosing private commercial terms or unsupported enforcement assumptions.

Architecture​

License evaluation considers the stored license state, validity dates, an optional grace-period window, administrative suspension, and reported user, storage, and AI usage against configured capacities. It returns an evaluated status and capacity results for callers.

Business concepts​

  • Client license — Implemented / Transitional: provisioning can associate licensed-user and pricing metadata with a platform client.
  • License definition — Implemented: the richer model carries validity, capacity, usage, expiry, grace, and administrative-state information.
  • Grace period — Implemented: a recorded grace window can affect evaluated status after validity ends.
  • Evaluation — Implemented: source calculates an effective license status and capacity outcomes from current records and usage.
  • Usage reports — Implemented: user, storage, and AI consumption can be reported to the licensing boundary.
  • Relationship to plans — Implemented: provisioning and entitlement reconciliation derive some license capacity from subscription snapshots.
  • Relationship to entitlements — Implemented, bounded: license/subscription and tenant status can restrict effective access; a license does not itself define the feature package.
  • Commercial enforcement policy — Requires confirmation: contractual interpretation, notification policy, and organization-wide enforcement behavior require approved product and operational decisions.

Technical implementation​

Licensing endpoints retrieve, maintain, evaluate, suspend, reactivate, and accept usage reports for license records. The evaluator recognizes active, suspended, and expired outcomes and capacity checks. Exact formulas, thresholds, commercial values, and configuration are intentionally not published.

Source References​

  • microservices/src/platform-service/Api/PlatformLicensingEndpoints.cs
  • microservices/src/platform-service/Domain/LicenseEvaluation.cs
  • microservices/src/platform-service/Domain/Entities/License.cs
  • microservices/src/platform-service/Domain/Entities/ClientLicense.cs
  • microservices/src/platform-service/Domain/Entities/GracePeriod.cs
  • microservices/src/platform-service/Domain/Entities/Usage.cs
  • microservices/src/platform-service/Api/PlatformEntitlementEndpoints.cs

See Also​

Keywords​

  • License validity
  • Grace period
  • Capacity evaluation
  • Usage reporting

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-14
  • Review cycle: Quarterly