No relay. No vendor. Just peers.

Uptime Monitoring, Peer to Peer

Your browser connects directly to your nodes via WebRTC. Heartbeats flow peer-to-peer. The only server is a stateless signaling relay that stores nothing.

Open DashboardHow It Works

Zero Server Overhead

Your Browser
— WebRTC —
Your Node
signaling only (stateless)
STUN: stun.l.google.com

After the WebRTC handshake, the server is out of the loop. Heartbeats, latency data, uptime stats -- all peer-to-peer. Google STUN handles NAT traversal for free.

How It Works

1

Open the Dashboard

Get a Peer ID instantly. Your browser tab becomes a monitor node -- no install, no account.

2

Add Monitors

Monitor peers via WebRTC heartbeats (your Pi, home server, another browser) or ping URLs directly via HTTP.

3

Everything Stays Local

All monitoring data lives in your browser. The server only relays WebRTC signaling -- stateless, zero storage.

Run Your Node

Pick how you want to participate

www

Browser Tab

Open the dashboard. Your browser is the monitor node. WebRTC heartbeats to peers, HTTP pings to URLs. Zero setup.

Start now →
>_

Self-Host (Node.js)

Run a lightweight Node.js process on your own server or Raspberry Pi for always-on monitoring.

Coming soon
Pi

Plug & Play Hardware

Pre-configured Raspberry Pi. Plug it in, connect to WiFi, and it joins the network as a peer.

Coming soon