Wake on WAN lets you power on any machine — desktop, homelab rack, office workstation — from your phone, a browser tab, or a scheduled job. Live fleet state, zero router surgery.
A tiny agent on your LAN. A control plane you talk to from anywhere. A magic packet that lands on your sleeping machine in under a second.
One static Go binary on any always-on device — Raspberry Pi, NAS, router. It opens a single outbound connection to the control plane and waits.
Phone, laptop, CI runner, shell script. Each client opens a persistent RPC channel to the control plane and subscribes to the hosts it cares about.
Send a wake RPC. The agent on the target LAN broadcasts the magic packet. Live-state updates stream back so you see the host come up in real time.
Built by people who got tired of yak-shaving router configs every time they wanted to wake a machine.
The agent makes a single outbound WebSocket connection. Your router stays untouched. ISPs with CGNAT? Works the same.
Livequeries push every host transition — asleep, waking, online, dropped — to your dashboard as it happens. No polling.
One static Go binary for the LAN side. Install as a service on Linux, macOS, or Windows. A full user-facing CLI for multi-host orchestration is on the roadmap.
Native iOS + Android apps with tap-to-wake and home-screen widgets. On the roadmap — the web dashboard is mobile-friendly in the meantime.
"Boot the build server at 07:00 weekdays." Cron syntax, timezone-aware, durable timers — survives restarts of the control plane.
Organizations with member invitations, pending-invite tracking, and accept/reject flows. Per-host roles, per-wake audit log, and SSO (SAML, Google) are on the roadmap.
React to state changes. Trigger a CI job when the build box comes online. Public webhooks and a scriptable HTTP API are on the roadmap.
If your NIC speaks WoL (and it does — it's been standard since 1998), Wake on WAN will boot it. No driver games.
The agent is a single Go binary. Pin a specific version, run it in an air-gapped lab if you must.
The agent is a static binary you run as a service on your LAN. A full user-facing CLI for multi-host orchestration is on the roadmap.
Built for the homelab, taken seriously by the office.
Your GPU rig lives under the stairs. You live abroad. It's asleep 23h a day. One tap on your phone and it's ready when you SSH in.
Your work desktop has the RAM and the GPUs. You're on your MacBook at a café. Wake it, mosh in, close laptop when done.
Fleet of 40 desks. Half in on any given day. Schedule wake-on-arrival, sleep-on-idle. Power bill drops, morning queues don't.
Self-hosted runners don't need to idle. Schedule a wake at build-queue time, run the job, sleep. Webhook triggers from git providers on the roadmap.
We don't use WireGuard, overlay networks, or any of the usual suspects. A live database speaks RPC. Agents subscribe. It's simpler than you think.
cli · app · web · webhook
livequeries + rpc
fleet state · auth · audit
outbound WebSocket
subscribes to wake rpc
WoL magic packet
broadcast · unicast · directed
Pay for the work you're doing, not the seats you're not.
Early access: Starter + Pro check out today. Business and Enterprise are on the roadmap.
asleep → waking → online) to every subscribed client in real time. When you send a wake, the agent on the target LAN broadcasts the magic packet. It's a database doing its job.ethtool -s eth0 wol g on Linux, checkbox in Device Manager on Windows).Free on Starter: 1 user, 1 computer, no card required.