> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Account Quotas And Limits

> Understanding rate limits, daily quotas, monthly sending tiers, and burst allowances.

# Account Quotas and Limits

Mailofly enforces quotas to ensure infrastructure stability, protect IP reputations, and prevent accidental burst sending.

***

## Plan Quotas

Monthly public catalog checked **November 3, 2026**. Workspace entitlements and the [pricing page](https://www.mailofly.com/pricing) determine your current allowance. Marketing contact plans are separate.

| Transactional plan | Monthly price | Included monthly emails |
| :- | :- | :- |
| **Free** | \$0 | 3,000 |
| **Pro 50K** | \$20 | 50,000 |
| **Pro 100K** | \$29 | 100,000 |
| **Scale 100K** | \$75 | 100,000 |
| **Scale higher volumes** | See current pricing | 200,000–2,500,000 |
| **Enterprise** | By agreement | By agreement |

Free has a 100-email daily workspace limit. API request rates and provider restrictions are separate from monthly email allowances. Dedicated IP arrangements are not implied by the volumes above.

***

## Handling Over-Quota Requests

* **Rate Limit (HTTP 429)**: If your application exceeds the per-second API burst rate, Mailofly returns a `429 Too Many Requests` header with a `Retry-After` timestamp. Use an exponential backoff retry mechanism.
* **Monthly Quota Exceeded**: You will receive email notifications when you reach 80% and 100% of your plan allowance. You can enable automatic overage protection in **Billing Settings** to avoid delivery interruption.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.