Policies decide where each event goes.
Business events map to channels, templates, and binding sets without hardcoding provider behavior inside the upstream service.
Self-hosted notification control plane
One control plane for every notification flow.
NotifyHub centralizes templates, providers, routing, callbacks, retries, and observability so upstream services can stay simple and generic.
Why it exists
Built for teams that need control without ceremony.
Upstream systems send canonical requests. NotifyHub owns the delivery mechanics, provider logic, and the long tail of notification operations.
Delivery status returns as normalized lifecycle events.
Provider callbacks update state in the control plane and can be forwarded to subscribed systems as durable webhooks.
Built to behave like infrastructure, not a point integration.
Retries, health, and observability are first-class, so the platform remains predictable as volume grows.
Docs
Start with the pieces people actually need.
The docs are written as a product site: getting started, architecture, providers, deployment, and operations all live in distinct paths.
01
Getting started
Client onboarding, auth headers, and the order to create initial records.
02Architecture
The runtime shape, data flow, and model relationships behind the platform.
03Channel guide
End-to-end send, callback, and reply behavior for each supported channel.
04Deployment
How to run the stack locally and ship it to Kubernetes or AWS.
05Admin API
How to create provider accounts, templates, policies, and callback routes.
Flow
From request to delivery, the path stays narrow.
1
Client sends a canonical request
The client posts a single notification intent, not a provider-specific payload.
2
NotifyHub resolves policy
Templates, preferences, bindings, and provider accounts are resolved centrally.
3
Connectors dispatch the message
Provider credentials stay inside the platform boundary and are resolved at runtime.
4
Callbacks update the record
Status changes and replies return as normalized events the client can consume.