Licensing Models
MyHoreca Licensing packages rights as policies and plans on the Management plane, then enforces them on Runtime (and optionally Relay). This page is a short map of the common modes — not a full policy schema.
A license key identifies the license for Runtime calls; it is a credential, not a licensing model.
Common modes
| Mode | Idea | Where to go next |
|---|---|---|
| Node-locked | Rights bound to a device / install identity (fresh install key per machine — not MachineGuid alone) | Activations · Device identity |
| Floating | Shared concurrent seats (checkout, heartbeat, release) | Floating |
| Offline / air-gapped | Enforce with signed leases or handoff when cloud is unavailable | Offline · Air-gapped · Local Relay |
| Trials | Time-bounded evaluation windows | Trials |
| Metered | Usage signals and limits | Metered usage |
Modes can combine (for example a trial that is node-locked, or floating seats with offline lease windows). Exact limits live in the product’s policy/plan.
How to choose (quick)
- Always-online product with fixed machines → start with node-locked.
- Shared pool of concurrent users/seats → floating.
- Sites with poor or no cloud connectivity → offline / air-gapped (and Relay when sync is needed).
- Evaluation before purchase → trials.
- Pay-for-usage or soft caps → metered.
Related packaging
- Catalog: Products · Plans · Policies · Entitlements
- Vocabulary: Core Concepts
- Integrators: API Reference · SDKs
Next steps
- New here? Getting Started
- Human key shape: License Keys
- Deepen offline / floating / relay: Offline · Floating · Local Relay