Introduction
What is EmBoux?
Section titled “What is EmBoux?”EmBoux is an Inbound/Outbound Email Orchestration Engine built exclusively for B2B SaaS platforms and agencies that manage email for multiple clients.
It’s not a transactional email service like Mailgun or SendGrid. It’s the plumbing layer between your application and a fully managed mail server, giving you programmatic control over the entire email infrastructure through a REST API.
Who is EmBoux for?
Section titled “Who is EmBoux for?”- SaaS platforms that provision email domains for customers as part of their product
- Agencies managing email infrastructure across dozens or hundreds of client domains
- ERP integrators (especially Odoo) automating email setup as part of business workflows
- DevOps teams that want infrastructure-as-code for email — no cPanel, no Plesk
The Core Difference
Section titled “The Core Difference”Traditional providers like Mailgun or SendGrid are designed for one company sending its own emails. They bolt on multi-tenancy as an afterthought, charge you per email, and delete your logs after a week.
EmBoux is designed from the ground up for the reseller model:
| What you need | Traditional Providers | EmBoux |
|---|---|---|
| Isolate Client A from Client B | Manual subaccounts | Automatic — each API key is scoped to a partner |
| Stop a hacked client from sending spam | They send it, you pay | Hard caps enforced at SMTP level |
| Bill clients for their usage | Logs deleted after 3-7 days | Persistent counters per domain |
| Freeze service for non-payment | Open a support ticket | One API call, data preserved |
| Control storage per mailbox | Not applicable | Server-level quota enforcement |
Architecture
Section titled “Architecture”Your App → EmBoux API → EmBoux Mail Server → Email delivery (REST) (IMAP/SMTP)When you create a domain or mailbox via the API, the mail server picks it up immediately — no config reload, no propagation delay.
Multi-Tenancy Model
Section titled “Multi-Tenancy Model”Every API key belongs to a partner (your client). Resources are automatically scoped:
- A partner can only see and manage their own domains, mailboxes, and aliases
- Quotas are enforced per key: domains allowed, mailboxes per domain, storage per mailbox
- A master key has full access and manages the API keys themselves
- Partners can have multiple keys with optional expiration dates — perfect for giving contractors limited access
What You Can Control
Section titled “What You Can Control”| Resource | Operations | Enforcement |
|---|---|---|
| Domains | Create, list, delete, suspend, activate | Domain count quota per partner |
| Mailboxes | Create, list, update password, delete | Mailbox count per domain, storage quota (MB) |
| Aliases | Create, list, delete (including catch-all) | Alias count per mailbox |
| Retention | Get/set per domain | Auto-purge cron deletes expired emails daily |
| Transfer | Get/set per domain | Monthly bandwidth cap per domain |
| API Keys | Create, update, delete, usage reporting | Multiple keys per partner, optional expiration |
Next Steps
Section titled “Next Steps”- Quick Start — Create your first domain and mailbox in 2 minutes
- Authentication — Understand token types, quotas, and multi-key support
- API Reference — Full endpoint documentation