Skip to content

License tiers

Vesana has three license tiers. All run on the same codebase — features unlock server-side via license key.

Feature matrix

Feature Community Pro Enterprise
Hosts up to 25 up to 250 unlimited
Tenants 1 up to 5 unlimited
Agent + collector ✓ ✓ ✓
Auto-discovery ✓ ✓ ✓
SNMP sensor picker ✓ ✓ ✓
MIB snippets (vendor-specific) – ✓ ✓
Custom dashboards up to 3 unlimited unlimited
Public status pages – ✓ ✓
Mobile app + push (shared FCM) ✓ ✓ ✓
Mobile push (own Firebase) – – ✓
AI chat (own provider) – ✓ ✓
AI analysis per service – ✓ ✓
Wiki ✓ ✓ ✓
SLA reports – ✓ ✓
PDF reports + scheduling – ✓ ✓
Anomaly detection + predictions – ✓ ✓
Policies (bulk config) – ✓ ✓
Custom roles + granular RBAC – ✓ ✓
Audit log ✓ (30 d) ✓ (90 d) ✓ (configurable)
Soft delete & trash ✓ ✓ ✓
Backup sidecar ✓ ✓ ✓
Multi-API replicas + distributed locking – ✓ ✓
Offline license – – ✓
NSCA receiver – ✓ ✓

Snapshot of this page

State at last_verified of this page. Current values: vesana.org/home#pricing.

Activation

Online (default)

  1. Copy license key in format OVS-XXXX-XXXX-XXXX from licence portal
  2. Admin → License → Set key
  3. Save

API server verifies against license.vesana.org at boot. On success, caches the result and rechecks every 24 h. Cache TTL keeps the server productive even during portal outages.

Offline license (Enterprise)

For air-gapped environments, offline-signed license files:

  1. Licence portal: Licenses → Create offline license with customer UUID
  2. Download <customer>-license.json
  3. Admin → License → Upload offline license

Offline licenses have a duration (typically 1 year) and must be renewed before expiry. Server warns 30 days ahead via banner.

Tester mode

For acquaintances and beta testers, a bypass:

echo "VESANA_TESTER_MODE=true" >> /opt/vesana/.env
docker compose -f /opt/vesana/docker-compose.prod.yml up -d

With tester mode active:

  • All features unlocked, no license key
  • Setup wizard skips license step
  • Instance registers with licence portal as tester
  • Lukas / vendor team can block updates per instance

Remove tester mode before handing over to a real customer

Anyone who knows the env bypass gets all features for free. For a commercial handover: remove VESANA_TESTER_MODE from .env, set license key, restart stack.

Details: Self-hosting → Tester mode.

Renewal & switch

Tier switch: new license key generated in licence portal, replaced in Vesana. No migration needed — data stays, only feature visibility changes.

Downgrade to Community: hosts above the limit stay registered but new ones can't be added until the limit is undercut.

What the license does NOT do

  • It doesn't restrict source access — anyone who clones the repo sees everything. Protection is via the license check at API boot, not obfuscation.
  • It doesn't phone home secretly — phone-home contains only {instance_id, hostname, version}, no tenant or check data.
  • It's per-instance, not per-server — one license can only be active on one instance.

Next