Docs/Plans & Limits
Account

Plans & Limits

SendFleet offers four plans across two infrastructure modes. Every plan shares the same API endpoint - the difference is whose AWS account delivers the mail, and what caps apply.

Plan comparison

FeatureStarterBYOCGrowthPro
PriceFree$9 / mo$15 / mo$59 / mo
InfrastructureYour AWS SESYour AWS SESSendFleet SESSendFleet SES
Monthly email limit50Unlimited *25,000100,000
API keysUnlimitedUnlimitedUnlimitedUnlimited
Email content storedNeverNever90 days90 days
Email log dashboard--
Webhook events--
Bounce & complaint handlingYour SESYour SES✓ Managed✓ Managed
Manual approval requiredNoNoYesYes
SupportEmailPriority emailPriority emailPriority + SLA

* BYOC unlimited = no SendFleet cap. Your AWS SES daily send quota applies.

How monthly limits work

Monthly email counts reset at the start of each calendar month (UTC).

When you reach your plan's limit, further POST /api/send/ requests return 429 Too Many Requests with error code usage_limit_exceeded. No emails are queued or partially sent - the response is immediate.

429 - limit reached
{
  "success": false,
  "error":   "usage_limit_exceeded",
  "detail":  "Monthly limit of 25,000 emails reached. Upgrade your plan to continue sending."
}
Usage counts are cached for up to 30 seconds to reduce DB load on the hot send path. A small burst of sends after hitting the limit is theoretically possible in rare high-concurrency scenarios, but billing enforcement will catch any overage.

Rate limits

Rate limits are enforced per API key, per minute, using a sliding window. Limits reset continuously.

PlanLimitHTTP status on breach
Starter / BYOC / Growth / Pro60 requests / minute429 Too Many Requests

BYOC plan - your SES quota

On Starter and BYOC plans, emails are dispatched through your own AWS SES account. SendFleet enforces the Starter plan's 50-email cap but does not otherwise impose a sending ceiling on the BYOC plan. Your actual limit is determined by AWS:

SES statusDaily limitNotes
Sandbox (default)200 emails/dayOnly to verified addresses. SendFleet rejects sandbox accounts at BYOC setup.
Production accessSet by AWS (typically 50,000+/day)Request at AWS docs →
SendFleet validates that your SES account is out of sandbox mode during the BYOC IAM role setup. If your quota is ≤ 200 emails/day, the validation will fail with a clear error message asking you to request production access from AWS first.

Shared SES - manual verification

Growth and Pro plans send via SendFleet's managed AWS SES infrastructure. Because all customers on these plans share the same sending reputation, we manually review every account before granting access.

1
Subscribe to Growth or Pro
You can subscribe before being approved, but sending will be blocked until approval is granted.
2
Submit a verification request
From your dashboard, go to Dashboard → Request Verification. Describe your use case, company, and expected volume. We review within 1–2 business days.
3
Approval granted - sending unlocked
You'll receive an email confirmation. The restriction lifts immediately upon approval - no action needed on your side.

Upgrading plans

Plan upgrades take effect immediately. If you switch from Starter/BYOC to Growth/Pro mid-month, your monthly counter resets and you immediately gain access to the higher limit. Downgrades take effect at the end of the current billing period.

To upgrade, go to Dashboard → Billing. All billing is handled via Paddle - no invoice management or bank transfers required.

Abuse thresholds (Shared SES)

For accounts on Shared SES (Growth/Pro), we continuously monitor bounce and complaint rates over a rolling 7-day window. If your rates breach the thresholds below, sending is automatically suspended to protect the shared pool's deliverability.

MetricThresholdWindowMinimum volume
Bounce rate≥ 4%7 days50 sends
Complaint rate≥ 0.08%7 days50 sends

Suspension does not lock you out of the dashboard - you can still view your logs and contact support. To be reinstated, email support@sendfleet.net. See Suppression & Suspension → for full details.