Transactional email limits and allowance
Every hosting plan includes monthly email allowance. Extra packs cover busy months.
Allowance resets on your subscription anniversary. There is no automatic top-up.
- Beta
- Sending API
- SMTP relay
Allowance
Included emails
| Plan | Included each billing cycle |
|---|---|
| Hobby | 5,000 emails |
| Starter | 25,000 emails |
| Pro | 100,000 emails |
- At 90% of allowance, Eza warns Organisation Owners.
- Eza allows one 10% grace period each billing cycle.
- After allowance, grace and purchased packs run out, sends return
email_limit_reached.
Email packs
Extra email packs
- An extra 20,000-email pack costs KES 500.
- Buy packs in Billing → Add-ons or with the CLI.
- Eza sends an M-Pesa prompt only after you start the Pay action. Credits become available after M-Pesa payment confirms.
- Packs are used after the plan allowance.
- A pack expires at the end of the billing cycle after the one in which you bought it.
- No automatic email top-up exists.
Rate limits
Rate limits
| Limit | Value |
|---|---|
| API requests | 10 per second per Organisation |
| Batch send | Up to 100 emails per request |
| SMTP connections | 10 at once per Organisation |
For the first 14 days, Organisations receive one-quarter of standard sending limits.
Over-rate-limit requests return HTTP 429 with a Retry-After header.
Messages
Message size and retention
- Attachments are supported up to 10 MB per message after encoding.
- Executable and similar high-risk file types are blocked.
- Message bodies and attachments are deleted after 72 hours.
- Delivery records remain available for 30 days.
Suppression
Bounce and complaint suppression
- Hard bounces are suppressed for the Organisation for 90 days.
- Remove up to 20 hard-bounce suppressions per day through the dashboard or API.
- Complaint suppression remains until removed. Removal needs a support request with evidence that the recipient agreed to receive the message.
Transactional email
