Wake on WAN lets you power on any machine — desktop, homelab rack, office workstation — from your phone, a shell, or a cron job. Sub-second wakes, 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 binary, any always-on device. Raspberry Pi, NAS, router — it sips <6 MB RAM and opens a single outbound connection to the control plane.
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 an outbound mTLS 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.
Script it. Cron it. Pipe it. wowan wake, wowan watch, wowan sleep. JSON output everywhere.
Tap to wake. Widget on your home screen. Fingerprint-gated. One swipe from lock screen to a booted workstation 400 miles away.
"Boot the build server at 07:00 weekdays." Cron syntax, timezone-aware, retries on failure, never misses a wake.
Share a fleet with colleagues. RBAC per host, audit log per wake, SSO when you grow up.
React to state changes. Trigger a CI job when the build box comes online. Zapier, n8n, whatever — we publish events.
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. Source-available. Audit it, pin it, run it in an air-gapped lab if you must.
Every workflow starts with a flag, ends with JSON. Designed to be piped, cronned, and scripted into oblivion.
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 128 GB 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. Wake-on-webhook from your git provider, run the job, sleep. Scale to zero, literally.
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 mTLS
subscribes to wake rpc
WoL magic packet
broadcast · unicast · directed
Pay for the work you're doing, not the seats you're not.
wowan wake.asleep → waking → online) to every subscribed client in real time. When you call rpc.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). We document the setup for every common OS.wowan wake HOST, or hit POST /v1/hosts/HOST/wake. Personal API tokens for humans, service tokens for CI, webhook-triggered wakes for git providers. All documented, all rate-limited, all audited.Free forever for your first three hosts. 14 days of Pro, no card.