Reach yourself wherever you actually are.
A notification is recorded on your computer first and always. A channel is the optional second step that carries it somewhere else — your phone, a chat room, an inbox, an endpoint of your own. Nineteen are implemented; every one is off until you configure and enable it.
19
adapters implemented
0
enabled before you say so
1
local record that stays authoritative
Pick the ones you already use.
You can add more than one of each — a quiet Slack channel for completions, your phone for approvals only.
Your own phone
The path built for this job, rather than someone else's product with notifications bolted on.
Push services
Self-hosted or public push, if you already run one.
Chat and mail
Where your team already looks. Message content is excluded by default.
Automation and self-hosted
For anything with an endpoint or a broker of its own.
Paid messaging
Billed per message by the provider, and labelled as such in the interface.
Delivery is secondary, on purpose.
A channel that is down, misconfigured, or rate limited never removes, changes, or delays the local record.
Tested with fake transports, not with your account.
Automated tests use synthetic secrets and fake transports. They prove the adapter builds and sends the right request; they cannot prove your provider account, template, broker ACL, quota, or recipient is correct. That is what each channel's Test button is for — after you have read what it will cost and who will see it.