Registered post for the internet.
Signed for on delivery, or returned to sender. One API call guarantees your message reaches someone — or tells you it didn't. Fluxmon walks your escalation chain — webhook and Slack today, SMS & voice as a planned feature — until a human signs for it, and hands you the receipt.
Not another on-call suite
No schedules, no incident timelines, no per-seat pricing games. Just the primitive every one of them buries: deliver-until-acknowledged, with a deadline. Embed it in your product, your cron jobs, your family logistics.
A receipt, either way
Like the slip that comes back from the post office, except it always comes back. Every missive ends in exactly one of two states: ACKED by a named recipient at a known time, or FAILED with the full audit trail of who was tried and when. Never a shrug.
The whole API, honestly
curl https://fluxmon.example/api/v1/missives \
-H "Authorization: Bearer $FLUXMON_KEY" \
-d '{
"subject": "Freezer #2 is at -4°C and climbing",
"chain": "cold-storage",
"deadline_seconds": 900
}'
# → 201 {"id":"…","state":"STAGED","deadline":"…"}
# Fluxmon now escalates: webhook → Slack → SMS → call,
# each step with its own ack window, until someone answers
# — or the 15-minute deadline fails it loudly.