notifything
Planned · the commands are the design
One call for every message.
Email, SMS and chat each mean a provider, a key and retry code in every project. notifything is one API in front of all of them.
- 1 key per project
- 1 call for any channel
- 1 line to swap a provider
- 0 provider keys in a project
Features
The boring failures, handled once.
-
Scoped keys
A project's key can send to its own groups on the channels you allow, and nothing else.
-
Any channel
A project says who and what. notifything decides the channel, the provider and the retry.
-
Groups in one file
Moving the ops alerts from one chat to another is an edit, and no project knows it happened.
How it works
A seam in front of every provider.
-
1
Scope
Each project gets one key with the scopes it needs, so revoking it is one command.
-
2
Send
One call names the recipient and the message, so no project learns a provider's shape.
-
3
Route
Channels and providers are configuration, so changing them needs no pull request anywhere.
Who built it
Built by Rytter.
I'm Jakob Rytter. I build software and run it, from the server to the screen, and notifything is the seam every project of mine will send through.