About
Built because CGNAT is annoying.
Linkvec started as a personal tool for reaching machines behind carrier-grade NAT. It turned into a platform when it became clear the problem needed more than a script.
Why Linkvec exists.
The problem
Most ISPs hand out CGNAT addresses. SSH tunnels break on reconnect. ngrok works but you cannot run the broker. Tailscale works but the coordination server is theirs. WireGuard works but you need static IPs and a weekend to configure it.
The gap
Every tool forces a choice: take the managed product (no control) or do it yourself (no product). There was nothing that provided both a complete, polished tool and the option to own every layer of infrastructure.
The decision
Build it. Named tunnels, three-path routing, HTTP-over-broker, mesh VPN, hub sharing — with a self-hostable broker as a first-class component, not a bolted-on option.
What Linkvec believes.
Choice is a feature, not a trade-off.
Choosing your broker, your path, your relay should not cost you usability. Linkvec makes every layer configurable without making it complicated.
Your data plane should be yours.
If you self-host the broker, your traffic never touches a third-party server. That is a structural guarantee, not a policy that can change.
Security should be structural, not just configured.
No root daemon. No inbound ports. Bounded blast radius per tunnel. These are design decisions, not optional hardening steps.
Find Linkvec.
The project is open. Come read the code, ask questions, or just follow along.
GitHub
Source code, issues, and releases. The CLI and linkvec-broker are both on GitHub.
Explore the product.
Install in 60 seconds. Bring your own broker or use ours.