Stuck behind CGNAT?
Reach your Raspberry Pi, home server, or office PC over a private mesh when port forwarding is not available.
v1.0.0-rc2 controlled field release
VeloraMesh is a low-latency private mesh VPN for games, remote desktop, file transfer, and personal devices.
Direct P2P by default. No relay in v1. No public cloud. Simple, fast, and under your control.
Client platforms
Windows / macOS / Linux / Android
Field result
RDP, LAN discovery, and large file transfer validated
Release state
Packaged as RC with checksums and legal files
Reach RDP and SSH services through your own private network without exposing those services to the public internet.
Reach your Raspberry Pi, home server, or office PC over a private mesh when port forwarding is not available.
Keep internal services off the public internet and expose them only to authorized VeloraMesh devices.
Classic LAN discovery flows can meet inside one virtual network for low-latency game sessions.
VeloraMesh hides the networking complexity while your devices meet inside one secure virtual LAN.
Low-latency virtual LAN behavior for Counter-Strike, FlatOut, and classic LAN games.
Reach your PC, Mac, and Android devices by private IP for RDP and local services.
Access servers, homelab devices, media boxes, and dev machines from one private network.
The value is simple: stop caring where the device is and connect to it directly.
The server operator creates the network name and join secret; the control plane manages only the derived public verifier, members, and endpoint freshness.
Windows, macOS, Linux, or Android clients join once and keep running as a service or VPN.
Peers talk over encrypted UDP directly; when possible, data traffic never crosses the server.
VeloraMesh uses modern cryptography, server-signed membership, and short-lived sessions/tickets to build private mesh access with secure defaults.
Not part of the current RC; planned after the core matures.
No. VeloraMesh v1 runs with your own Ubuntu control plane and is designed for direct P2P data paths.
v1 is direct-only. A future relay is planned only as optional self-hosted support for extreme NAT cases.
Not yet. Packages are distributed with EULA, privacy, security, and third-party notice files.
Yes, on networks that permit a direct UDP path. Devices in the same VeloraMesh network can reach RDP, SSH, and HTTP services through virtual IPs. Connectivity depends on NAT and firewall policy; v1 uses direct P2P.
Yes. Pilot networks, Ubuntu API/edge separation, firewall guidance, and client rollout support are available through WhatsApp or email.
If the service is reachable only over VeloraMesh private IPs, access also requires an authorized device and active mesh membership.