Workspace governed delivery
Reliable notification infrastructure for every product channel
Connect provider accounts, issue API keys per platform integration, and route Email, SMS, WhatsApp, WebSocket, MQTT, and chat notifications from one workspace-governed API.
Interactive routing lab
Try a channel route
Selected channel
Transactional and operational email through the provider account each user connects.
Delivery path
Async + fallbackCustomer web app
api_live_web
Email + WhatsApp fallback
Provider connections ready
Operations console
api_ops_console
WebSocket + MQTT events
Platform integrations active
Mobile checkout
api_mobile_checkout
SMS + localized Email
Audit logging enabled
Product foundation
One notification system for users, teams, providers, and channels
Built around workspaces, subscription limits, provider credentials, platform API keys, and multilingual notification payloads.
User and workspace management
Individual users and team/company accounts can manage profiles, members, roles, linked accounts, and secure access from the same system.
Provider connections
Attach SMTP, Mailgun, SendGrid, Mailtrap, SMS, WhatsApp Business API, WebSocket, and MQTT providers per workspace.
Platform integrations
Create separate API keys for each product, environment, or integration so access can be rotated and audited independently.
Localized notification payloads
Send content with locale and fallback fields so one request can support English, Traditional Chinese, and additional registered languages.
Usage and subscription controls
Pricing and limits can reflect connected channels, platform integrations, provider accounts, and linked team accounts.
Delivery visibility
Use audit logs, provider test sends, delivery status, and analytics to operate notification routing with confidence.
Channel coverage
Bring your own providers without changing product code
Provider credentials stay workspace-owned while application code talks to one consistent API.
Channel mix
Adjust the example blend between low-touch automation and high-touch recovery.
Integration workflow
A predictable path from workspace setup to delivery monitoring
Create workspace
Start as an individual user or create a team/company workspace with member and linked-account controls.
Connect providers
Store provider credentials per channel while keeping secrets owned by the user or workspace.
Bind channels to integrations
Assign routes, fallback channels, and API keys for each platform integration.
Send and observe
Deliver localized payloads through the API or SDKs, then inspect usage, audit logs, and delivery status.
Pricing model
Pricing dimensions match how customers actually integrate
Individual and team/company plans can scale by connected channels, platform integrations, provider connections, and account structure.
Individual user
Base plan + connected channels + platform integrations for builders who manage their own provider accounts.
- Channel connection allowances
- Separate API keys per integration
- Usage limits and delivery history
- Optional provider-specific add-ons
Team / company user
Base plan + connected channels + platform integrations + linked team accounts for organizations with shared workspaces.
- Workspace members and linked accounts
- Provider credentials owned by the company
- Audit controls for sensitive actions
- Team usage and subscription management
Developer experience
SDKs and REST APIs for the platforms your customers use
Keep the REST API as the source of truth, then provide idiomatic SDKs for backend, mobile, web, and cross-platform teams.
Implementation references
Use the existing docs to connect providers, API keys, localized payloads, and delivery flows.
Build notification delivery around your workspace model
Start with provider connections and platform API keys, then scale channels, SDK usage, and team account access as products grow.