Company admin
Tenant-scoped administration, roles, policy, audit, node status and connector configuration.
Run your own VIX edge without separating from the master trust fabric.
Each customer gets an isolated deployment, its own administration surface and local operational control while master VIX nodes remain the root for chain authority, entitlement, trust policy and governed updates.
Tenant architecture
VIX-MSG gateway
Local encrypted message service integrated with VIX identities, groups, receipts and proof anchoring.
VIXNet relay
Tenant relay and routing services connected to master-trusted route and proof infrastructure.
Isolated workloads
Basic website and service hosting in separate containers with controlled ingress and persistent state.
Master dependency
The company owns and operates its edge. The edge does not become an independent fork of VIX. Enrollment, licensing, node identity, trust policy, chain proof and update entitlement remain cryptographically tied to the master platform.
CUSTOMER ADMIN → TENANT NODE → VIXNET / VIX-MSG / HOSTING
↓
MASTER VIX TRUST ROOT
licensing · policy · chain · proof · updates
Commercial control
One-time subscription token
Enrollment credentials are hashed at the master and consumed after successful activation.
Master-signed manifests
Features and plan rights are accepted only when signed by the pinned master Ed25519 key.
Node-signed heartbeat
The master validates heartbeat signatures from the enrolled node identity.
Revocation + updates
Commercial nodes are designed for central revocation, version policy and controlled image channels.