Self-hosted · Go · MIT · v0.7.0
Every message on time, from your own servers
notify delivers your product's notifications in-app, by email, SMS, push and chat. It holds them for digests and schedules, answers inbound email with agent drafts, and keeps every original. Each run is durable and survives a restart.
One binary and a dagnats sidecar. notify serve
Departures
| Time | Step | Status | Detail |
|---|---|---|---|
| 09:14:02.118 | trigger | Accepted | workflow v7 |
| 09:14:02.132 | in_app | Delivered | +14 ms · 2 devices |
| 09:14:03.040 | Sent | reply-to armed | |
| 09:14:03.041 | throttle | Passed | 1 of 3 this hour |
| 09:14:03.042 | digest | Held | weekly-billing |
| Mon 09:00 | push | Scheduled | America/Chicago |
Example run. Held steps wait on the engine, so a restart does not lose them.
One event in, every channel out
Your app sends one event. The workflow decides who hears about it, where, and when.
# your app, once curl -X POST https://notify.example.com/v1/events/trigger \ -H "Authorization: ApiKey $KEY" \ -d '{ "name": "invoice-paid", "to": { "subscriberId": "dan" }, "payload": { "amount": "$480.00", "invoice": "INV-2291" } }' # every /v1 response carries Notify-Contract: 1
The API only grows: /v1 changes are additive.
- Deliver in the appThe subscriber's inbox and live feed update first.
in_app - Send the emailWith a tokenized reply address, so an answer threads back.
email - Keep it politeA throttle caps how often one person hears from you.
throttle - Roll it upSimilar events wait and go out together on the subscriber's schedule.
digest - Wait for the right hourDelays run in the subscriber's own timezone.
delay
What it handles
The parts every product rebuilds, in one service you run yourself.
- Channels
- In-app, email, SMS, push and chat, with per-subscriber preferences, templates, layouts and translations. Provider adapters are optional, so you can start with your own SMTP.
- Timing
- Delays, digests, throttles and schedules that the engine holds durably, in each subscriber's timezone.
- Inbox and agents
- A subscriber inbox and conversations with agents. Agents run on the mesh.
- Inbound mail
- Replies come back in. notify receives mail over SMTP or a webhook, drafts answers for review, and keeps every original byte for byte.
- Operations
- One Go binary, SQLite, and blobs on disk or any S3 store such as Garage. A console for workflows, subscribers and deliveries.
Runs on
No hosted dependency in the delivery path.
- dagnats durable workflow engine
- NATS messaging
- SQLite records
- Garage or any S3 original mail