VeilNet Master

VeilNet Master

VeilNet Master is the global control channel of the VeilNet system, implemented as a NATS-based super cluster designed for global reach, high availability, and minimal downtime.

NATS is a high-performance, cloud-native messaging system built for distributed systems. It provides sub-millisecond latency, efficient fan-out, and strong resilience under network partitions—making it ideal for a global control realm rather than a traditional request–response API.

VeilNet Master does not act as a centralized controller. Instead, it functions as a distributed coordination fabric, interconnecting Guardian services, Conflux instances, and supporting microservices across regions, clouds, and administrative boundaries.

By leveraging NATS Super Cluster architecture, VeilNet Master provides:

• Global access with region-local latency
• Active-active clustering across regions
• Automatic failover and self-healing
• Minimal downtime during node, zone, or region failures
• Event-driven, low-overhead control messaging

The Master channel carries control and coordination signals only. It never transports user data or application payloads, maintaining a strict separation between the control realm and the data realm.

This design allows VeilNet to remain operational even under partial outages or network partitions. As long as any portion of the NATS super cluster remains reachable, control messages can be dynamically rerouted, ensuring continuity of operations and consistent system behavior.

VeilNet Master therefore serves as a globally distributed, highly resilient control backbone—enabling VeilNet’s decentralized network to operate as a cohesive system without introducing a single point of failure.

Self-Hosting (Future Availability)

VeilNet is designed from the ground up to support self-hosted deployments without compromising security or trust.
However, full self-hosting is not yet publicly available.

In the future, self-hosting will be enabled through a certificate-based trust model. Organisations will be able to request a dedicated set of cryptographic certificates from the VeilNet team, allowing their self-hosted components to participate securely in the VeilNet ecosystem.

This approach ensures:

• Strong cryptographic identity for self-hosted services
• Mutual trust between VeilNet-operated and self-hosted infrastructure
• Policy enforcement and revocation capabilities
• No reliance on shared secrets or static credentials

To support this securely at scale, VeilNet plans to establish a CA-like authority service responsible for certificate issuance, lifecycle management, and revocation. Once sufficient operational and security resources are in place, this authority will enable organisations to self-host Guardian, Master-adjacent services, or other VeilNet components while maintaining system-wide trust guarantees.

Until then, self-hosting is available by request and review, ensuring that early deployments meet VeilNet’s security, reliability, and operational standards.