Licensing Overview
Every Atrium deployment — SaaS or self-hosted — operates under a license that determines which features are available and at what capacity. Licenses are managed by the Control Plane and enforced locally by the application.
SKU tiers
Licenses are organized by deployment mode and tier:
| SKU | Deployment | Description |
|---|---|---|
| saas-starter | SaaS | Entry tier. Core visitor management with lower capacity limits. |
| saas-professional | SaaS | Mid tier. Adds premium features (CRM, calendar, WLAN), higher limits. |
| saas-enterprise | SaaS | Full feature set with high or unlimited limits. |
| self-hosted-professional | Self-Hosted | Mid tier equivalent for on-premises deployments. |
| self-hosted-enterprise | Self-Hosted | Full feature set for on-premises. |
There is no self-hosted starter tier — self-hosted deployments require at least the professional tier.
What's always included
Every license tier includes:
- Visitor lifecycle (pre-registration, check-in, check-out).
- Default document templates (NDA, WiFi AUP, GDPR notice) with digital signature capture.
- Host notifications.
- Audit log.
- Admin dashboard (visitor directory, site management, user management).
- Control Plane connectivity and software updates.
What's tier-dependent
Premium features and capacity limits vary by tier. See Entitlements for the full breakdown.
How licensing works technically
- Your Atrium instance periodically checks in with the Control Plane.
- The Control Plane responds with a license grant — a signed payload containing your SKU, entitlements, quantity limits, and expiry date.
- The application caches the license grant locally and enforces it.
- If the Control Plane is unreachable, the cached license remains valid for a grace period (default: 30 days).
The license is enforced locally — the Control Plane is not in the runtime path of API requests. This means your Atrium instance works normally even if the Control Plane is temporarily down.