Skip to content
wavemesh
Early development: What works today

Reach your devices from anywhere.Through your own server.

At 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.
*.wave.example.comwave0
relaylaptop10.77.0.2nas10.77.0.3workstation10.77.0.4grafanaCluster service

Every path is direct. The devices found each other through their NATs.

  • Linux
  • macOS
  • Windows
  • Synology DSM 7
  • Kubernetes
  • iOSin progress
  • Androidin progress

One binary for Linux, macOS and Windows (amd64/arm64). Synology DSM 7 has an SPK package.

Downloads

Latest releases

Choose a version and download the package for your system directly from GitHub.

On the network in three steps

A wave is a network. Start the server once, then install the right client on each device.

Read the full guide
  1. Start the control server

    Control 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 .
  2. Install the client

    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
  3. Log in and connect

    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

Local services on the internet: the pier

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

What a wave does

Direct whenever possible

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.

wave status
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

Several waves at once

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.

wave status
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 ago

Names under your domain

Give 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.

  • laptop.wave.example.comconnected
  • nas.wave.example.comconnected
  • workstation.wave.example.comconnected
  • build-runner.wave.example.com3 hours ago
$ ssh nas.wave.example.com

Real certificates for every device

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
$ 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.

Access as a graph

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.

Cluster and wave, both ways

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.

Signed updates

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.

Local services on the internet

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.

What the server knows, and what it doesn't

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.

LayerKnows private keys
Control serverno
Relayno
Pier nodeno
Deviceonly its own

Signed network map

The control server signs the network map with its Ed25519 key, and devices only accept what matches.

Authenticated discovery

Even the packets devices use to find each other are encrypted: X25519 and XChaCha20-Poly1305.

Login you control

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.

No plaintext at the pier

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.

Two locks at the pier

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.

Certificates for own names only

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.

What it costs

wave-mesh is licensed under the Elastic License 2.0. Running it yourself is free and stays free.

Run it yourself

€0no device limit

Every feature, on your own infrastructure. Use it, change it and run it inside your company.

  • Control server and relay
  • Clients for every platform
  • Updates through your server

Hosted free

€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.

  • Up to 3 people
  • Up to 100 different devices
  • Control server and relays run by us

How we count

  • The same person or device in several waves counts once.
  • Open invitations reserve seats.
  • Existing customers keep their waves.

The networks of the waves stay separate; only the limits count account-wide.

More people or devices? That is what “Hosted paid” is for.

Hosted paid

€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.

  • Control server and relays run by us
  • Updates and backups included
  • Your own domain for your devices
Manage subscription

Installation in your cloud

€4,650one-off

We install wave-mesh in your company's cloud. Afterwards, an optional maintenance package covers updates and operations.

  • Control server and relays in your cloud
  • Your clusters and devices connected
  • Optional: maintenance package for 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.

Roadmap

Everything under “Available” ships in the stable releases. “Next” is in progress or planned; new additions are listed in the changelog.

Read the changelog

Available

  • Direct connections through NAT
  • Relay when punching fails
  • Names under your own domain
  • Let's Encrypt certificates
  • Services from your Kubernetes cluster
  • From the cluster into the wave
  • Sign-in via OpenID Connect and second factor
  • Access rules and audit log
  • Signed self-updates
  • Signed and notarised macOS clients
  • Wave services on the open internetpier and wave expose; not yet checked at a real ingress on the internet

Next

  • iOS and Android appscore done, apps in progress
  • Subnet routers and exit nodes

Questions

How is this different from a hosted mesh VPN?

You 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.

How fast is it?

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.

Do I need my own domain?

No. Without a domain your devices live under .internal and are still reachable by name. Publicly valid certificates need a domain you own.

What does the licence allow?

Using, changing and redistributing it, including inside your company. Offering wave-mesh to third parties as a hosted or managed service is not allowed.

What do I need on the server?

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.

Do I need port forwarding to put a service on the internet?

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.

Does the pier see my traffic?

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.

How do I list exposed names and remove them again?

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.

What does “Hosted free” include?

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.

How does the free plan count people and devices?

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.

Do open invitations count already?

Open invitations reserve seats. An invitation therefore takes one of the seats before the person has accepted it.

What changes for existing customers?

Existing customers keep their waves. The paid plan keeps charging per user.

Bring your devices together.

One server, the right client on each device, and everything talks directly.