Mesh (vspaces)
How ForestVPN's private mesh works for developers — device-to-device connectivity, MagicDNS names under mesh.fvpn.net, and where end users manage their own mesh.
A vspace is a private mesh: the devices in an account reach each other directly, end-to-end encrypted, routing peer-to-peer when a direct path exists and falling back to a relay when it does not. It is the same mesh your SDK brings up when a device joins the network.
Setting up a mesh in the app?
If you just want to link your own devices into a private network, the app does it for you — see the consumer help center at forestvpn.com/help.
Mesh names (MagicDNS)
Devices in a mesh get stable names under mesh.fvpn.net, so one device can reach
another by name instead of address:
# Reach another device in the mesh by its MagicDNS name.
ping work-laptop.mesh.fvpn.netNames stay leak-free under an exit node, and split-DNS routes only the queries you choose. See the Infrastructure API guides for how the mesh, devices, and consumers fit together, then start from a quickstart.