Trials
A trial is a time-bounded evaluation window for a catalog Product — typically a license issued under a trial License Plan or with trial dates on the license. Commercial rules (who may start a trial, duration, conversion) live in Management; Runtime enforces expiry and deny outcomes on validate / activate / refresh.
What Runtime enforces
- Trial end (and related grace if configured on Policy) — fail-closed after expiry.
- Same packaging layers as paid licenses: FeatureLimits, entitlements, optional custom data.
- Modes from Licensing Models still apply (node-locked trial, floating trial seats, offline trial lease windows).
Trials do not weaken signature or JWKS requirements. Clients always verify the signed snapshot.
Trial vs PlatformPlan trial
- Product trial — evaluation of your software under a License Plan.
- Platform evaluation / SaaS trial — access to the Licensing platform itself (Checkout).
Keep naming distinct in Console copy and integrator docs.
Conversion (upgrade path)
- Customer converts to a paid License Plan (or purchases seats).
- Management updates the license binding / entitlements.
- Next Runtime refresh / validate returns the new signed snapshot.
- Client re-verifies JWS and unlocks paid features (Entitlements).
Exact conversion APIs follow shipped OpenAPI — this page does not invent endpoints.
Related
Next steps
- Getting Started
- Metered / usage after trial: Metered usage