Nightbell

me.river.nightbell
by Zapstore Catalog

Uptime monitoring that runs on your phone. No server, no account.

Point Nightbell at anything that answers over HTTP, or at one element on a rendered web page, and it watches it, charts it, and gets loud when it breaks. There is no server and no account. The phone in your pocket does the checking, and your API tokens and target URLs never leave the device. Three kinds of monitor: - Status check: hit a URL, assert on the status code. - Request and response: pick the method, set headers and a body, assert on what comes back (contains, equals, regex, or a JSON field by path). - Page element: load the real page in an embedded browser and watch DOM nodes you picked by tapping them. Urgent alerts arrive as a full-screen red page with a looping alarm that keeps going until you acknowledge it, and it wakes the screen even if the phone is locked. A first-launch screen walks through the four Android grants a paging app actually needs (notifications, unrestricted battery, full-screen intent, Do Not Disturb access), because two of them have no system dialog and have to be opened by hand. A home-screen widget shows the worst monitor first. Settings let you shape the alert policy: what counts as down, sound, haptics, escalation, and quiet hours. Signed with the developer's own key. No Play Store listing.

First release: Nov 3, 2026, 1 total release.

Most recent release: Nov 3, 2026.

Website Repo

Appears in 0 app stacks.

0 sats / 0 zaps received in the past year.

Sats Received

Underlying data available via MCP: app_zaps, app_releases.

Zap Count

Underlying data available via MCP: app_zaps, app_releases.

Releases

  • Nov 3, 2026 3.20.0
    A host can now be watched as well as a service. Two new monitor kinds, **Ping** and **TCP port**, take an IPv4 or IPv6 address or a name and need no root. Asked for in #21. **Ping** sends 1 to 10 echo requests per check and shows the fastest, average and slowest reply and the packet loss. Every reply back is up, some lost is degraded, none back is down. **TCP port** connects to one port and hangs up. Refused, timed out and no route each get their own message. **This host:** put both on the same host and the monitor's screen reads them together, so you can tell the network from the service. Both kinds also list their recent outages and how long each lasted. **Passes before all-clear** works on every kind. Above one, an outage stands until that many checks pass in a row, so a flapping host no longer pages, clears and pages again. The default is 1, as before.
    More…
    Driven on the emulator against loopback, 1.1.1.1 and a server of mine. Packet loss was shown with faked replies. Ping on a real phone is the least proven part: if a phone refuses the socket, the monitor says so instead of calling the host down.