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. 

Yes, using VeilNet conflux is completely free and we encourage you to self-host conflux in portal mode under public plane!

Yes, but only in public plane and it is completely safe. More safer than other decentralised network such as ToR. Each packet is P2P encrypted via Kyber KEM and AES GCM 256, also authenticated by Dilithium. It is impossible for you to peek inside others packets and others could not peek into yours either.

Your conflux may serve as relay or the final exit node, but it is impossible for you to know where the packet is originated, except a randomly generated UUID that changes every time the conflux starts.

Since conflux utilizes WebRTC, your conflux is visible only within VeilNet. Your ISP (Internet Service Supplier) has absolutely no way to tell if you are using VeilNet conflux, or just any other real time messaging application such as Zoom, Microsoft Team, etc.

Yes, your conflux will fetch a identities list which including you and your team members only. And any traffic towards linked local network is only allowed if the traffic is originated from a known indentity, aka you or your team mates.

In fact, your conflux will ignore traffic towards linked local network if it is not allowed. Other user on the public plane will have no idea which or even any local network is liked via your conflux!