The Universal Communication Hub.
Stop duct-taping APIs together just to send an alert. Aeion Notifications is a unified routing engine built natively into your OS. It intercepts system events, checks user preferences, respects quiet hours, and dispatches perfectly templated messages across In-App, Email, SMS, and Push channels automatically — with 24 built-in transactional handlers covering every lifecycle event.
Total Notification Orchestration
Smart Channel Routing
Don't spam your users. The engine evaluates notification priority. A `transactional` receipt might just trigger an In-App badge, while an `urgent` security alert blasts to Email, SMS, and Push simultaneously until acknowledged.
Cross-Platform Push
Engage users outside the app. The system handles all the cryptographic VAPID key exchange required for Web Push, and natively integrates with Apple APNS and Firebase FCM for iOS and Android delivery.
User Preference Center
Empower your customers. The native Next.js portal component allows users to define exact granular preferences—"Email me for Marketing, but only Push for Social Mentions," with localized timezone Quiet Hours and frequency caps.
Priority Escalation & Quiet Hours
Non-urgent notifications triggered at 2 AM are automatically queued and held until the user's defined "active window" (e.g., 8:00 AM). However, `urgent` alerts (security breach, payment failure, SLA breach) bypass all filters immediately.
Unified In-App Inbox
Provide a consumer-grade experience. The system keeps every notification and its read/unread state in sync in real-time across all open browser tabs.
Zero-Code Event Triggers
The engine listens to the platform's internal event bus. When the Commerce module emits `commerce.order.shipped`, the Notification Engine intercepts it, fetches the matching template, and dispatches it automatically without writing a single line of API logic.
What Ships in Aeion Notifications
Transactional email library
24 lifecycle events already have a working email behind them — HTML templates, CSS-inlined responsive design, mobile-optimized at 580px — so a new signup or a shipped order never goes uncommunicated while someone gets around to writing the template.
Unified send API
One interface handles preference lookup, channel selection per recipient, and queue management with retry — so triggering a notification is one call regardless of whether it ends up as an email, a push, or all four channels at once.
5 delivery channels, one provider interface
Email, SMS, push, webhook, and in-app all register through the same interface, so adding a sixth channel later doesn't mean forking the routing logic that already works for the other five.
Push (web + mobile)
FCM and APNs are wired in with subscription management, push campaigns, and topic broadcasts — reach users on web, iOS, and Android from the same call, no separate vendor integration per platform.
Webhook delivery
Signed payloads with exponential-backoff retry and delivery confirmation, so a Slack or Teams integration doesn't quietly drop messages the first time the receiving end hiccups.
User preferences
Per-channel opt-in/opt-out, quiet hours, and frequency caps give customers real control — without a preference change ever requiring an engineer.
SMS via Twilio
GSM-7 to UCS-2 character handling, billable-segment counting, and templated body merging happen automatically, so an emoji in a template doesn't silently triple your per-message Twilio bill.
REST surface
Notifications, preferences, templates, delivery logs, and one-click unsubscribe are all standard endpoints — nothing about the engine is a black box you have to reverse-engineer.
24 Built-In Transactional Email Handlers
Every critical user lifecycle event ships with a baseline email handler that fires regardless of whether a custom template is configured. The platform never silently drops a critical communication.
Cross-Platform Push — Web + iOS + Android
Native push delivery across every surface where your users live. No Pusher subscription, no OneSignal vendor lock-in.
SMS via Twilio — Character-Aware Routing
SMS isn't just a short email. Aeion's SMS provider handles the messy reality of GSM-7 encoding, multi-part concatenation, and Unicode fallback automatically.
User Preferences + Quiet Hours
Every notification respects a per-user preference graph. No third-party preference SaaS needed.
Template Centralization
Visual Template Library
Marketing and Operations teams can manage transactional emails without bugging developers. Create, edit, and translate HTML templates natively in the Admin UI.
Dynamic Context Variables
Templates support Handlebars-style injection (`{{user.firstName}}`). The engine automatically maps the triggering event's data into the template variables at runtime.
Delivery Analytics
Every dispatch attempt is tracked — Sent, Delivered, Opened, Clicked, Bounced, Provider Error Codes. Real-time aggregate metrics + per-user audit trail.
Multi-Language Support
Templates can be localized per locale via the Localization module. Users get notifications in their preferred language automatically.
CTO / DevOps-buyer questions
Those are vendor-hosted SaaS sitting outside your stack. You pay per send, suffer API latency, and your customer preference data lives in their database. Aeion Notifications runs *inside* your OS — same database, same auth, same audit log. SendGrid is the SMTP relay; Aeion is the orchestrator. We replace Novu/Courier; we use SendGrid (or any other provider) as the bare delivery layer.
Email: SendGrid, Mailgun, Postmark, AWS SES, generic SMTP, plus Bring Your Own Infrastructure — all included free. SMS: Twilio (more coming). Push: VAPID Web Push, APNs (iOS), FCM (Android). Webhooks: Slack, Teams, Discord, generic. All swappable per-tenant.
Real-time. Your preference settings are the single source of truth — when a user updates their preference center, the next notification check picks it up immediately. No cache invalidation games, no stale state.
Yes. Every notification carries the user's opt-in record, every email has a one-click unsubscribe link, SMS sends include "Reply STOP" instructions, and a regulator-friendly audit trail is kept for every send. Marketing-category notifications respect double-opt-in flows when enabled.
Unlimited provider fallback chains are included free. Configure SendGrid primary → AWS SES secondary; if primary returns 5xx, the engine automatically retries on secondary. Delivery is best-effort guaranteed within retry budget.
Yes. The 24 built-in handlers are *defaults* — define your own template for the same event and the system uses yours instead. The default handler is the safety net so a missing template never silently drops a critical communication.
Campaign sends go through a dedicated bulk-send pipeline with per-tenant rate limiting tuned to your provider's burst caps (SendGrid: 100/sec, Mailgun: variable, etc.). Every send carries an idempotency key derived from the campaign + recipient so retries never double-send.
Every send emits Prometheus counters (enqueued/processed/dlq) tagged by tenant + channel + provider. The admin UI surfaces a per-channel dashboard: success rates, latency P50/P95/P99, bounce reasons, top error codes. Plus full delivery audit log per recipient.