FREE GROWTH ROADMAP · NOT AVAILABLE YET
Up to 50,000 sends per day.
That is our planned maximum free tier for customers with a pristine sending history. 50,000/day is not available today. It requires gradual warm-up, current evidence, human review and provisioned capacity. There is no guaranteed upgrade or fixed graduation date.
Read the stages and review policy ↗
What you can use today
New accounts start at 100 recipient reservations per UTC day and 3,000 per calendar month. New sending domains start at 100 per day and hour. Existing accounts and domains keep their saved limits; your dashboard and usage API show your actual account allowance.
Current shared delivery budgetThe whole platform shares 1,000 delivery attempts per day, including 50 reserved for identity mail. Attempts are at least 3 seconds apart, and retries use capacity. Account allowances are ceilings, not reserved throughput or promises of delivery.
How do increases work?
Increases require a human review of real, wanted transactional sending, authentication, delivery and complaint evidence, and available capacity. Missing or stale data does not establish a clean history. Increasing a number in the dashboard does not create delivery capacity. See the proposed growth stages.
What does Free for Life mean?
The plan stays $0 per month, with no trial expiry, automatic subscription charge or paid overage. Published usage limits and sending safeguards apply. The name describes the price; it does not promise unlimited sending.
What counts toward the limit?
Recipient reservations count when accepted, including messages later canceled or failed. Daily and monthly limits reset on UTC calendar boundaries. Account quota returns 429 when exhausted; unavailable delivery capacity can return 503 before acceptance without spending quota. A 202 response means queued; inspect delivery logs for later outcomes.
What can I send?
Approved transactional emails tied to fresh, real customer events. Marketing campaigns, bulk recipients, Cc/Bcc, arbitrary body overrides, attachments and custom headers are outside the current sending contract. Financial receipts and paid orders use Stripe verification; other supported events use a signed application callback.
What happens if quality drops?
Delivery complaints and other safety checks can hold sending. Higher limits are not permanent permission to bypass verification, suppressions, domain pacing or account review.