Account

Plans & Limits

Five plans across two sending modes. Every plan uses the same API endpoint, what differs is which sending infrastructure delivers the mail and what caps apply.

Plan comparison

All plans compared
FeatureFree BYOCBYOCManaged StarterManaged GrowthManaged Pro
PriceFree$5 / mo + usage$5 / mo$15 / mo$59 / mo
Sending modeYour AWS SESYour AWS SESShared SESShared SESShared SES
Shared SES sendingSmoke test only: your own address—YesYesYes
Monthly email limit3,000 (both together)20,000 included, up to 1,000,000 *5,00025,000100,000
Recipients per message50 (to takes a string or a list)50 (to takes a string or a list)5 — exactly one in to5 — exactly one in to5 — exactly one in to
Rate limit60 req/min60 req/min60 req/min60 req/min60 req/min
API keysUnlimitedUnlimitedUnlimitedUnlimitedUnlimited
Domain-scoped keysYesYesYesYesYes
Email content storedBodies never; metadata only with email logs on (smoke tests: 14 days)Bodies never; metadata only with email logs on14 days14 days14 days
Email log dashboardOptional, metadata onlyOptional, metadata onlyYesYesYes
Delivery webhooks—Yes, from your own SES eventsYesYesYes
Bounce & complaint handlingTracked, with protection you chooseTracked, with protection you chooseManagedManagedManaged
AWS account requiredYes, for BYOC sendsYesNoNoNo
SupportEmailEmailPriority emailPriority emailPriority email

* $0.10 per 1,000 emails beyond 20,000 and $0.10 per 1,000 logged emails beyond 20,000, under a monthly cap you set. Your own AWS SES daily sending quota also applies, and whichever is lower is the limit you meet first. Only usage while you are on the BYOC plan is charged: Free-plan sends earlier in the month, sends after the plan ends and emails Amazon SES did not accept never are.

How monthly limits work

Monthly counts reset at the start of each calendar month, in UTC. Only accepted sends count, a request that fails validation or authentication is not deducted. Every recipient counts as one send, the way Amazon SES counts them: an email to two to addresses and one cc is three.

Once you reach your plan's limit, further POST /v1/send requests return 429 Too Many Requests with the error code usage_limit_exceeded. Nothing is queued and nothing is partially sent, the response is immediate.

429: limit reached
{
  "success": false,
  "error":   "usage_limit_exceeded",
  "detail":  "Monthly limit of 25,000 emails reached for this calendar month (UTC). Counts reset on the first of the month. Plans and limits: https://docs.sendfleet.net/plans. Upgrade: https://sendfleet.net/pricing/"
}

Rate limits

Rate limits are enforced per API key at 60 requests per minute on every plan, and are entirely separate from the monthly quota. Both can produce a 429, so check the error field to tell them apart: a rate-limit 429 is worth retrying, a quota 429 is not.

Rate limit
ScopeLimitOn breach
Per API key, all plans60 requests / minute429 Too Many Requests

Note that GET /v1/me shares this budget, so a polling health check eats into your sending headroom.

BYOC plans and your SES quota

On Free BYOC and BYOC, mail is delivered by your own AWS SES account. SendFleet enforces a monthly cap on both — 3,000 emails on Free BYOC, and on the paid BYOC plan the cap you set (default 100,000, up to 1,000,000) — and your own SES account sets a daily limit on top of that:

AWS SES sending quotas
SES statusDaily limitNotes
Sandbox (default for new accounts)200 emails/dayVerified recipients only. Production access is granted per region; SendFleet can file the request with AWS for you from Dashboard → AWS.
Production accessSet by AWS, commonly 50,000+/daySendFleet requests it for you, or request it from AWS (opens in a new tab)

On Free BYOC the 3,000 is one monthly counter, whichever path the send takes: Shared smoke tests and BYOC sends count together. The smoke test's rules are on the Shared SES page.

Deleting your account does not reset the 3,000. Sign up again with the same address in the same calendar month (UTC), where letter case, a +tag and, for Gmail, dots do not make it a different address, and the new account continues from the sends the deleted one had used. The next month starts at zero.

Managed plan onboarding

Managed Starter, Growth, and Pro all send through SendFleet's managed infrastructure. There is no approval queue, but sending stays blocked until your domain passes both DNS checks.

  1. Subscribe to a Managed plan

    Go to Dashboard → Billing and choose Managed Starter, Managed Growth, or Managed Pro. Checkout requires a verified account email.
  2. Verify a Shared SES domain

    Add your domain, publish both ownership TXT records and all three DKIM CNAMEs, then run both checks in the dashboard. API sending is enabled only once both pass.

Changing plans

Plan changes apply as soon as the change is confirmed, usually within seconds, and certainly before your next request. Upgrades are prorated: you are charged only for the remaining days in the period you have already paid for, and your new limit is available immediately.

To change plan, go to Dashboard → Billing. Billing is handled through our payment processor, no invoices to chase or bank transfers to arrange.

Sending-quality protection on Shared SES

SendFleet monitors bounce and complaint activity on Shared SES to protect deliverability. Keep recipient lists accurate, send only expected mail and promptly remove addresses that bounce or complain.

What is measured
SignalHow it is judged
Hard bouncesRemove permanently undeliverable addresses from your application.
Spam complaintsStop sending to recipients who report your mail as spam.
Severe abuseFraud, malware or policy violations can result in immediate suspension.

Sending-quality thresholds are not published. Use delivery webhooks and dashboard logs to identify and resolve problems before they affect sending.

A first sending-quality breach normally pauses sending for 24 hours without changing your subscription. A repeat breach results in suspension and ends your subscription. Severe abuse and a spam complaint on a free-plan Shared smoke test can cause immediate suspension. Dashboard access remains available. See Suppression & Suspension for the restrictions and support review process.

Frequently asked questions

Quota resets, the BYOC monthly limit, and what happens at the limit.

When does my SendFleet monthly email quota reset?
Monthly email counts reset at the start of each UTC calendar month. Failed sends are not deducted from your quota — only messages that were successfully queued are counted.
Does the BYOC plan have an email limit?
Yes. The BYOC plan is $5 a month with 20,000 emails and 20,000 logged emails included each calendar month (UTC), then $0.10 per 1,000 emails sent and $0.10 per 1,000 emails logged (logging is only charged while email logs are on). Sending stops at the monthly cap you set on Dashboard → AWS, 100,000 by default and up to 1,000,000. Your own AWS SES production quota also applies, and whichever is lower is the limit you meet first. If you need more than 1,000,000 a month, email support@sendfleet.net with your volume.
Do Managed plans require manual approval?
No. Verify your account email, activate a Managed plan and you are good to go. Domain ownership and DKIM verification are still required before you can send.
What happens if I go over my monthly email limit?
Sends beyond the limit return HTTP 429 with the error code usage_limit_exceeded and are not queued. Retrying does not help. Upgrade to a plan with a larger allowance, which takes effect immediately, or wait for the quota to reset at the start of the next UTC calendar month. On BYOC the limit is the monthly cap you set, which you can raise in Dashboard → AWS. BYOC has the largest allowance, up to 1,000,000 a month; above that, email support@sendfleet.net.