EdgeVISS Cloud Manager
Licensing & Governance
Two independent license layers, a full audit trail of tracked actions, and organization-scoped team access — the controls a commercial deployment is actually audited against.
Two layers, deliberately independent
Deployment Licenses
Created automatically with every organization. The validity an application deployment is checked against: an optional expiry and an active, expired or blocked status. The number of gateways an organization may enrol is set once, on its plan.
Gateway Licenses
Node-locked, fully-offline feature-tier unlocks (FEATURE_*) per gateway, verified entirely on-device — never a live call-out. Signed with the Manager's own private key and checked against a UUID gateway ID, rejecting a pasted device name or license key at issuance time.
Revoking a gateway license
Not purely an audit record — what happens next depends on whether the gateway is actually reachable.
Enrolled + connected
Picks up the revocation automatically on its next commands poll (typically within a minute) and clears its own stored key.
Not enrolled, or connectivity not activated
Has no way to receive the revocation — remove the license by hand from its own System → License page instead.
Every tracked action, one log
Platform-admin-only visibility across the organization — the 200 most recent entries, newest first.
Team access, scoped to your organization
An org admin invites teammates by email as Admin or Member. Invites can be revoked before acceptance; members can be removed after — except yourself, so an organization can never accidentally lock out its own access.