WAVE Mesh

WAVE's conversion layer for reachability. Every WAVE device joins one flat, NAT-regardless, WAVE-owned mesh with a single identity — direct when the net allows, relayed when it doesn't, controlled and metered end to end. Not a borrowed tailnet — your devices on the WAVE network.

WRT identitymultihomingdiversity-gridrelay-fallbackzero-configno inbound

  device ──▶ WAVE Coordinator (dial out :443) ──▶ flat Mesh address
   │ WRT          registry · endpoint map · policy        │
   └───────── direct (Iroh) ◀── or ──▶ relay (moq.wave.online) ───────┘

See, reach, route, control, and meter every interface, device, stream, and piece of content — one identity (WRT), one network, one bill. Stream + device orchestration and content riding the mesh, all behind the gateway's mesh scope.

Pricing

Value-based and metered monthly — the coordinator's cost to operate is effectively zero, so price reflects the reliability delivered, not raw infra (~99% gross margin by design). Inert until a subscription attaches: every dimension bills $0 until your mesh subscription is active.

$0.0002 / opRequests routed — the core usage unit. At typical heartbeat volume that's about $6 per device / month, the overlay-network market norm.

$0.02 / eventFailover — the reliability premium: the moment the stream didn't drop (heartbeat-driven re-route).

$2.00 / region·moActive regions — footprint and reach, per active region per month.

$1.00 / policy·moRouting policies — the control surface, per active flow/routing policy per month.

What's live + proven: the control plane — coordinator and the M-A → M-G spine (registry, multihome route planning, heartbeat-driven failover, orchestration, content, authz + audit, billing), customer-key auth, and content dedup. Reachable at api.wave.online/v1/mesh/*, gateway-trust only — never an open endpoint, scoped to your account and audit-logged.

Roadmap, not yet hardware-proven: the multi-ISP / two-uplink physical braid (true link diversity across distinct uplinks) is implemented in the coordinator's path planner but not yet proven over real dual-uplink hardware — we label it roadmap, not a benchmark or a customer claim.

Read the docs →