Our Mission
Enbbox exists to solve one of the most common — and most underestimated — problems in software: notifications.
Every application needs them. Few get them right. Building a reliable, multi-channel notification system from scratch means integrating dozens of providers, managing subscriber preferences, handling delivery failures, building visual workflow editors, and maintaining it all as your product scales.
We believe notifications should be infrastructure, not a project.
What We Build
Enbbox is a complete notification infrastructure platform that gives development teams everything they need:
| Capability | Description |
|---|---|
| In-App Inbox | Drop-in React component for real-time in-app notifications |
| Multi-Channel Delivery | Email, SMS, Push, In-App, and Chat from a single API |
| Workflow Engine | Visual builder for complex notification flows with conditions, delays, and digests |
| 21+ Provider Integrations | SendGrid, Twilio, FCM, APNS, Slack, and more — swap providers without code changes |
| Framework SDK | Code-first workflow definitions with TypeScript and React Email |
| MCP Server | AI-native access — manage your notifications directly from Cursor, Claude Code, or any MCP-compatible IDE |
Our Values
- Developer-first. We build tools we'd want to use ourselves. Type-safe SDKs, comprehensive API docs, and a code-first approach.
- Open standards. We support open protocols (MCP, webhooks) and provide transparent pricing with no vendor lock-in.
- Reliability. Notifications are critical infrastructure. We treat uptime, delivery rates, and data integrity as non-negotiable.
- Simplicity. Start with
<Inbox />— scale to enterprise workflows. The learning curve should be minutes, not days.
The Company
Enbbox is operated by two entities:
- SWYPE FZE — Dubai, UAE
- Digital Services LLC — Batumi, Georgia
Together, we build developer tools and infrastructure products used by teams worldwide.
Get in Touch
- Email: [email protected]
- GitHub: github.com/enbbox
- Documentation: enbbox.com/docs