Stable
v0.17.0
For regular use
Nov 16, 2026
Synology DSM 7
Release on GitHubAt the office, at home or on the road: wave-mesh connects laptops, servers, NAS boxes and clusters directly over WireGuard, even behind NAT and without port forwarding. You run the coordination server yourself, and it never sees a private key.
Several waves at once. One device is in your company's network, your own and a client's at the same time, without switching.Every path is direct. The devices found each other through their NATs.
One binary for Linux, macOS and Windows (amd64/arm64). Synology DSM 7 has an SPK package.
Downloads
Choose a version and download the package for your system directly from GitHub.
Stable
For regular use
Nov 16, 2026
Synology DSM 7
Release on GitHubUnstable
Preview build for testing
Nov 16, 2026
Synology DSM 7
Release on GitHubA wave is a network. Start the server once, then install the right client on each device.
Read the full guideControl server, relay and Postgres via Kustomize in your own Kubernetes cluster; a single server with k3s is enough. The server hands out addresses, names and rules.
$ cd deployment/server/overlays/mywave$ kubectl apply -k .
On Linux, macOS and Windows, wave install sets up the service. On Synology DSM 7, install the SPK and run setup once as root.
$ sudo ./wave install
Use wave login to connect the client to your server. On Synology, use the wave page in DSM. The device then finds the others in the wave on its own.
$ wave login https://control.example.com$ wave up
For devices to make local services reachable from the internet, you need a pier node as the wave's operator: set-pier creates the DNS record *.pier.<domain>, allow-pier permits it per device, and the pier node runs as the image wave-pier. After that, devices expose services themselves.
Pier docs in the README (German)Pier in the installation guide
Each device learns its public address over STUN, and both sides punch through their NAT at the same moment. When that fails, say behind symmetric NAT on mobile data, traffic goes through a relay. When the direct path opens up, the connection switches over without dropping.
Covered by end-to-end tests through real NATs that run in CI.
wave0 10.77.0.2
name laptop.wave.example.com
dns *.wave.example.com
relay connected wss://relay.example.com
PEER ADDRESS PATH HANDSHAKE
nas 10.77.0.3 direct 192.168.1.20:41641 3ms 12s ago
workstation 10.77.0.4 via relay 61ms 8s ago
cluster 10.77.0.9 direct 203.0.113.7:41641 18ms 31s ago
↳ https://grafana.wave.example.com 10.77.128.1
A device is in as many waves as you need, all of them at the same time: your company's wave, your own at home and a client's, even on different control servers. There is no switching between networks. Each wave stays on its own, with its own keys, its own addresses and its own names, and none can see into another.
If the addresses of two waves overlap, the client refuses the second instead of silently overwriting a route. In the apps for iPhone and Android (in progress), a single tunnel carries every wave, and each can be paused on its own.
control.example.com https://control.example.com
wave0 10.64.0.12
name laptop.corp.example.com
dns *.corp.example.com
PEER ADDRESS PATH HANDSHAKE
gitlab 10.64.0.3 direct 198.51.100.4:41641 9ms 5s ago
staging 10.64.0.8 direct 198.51.100.9:41641 11ms 40s ago
────────────────────────────────────────────────
wave.example.net https://wave.example.net
wave1 10.80.0.5
name laptop.home.example.net
dns *.home.example.net
PEER ADDRESS PATH HANDSHAKE
nas 10.80.0.3 direct 192.168.1.20:41641 2ms 12s agoGive a wave a DNS suffix you own, and your devices are called laptop.wave.example.com instead of 10.77.0.5. A local resolver answers only the wave's names; everything else goes to your usual DNS untouched.
Every device gets a Let's Encrypt certificate for its name. The private key is created on the device and never leaves it. Renewal runs unattended via Cloudflare, Hetzner, IONOS or INWX. Without credentials it still works; you then add the TXT record yourself.
$ wave cert
This wave answers dns-01 by hand, so laptop.wave.example.com needs a record first:
name _acme-challenge.laptop.wave.example.com
type TXT
value 0Zq8…
Waiting... Ctrl-C is safe: `wave cert` takes the same order up again.Members, groups, tags and services sit side by side as cards. A rule is an arrow, and the ports hang off the edge. The page shows who can reach whom before you save.
A plain Ingress with the class wave makes an internal service reachable inside the wave and nowhere else. In the other direction, pods reach the wave's devices and services by name, over HTTP and HTTPS with TLS end to end. The connector in the cluster has no inbound port.
The service installs new versions on its own, but only with a valid Ed25519 signature. If the new build cannot reach a server, it rolls itself back.
A service on localhost or in your LAN becomes reachable from the internet at app.pier.wave.example.com with wave expose app http://localhost:3000. The name resolves through the wildcard *.pier.<domain> to the pier node, an ingress passes TCP 443 through by SNI, and the pier node reads only the name. TLS ends on your device, with its own certificate. No port forwarding, no fixed address. wave expose --list shows your names, wave expose --remove app takes one out, wave pier status tells you whether the proxy is running. Not checked: the pier at a real ingress and the wave-pier image.
wave-mesh keeps the layers strictly apart. The control server only hands out public keys, the relay only forwards ciphertext, and the pier node only reads a name from the connection setup. None of them can decrypt the traffic between your devices.
| Layer | Job | Knows private keys |
|---|---|---|
| Control server | Identity, authorization, network map, DNS | no |
| Relay | Reflect addresses, forward ciphertext | no |
| Pier node | Read the name from the connection setup, pass the connection through | no |
| Device | WireGuard tunnel, local configuration | only its own |
The control server signs the network map with its Ed25519 key, and devices only accept what matches.
Even the packets devices use to find each other are encrypted: X25519 and XChaCha20-Poly1305.
Email and password with Argon2id and, if you like, a second factor from an authenticator app, or your OpenID Connect provider such as Pocket ID, Keycloak or Google. The operator creates accounts; there is no open sign-up.
The pier node only reads the name from the connection setup and passes the connection through the wave to the device. Encryption ends on the device, with its own certificate. The pier holds no key.
The operator permits the pier per device; the default is off. Only then can the device's owner expose a name and a port. If the operator withdraws the permission, the device's names go with it.
A device gets a certificate for the names it exposed itself: not for the whole wave, not for other devices' names, and only while the operator permits the pier. A certificate that has already been issued keeps working until it expires.
wave-mesh is licensed under the Elastic License 2.0. Running it yourself is free and stays free.
€0no device limit
Every feature, on your own infrastructure. Use it, change it and run it inside your company.
€0per customer account
We run the control server and relays; you just connect devices. The limits apply to your whole customer account, across all waves together.
The networks of the waves stay separate; only the limits count account-wide.
More people or devices? That is what “Hosted paid” is for.
€4per user per month
We run the control server and relays; you just connect devices. Paying yearly costs €40 instead of €48 per user. Choose the number of users when you book and change it any time.
€4,650one-off
We install wave-mesh in your company's cloud. Afterwards, an optional maintenance package covers updates and operations.
Offers for businesses. All prices exclude statutory VAT; our terms apply. The one thing not allowed is offering wave-mesh to third parties as a hosted or managed service.
Everything under “Available” ships in the stable releases. “Next” is in progress or planned; new additions are listed in the changelog.
Read the changelogwave expose; not yet checked at a real ingress on the internetYou own the coordination server: it runs on your infrastructure, not at a vendor. Your devices have names under your own domain, and each one gets a publicly valid certificate.
Today the data path runs in userspace. Expect 100 to 300 Mbit/s per device. A faster path through kernel WireGuard is planned but not built yet.
No. Without a domain your devices live under .internal and are still reachable by name. Publicly valid certificates need a domain you own.
Using, changing and redistributing it, including inside your company. Offering wave-mesh to third parties as a hosted or managed service is not allowed.
A Kubernetes cluster; a single server with k3s is enough. Control server, relay and Postgres ship as ready-made images and are set up with Kustomize. From outside you need HTTPS and UDP 3478 for STUN.
No, and no fixed address either. wave expose makes a service on your device reachable at a name like app.pier.wave.example.com, with no inbound port. For that, the wave's operator has to run a pier node and permit it for your device.
No. The pier node only reads the name from the connection setup and passes the connection on. Encryption ends on your device, with its own certificate. The pier holds no key and sees no plaintext.
wave expose --list shows the names and how each one is doing, wave expose --remove app takes one out. wave pier status tells you why a name does not work yet, for example because a certificate is missing, the tunnel is down or the device is offline.
We run the control server and relays for you. Each customer account includes up to 3 people and 100 different devices, across all waves of the account together. More is available on the paid plan, which is billed per user.
The same person or device in several waves counts once. The limits apply to the whole customer account, not to a single wave. The networks of the waves stay separate; only the limits count account-wide.
Open invitations reserve seats. An invitation therefore takes one of the seats before the person has accepted it.
Existing customers keep their waves. The paid plan keeps charging per user.
One server, the right client on each device, and everything talks directly.