VeilNet is an ephemeral, secure network that supports full VPN functionality while relaying data through a decentralized architecture — similar to but more advanced than Tor. It uses post-quantum encryption (ML KEM) to protect your data against future quantum threats. Designed as a “non tracable, non loggable” system, VeilNet enables anonymous, scalable, and dynamic connections without relying on any central authority. 

Traditional VPNs route all your traffic through a single server, creating a fixed and traceable tunnel. In contrast, VeilNet connects you to a dynamic network of decentralized relays. Each destination you visit can use a different exit point, making it feel like you’re using hundreds of VPNs at once. This not only enhances privacy and anonymity but also distributes traffic for better performance. Plus, VeilNet uses post-quantum encryption, making it secure against even future quantum threats. 

VeilNet uses ML-KEM, a post-quantum key exchange algorithm selected by NIST to withstand quantum computing threats. Unlike conventional TLS encryption, which relies on elliptic-curve Diffie–Hellman and can be broken by Shor’s algorithm, ML-KEM is based on lattice cryptography. Cracking it would require hundreds of billions of stable physical qubits — an amount so extreme that the energy needed exceeds the capacity of our entire solar system. In short, VeilNet is designed to remain secure even in a post-quantum world. 

VeilNet Domains are human-readable identifiers used to logically separate groups of VeilNet Portals. Unlike traditional DNS domains, they are not used to resolve website addresses. Instead, they act as secure, isolated namespaces within the VeilNet network. Portals assigned to different VeilNet Domains are completely unaware of each other’s existence and cannot communicate — providing strict isolation for privacy, security, or organizational boundaries. 

Each VeilNet Domain establishes a logically isolated network of Portals. Portals in different domains operate over separate control signal channels, each secured with its own unique encryption keys and metadata isolation. This means routing, discovery, and coordination are entirely domain-scoped. A Portal in one domain cannot detect, connect to, or interfere with Portals in another — enforcing hard boundaries for privacy, security, and multi-tenant deployments. 

Yes — but only for private domains, which require at least a Team-level subscription. Private domains are fully user-owned and managed; only the domain owner can view, modify, or assign Portals to it. In contrast, public domains are created and maintained by VeilNet administrators to support the global relay network. Importantly, VeilNet administrators have no access or visibility into private domains — they remain entirely under the control of the domain owner. 

A public domain is like public infrastructure — open and accessible to all VeilNet users. Anyone can route traffic through Portals in a public domain. In contrast, a private domain is like an exclusive club: only authorized members even know it exists. Portals in a private domain are invisible and inaccessible to outsiders, ensuring complete isolation and control for teams, organizations, or sensitive use cases. 

Yes. You can bridge a VeilNet Domain to external networks or services using VeilNet Portals. A Portal acts like a secure gateway, allowing you to link a VeilNet domain with a physical LAN or cloud environment — much like connecting two private networks together. This makes it possible to securely access on-prem systems, internal APIs, or legacy infrastructure through the VeilNet overlay. 

A VeilNet Portal is a secure, self-hostable relay node that forms the backbone of the VeilNet overlay. It acts as a gateway between the VeilNet network and the user’s local, cloud infrastructure, or internet.

A VeilNet Portal acts like a Tor relay — but without needing to be publicly accessible from the internet. It securely relays encrypted traffic between Rift clients, other Portals, or external networks. Because Portals are not exposed to the open internet and operate within isolated domains, they are highly resistant to timing correlation attacks that affect traditional anonymity networks like Tor. This design enables private, dynamic routing without compromising security or discoverability. 

Tailscale connectors are built on WireGuard tunnels with peer lists and routing managed by a centralized coordination server. They require a global control plane to establish and maintain connectivity.

VeilNet Portals are fundamentally different. They do not use WireGuard, have no peer lists, no static routing tables, and no central server. Instead, each Portal is powered by the VeilNet Anchor — a custom-built system that combines software-defined networking, distributed dynamic programming, and reinforcement learning to make autonomous decisions about routing, encryption, and relay behavior.

It’s a fully decentralized, intelligent system that adapts in real time — delivering privacy, resilience, and performance without configuration. It just works — like magic, but grounded in serious tech. 

Yes — VeilNet is built for self-hosting. Using the VeilNet Console, you can automatically generate a ready-to-use Docker Compose manifest with the correct configuration for your environment. Whether on-premises or in the cloud, setup is fast and streamlined.

Importantly, if you self-host a Portal in a public domain, you’ll earn MP (Measurement of Participation) credits, which can be used for subscription-free access to VeilNet services. This incentivizes community contribution and helps power the decentralized infrastructure. 

Yes — it’s completely safe. All data in VeilNet is end-to-end encrypted using post-quantum cryptography (ML-KEM). Relay Portals, including your own, can never decrypt, inspect, or modify the traffic they forward. They simply move encrypted packets from one point to another — like a sealed envelope passed along a chain.

Even if your Portal relays other users’ data, it has no visibility into the content, source, or destination. Likewise, when your own data passes through the network, it remains unreadable and unlinkable to you, your identity, or your location. Even if your Portal serves as an exit point, you still won’t know who the source was.  

This separation of trust is fundamental to VeilNet’s design: zero trust in a already exclusive network. 

Yes — it’s completely safe and actually one of VeilNet’s game-changing features. Even when your Portal operates in a public domain, it will only respond to requests from your own Rift or trusted Portals. Other users have no way of knowing your local network is linked at all.

This creates a secure, invisible tunnel back to your home or office network — without needing dynamic DNS, domain names, public IPs, or port forwarding. Unlike traditional VPNs, VeilNet gives you frictionless access to your private systems from anywhere, with no exposure and no central coordination.

Your local network stays hidden. You stay connected — securely and privately.