Command Palette

Search for a command to run…

ZarynZaryn
Zaryn documentation

Private networks and proxy

A WireGuard mesh for your machines, and Zaryn on a filtered internet.

Connect laptops, servers and CI into one encrypted WireGuard network through any NAT, and reach Zaryn through your own proxy when the internet is filtered.

For Developers and AI teamsFor Infrastructure and virtualization
Start the tutorial →Open in Zaryn ↗
Learning path

Get started with private networks and proxy

A guided path from "my devices can't see each other" and "Zaryn is blocked here" to a self-healing setup: a private WireGuard network for your devices, your own proxy for zev, every app or the whole computer, failover, and leak checks. Pictures first, every step explained.

⏱ About 30 minutes◔ From zero to advanced
  1. Stage 1Understand
    1. Two problems, two tools
    2. How a private network connects
    3. How the proxy helps
  2. Stage 2Private networks
    1. Make a network and join it
    2. Servers, CI and phones
    3. See its weak spots
    4. Share an app, pull faster
  3. Stage 3Proxy
    1. One command: zev proxy start
    2. Your links and subscriptions
    3. Every app, or the whole computer
    4. When it doesn't work
  4. Stage 4Go further
    1. Many servers: the fastest, and failover
    2. A private network through the proxy
    3. Safe by default

What you can do

  • Join devices to a private mesh in one command
  • Share an app with teammates privately
  • Use your own proxy and find what’s blocked
  • Get honest DNS on a network that lies
  • Measure your line and fix jitter and bufferbloat
  • Find why the internet doesn’t work, and fix it

Start here

Read these in order; the rest you can open when you need them.

  1. 1Get started with private networks and proxyA guided path from "my devices can't see each other" and "Zaryn is blocked here" to a self-healing setup: a private WireGuard network for your devices, your own proxy for zev, every app or the whole computer, failover, and leak checks. Pictures first, every step explained.
  2. 2Private networksConnect your laptops, servers, CI runners and apps into one private network, so they reach each other directly and securely, wherever they are.
  3. 3Your own proxy (zev proxy)When sites are blocked, use your own VLESS, VMess, Trojan, Shadowsocks, Hysteria2 or WireGuard servers for zev, every app or the whole computer; zev learns per network which sites need it, says why each goes the way it does, counts the data and shows a server as a QR code.

Every guide in Private networks and proxy

Get started with private networks and proxy

A guided path from "my devices can't see each other" and "Zaryn is blocked here" to a self-healing setup: a private WireGuard network for your devices, your own proxy for zev, every app or the whole computer, failover, and leak checks. Pictures first, every step explained.

Your own proxy (zev proxy)

When sites are blocked, use your own VLESS, VMess, Trojan, Shadowsocks, Hysteria2 or WireGuard servers for zev, every app or the whole computer; zev learns per network which sites need it, says why each goes the way it does, counts the data and shows a server as a QR code.

DNS that works on any network (zev dns)

zev dns finds which DNS resolvers really work from your network and how (encrypted, another port, TCP, through your proxy), throws away a censor's answers, checks DNSSEC signatures itself, and falls back to the network's own DNS so names never stop.

A better internet line (zev tune)

zev tune measures your internet line in full (latency, jitter and loss to the router and beyond, speed both ways, bufferbloat, DNS, path MTU, IPv6, Wi-Fi), then fixes what holds it back one change at a time, keeps only what measurably helped, and never leaves you without a connection.

Other products for you

Code hosting and version controlRepositories, branches, pull requests, CI and evals on zev.CI, evals and releasesEvery push built and tested in a locked-down container, and gates that keep main working.Packages and mirrorsA registry for npm, PyPI, Cargo, Zig and containers, and mirrors of the public ones.Files, storage and encryptionShare files by link, prove they are intact, keep private work encrypted.Network automationRouters and switches as a site: backups, drift, paths, a digital twin and safe rollouts.Network design repositoriesThe network’s source of truth as text, checked against reality and protected by intents.VirtualizationEvery VM on seven platforms, joined to the switches it runs through.How it worksContent addressing, the object model, IPFS and provenance.