Notifications
by @ops Notification Dispatch Service
Outbound email/SMS/push, unified — delivery records in Postgres, a Redis-backed queue, and a worker already wired in for async, retry-safe sending. The opposite direction from the Webhook Receiver recipe (that's inbound events; this is notifications you're sending out).
Loads this recipe straight into the wizard — every setting stays editable before you generate anything.
The stack
Install
# pulls this exact recipe straight from the Vault $ npx stacktora install notification-dispatch-service --remote $ stacktora sync # generate the files
What you get
More from the Vault
Email Deliverability & Bounce Management
Bounce, complaint, and suppression-list tracking with a worker processing provider webhooks — distinct from Newsletter/Subscriber Management: that's the list itself, this is keeping your sending reputation intact.
Newsletter & Subscriber List Management
Subscriber lists, campaign sends, and unsubscribe/bounce handling — distinct from both other Notifications recipes: Dispatch is transactional sends, Drip is onboarding sequences, this is an actual mailing list with real subscriber lifecycle.
Onboarding & Drip Campaign Service
Scheduled, multi-step email sequences (day 0, day 3, day 7…) with a worker to send them on time. Distinct from the Notification Dispatch recipe: that's immediate/transactional sends; this is sequences that unfold over days or weeks.
.NET + Postgres + Redis: Fintech-oriented Baseline
A security-conscious starting point for financial and payments-adjacent backends: .NET API, Postgres for ledger/transaction records, and Redis for session and rate-limit state. This is a starting baseline only, not a certified or verified PCI-DSS/regulatory-compliant stack — your own security and compliance review is still required before handling real financial data.