VeilNet Plane refers to the overlay network formed by the VeilNet Conflux instance, which is divided into two categories:
- Community Planes: Community Planes are created for the VeilNet community and are accessible to anyone with a VeilNet account. They are our offering to replace the outdated TOR network, which aims to support a secure network with absolute privacy for personal users. Self-hosting VeilNet Conflux in portal mode under community planes will earn credits to access community planes in Rift mode on any devices.
- Private Planes: Private Planes are created by users with an active subscription. Only the user who has been invited can access Private Planes. Private Planes offer a secure “air-gaped” network for teams or organisations to connect their infrastructure or internal networks, as well as offering secure access for remote working.
How it works #
Each VeilNet Plane has its own dedicated control channel that is undiscoverable unless given information in advance. VeilNet Conflux instances under different planes will not be able to communicate with each other, and are not aware of each other’s existence.
Each VeilNet Plane also has a customizable IP address range set by the user, instead of being fixed to the carrier GNAT IP address range 10.64.0.0/16. This offers compatibility with the Kubernetes pod subnet or any local networks.
VeilNet Planes are also associated with a Veil, which is tied to a specific geo-location. This offers access control based on geo-location, which is absent in all other overlay network providers. VeilNet Planes can also be associated with Teams, VeilNet’s access control based on user identities, rather than IP addresses and subnets.