I'm the founder at Netrinos. I built a WireGuard-based mesh VPN because remote access has always been a pain. After years of SSH tunnels, IPsec headaches, and the fail2ban log horror movie, I wanted something simpler: install, sign in, get work done.
What it does:
- Creates a LAN-like overlay network across your devices
- Direct P2P connections using WireGuard, no central server routing traffic
- Each device gets a stable IP + DNS name (pc.you.netrinos.com)
- Fallback relay when direct connections fail (encrypted end-to-end, we can't see your traffic)
The hardest part is NAT traversal. UDP hole punching works most of the time. The rest is a cocktail of symmetric NAT, CGNAT, and serial NATs. We use STUN-style discovery and relay fallback for the edge cases. Biggest discovery: how low-end residential ISP routers just barely work, and how much technical wizardry it takes to hide that behind a clean, simple UX.
Stack: Go backend, WireGuard kernel mode (macOS is userspace), Wails.io for cross-platform UI. Traffic doesn't touch our servers except for relay fallback, and you can self-host the relay.
Popular use cases: RDP to home PCs, access NAS without exposing it, SSH into headless Linux boxes - one customer manages hundreds of IoT devices in the field, avoiding issues with customer routers.
We just released Pro with multi-user, access control, and remote gateway routing.
Personal is free (up to 100 devices). Pro adds team features.
Your feedback will really help shape our roadmap:
- What do you expect from a simple mesh VPN for small teams?
- What do you see as missing from current tools?
- What's lacking from your current remote access setup?
Comments
I'm the founder at Netrinos. I built a WireGuard-based mesh VPN because remote access has always been a pain. After years of SSH tunnels, IPsec headaches, and the fail2ban log horror movie, I wanted something simpler: install, sign in, get work done.
What it does:
- Creates a LAN-like overlay network across your devices
- Direct P2P connections using WireGuard, no central server routing traffic
- Each device gets a stable IP + DNS name (pc.you.netrinos.com)
- Fallback relay when direct connections fail (encrypted end-to-end, we can't see your traffic)
The hardest part is NAT traversal. UDP hole punching works most of the time. The rest is a cocktail of symmetric NAT, CGNAT, and serial NATs. We use STUN-style discovery and relay fallback for the edge cases. Biggest discovery: how low-end residential ISP routers just barely work, and how much technical wizardry it takes to hide that behind a clean, simple UX.
Stack: Go backend, WireGuard kernel mode (macOS is userspace), Wails.io for cross-platform UI. Traffic doesn't touch our servers except for relay fallback, and you can self-host the relay.
Popular use cases: RDP to home PCs, access NAS without exposing it, SSH into headless Linux boxes - one customer manages hundreds of IoT devices in the field, avoiding issues with customer routers.
We just released Pro with multi-user, access control, and remote gateway routing.
Personal is free (up to 100 devices). Pro adds team features.
Your feedback will really help shape our roadmap:
- What do you expect from a simple mesh VPN for small teams?
- What do you see as missing from current tools?
- What's lacking from your current remote access setup?
Use code HNPRO26 for 30 days of Pro.
https://netrinos.com