A town council announces the festival to its residents. A server tells whoever maintains it that something broke. Both are the same thing: someone has something to say and someone needs to hear it.
curl api.achtung-app.com/v1/notify \
-H "Authorization: Bearer achtung_token" \
-d "The nightly backup failed"The nightly backup failed
db-prod-1 · out of disk space
For anyone who informs a lot of people at once. You create a channel, people subscribe, and what you publish reaches them. No mailing lists nobody opens, no posters nobody sees.
So your own services can reach you. A token, one HTTP request, and the notification is wherever you are. Errors, deploys, tests, whatever you like.
Notifications aren't lost when you swipe them away. They stay in an inbox: you open them when you can, mark what you haven't read, and archive what you no longer need.
When a token ends up in a public repository, it has to be changed. If that token was in seven places, that's seven deploys to touch and an afternoon gone. So here you create as many as you like and give each service its own: one leaks, you rotate one.
Shop CI
acht_…f4Kp2xQz
Backup cron
acht_…9Lm7rTvB
Router alerts
acht_…2Wq8ndYh
Creating the account takes less than reading this sentence. The first notification, a little less.
Create accountLa app de Android está en pruebas. Sign up to try it.