NotificationHub
Fire notifications on any event — instantly, after a delay, on a recurring schedule, or with smart cancellations if a different event happens first. One template covers email, SMS, push, and in-app, each toggleable per send.
Schedule it. Wait. Cancel if needed.
Four ways to decide when a notification fires, all built into the same template you author once. Pick a mode, configure it, and the hub handles the rest — queues, retries, opt-ins, telemetry.
Event-triggered
Fire the moment an event lands on the bus. Zero latency, zero glue code.
Delayed
Wait a defined duration after the trigger event, then send. One-shot.
Delayed + Cancellable
Same delay, but cancel the send if a different event fires first. Perfect for nudges that shouldn't race the user.
Recurring
Send on an interval — daily digests, weekly summaries, anniversary reminders.
Author once. Toggle channels per send.
Your providers. Our engine.
Bring the SES, Twilio, FCM accounts you already ship with — implement IHubDispatchProvider and mark it [NotificationPublisherProvider], and the engine dispatches through your own. Templates, scheduling, smart cancellations, priority and opt-in respect stay in our hands. The wire stays in yours.
IEmailProvider, ISmsProvider, IPushProvider for anything else.
// Add a delivery provider by implementing the dispatch interface// and marking it with the publisher-provider attribute.[NotificationPublisherProvider("sendgrid", author: "acme", description: "SendGrid email")]public sealed class SendGridDispatchProvider : IHubDispatchProvider{ public Task DispatchNotificationAsync(DispatchMessage message) { // hand the rendered message to your provider's SDK return Task.CompletedTask; }}// The engine still owns: templates, scheduling, smart cancellations,// dispatch priority, and opt-in respect.Send the right thing. At exactly the right moment.
Two send modes
Pre-rendered content sends, or event notifications the hub templates and routes.
Smart cancellations
Drop a queued send when a correlated event arrives — matched by EventTopic + CorrelationId.
Eight channels
SMS, Email, Web, Push, InApp, WhatsApp, Webhook (PublishChannel) — single-select per content send.
Dispatch priority
Separate high- and low-priority queues — transactional sends jump ahead of bulk.
Scheduling
Delayed, recurring, and calendar sends via NotificationScheduleType.
Bring your own delivery
Implement IHubDispatchProvider + [NotificationPublisherProvider] to add a channel or provider.
Built in .NET.
Spoken in every language.
Every NotificationHub module ships as both a NuGet package and an official Docker image — runs on ECS, EKS, Fargate, App Runner, or your laptop. Call its HTTP/gRPC API from Python, Go, Node, Java, Rust, or anything else that speaks the wire.
- ✓Multi-arch images:
amd64+arm64from the same tag - ✓OpenAPI + gRPC reflection enabled out of the box
- ✓Same configuration surface — env vars, Parameter Store, file
Kanject.NotificationHub ships into your AWS, registers itself with one line in Program.cs, and exposes a typed API the rest of your service can use immediately.
Simplify your cloud
journey today.
Join forward-thinking developers and businesses who trust Kanject to eliminate cloud complexity and accelerate innovation.