live ntfy.sh public broker cf access gated

Push notifications for Vaspian ops and the home lab.

Every alert, deploy ping, and home-lab heartbeat that lands on your phone routes through one of 6 ntfy topics on ntfy.sh. This site is the canonical view of what we publish, where it runs, and how to receive it.

Wire up your phone → Browse topics Send a test

Topics

3 vaspian · 3 aloi

Broker

ntfy.sh

public tier

Auth

Cloudflare Access

Clients

iOS · Android

+ web

what

What we monitor

· VoIPMonitor — call quality, packet loss, fax failures
· Deploy outcomes for in.vaspian.com services
· Vaspian platform incidents and degraded carriers
· Home lab — Proxmox, containers, *arr stack
· Home WAN uplink and tunnel health

where

Where it runs

· Broker: public ntfy.sh
· Publishers: Vaspian servers, GitHub Actions, cron jobs, UniFi
· Registry: ~/.config/ntfy/topics.yml
· CLI: topics.sh · send.sh
· This site: Cloudflare Pages + Access

how

How it works

A publisher POSTs to https://ntfy.sh/<topic> with a message body and metadata headers.
ntfy.sh fans out the payload to every device subscribed to that topic.
The ntfy mobile app delivers it as a push notification with the chosen priority, tags, and click target.

Naming convention

Topics are globally namespaced on ntfy.sh. Ours follow <scope>-<area>[-<purpose>] — scope is aloi (home) or vaspian (work). Urgency is encoded by the Priority header, not the topic name.

$ curl -d "Hello" \
    -H "Title: Test" \
    -H "Priority: high" \
    -H "Tags: warning" \
    https://ntfy.sh/vaspian