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

# Team limits

> Review Free hard limits, Pro capacity, and managed sending safeguards.

Free limits are fixed. Pro offers Unlimited\* resource capacity, subject to fair usage and Qubrics admin approval for increases. Provider quotas, safety controls, account health restrictions and managed Amazon SES limits still apply.

## Free limits

| Resource | Starting limit |
| - | - |
| Active teams per account | 1 |
| Domains | 1 |
| Mailboxes | 2 |
| Your own or connected sending accounts | 1 |
| Webhooks | 1 |
| Credentials | 2 |
| Team members | Owner only |

> [!NOTE]
>
> Credentials include manual API keys across all key types and connected apps.
> Pending mailbox credential creation can also reserve capacity until it
> finishes. The **API Keys** page shows both credential classes in that total.

## Free limits are hard

A Free team cannot request a higher resource or managed-sending allowance. To get more capacity, delete an existing resource or upgrade to Pro. The app shows the upgrade path, and the Management API returns an upgrade message for a Free team.

## At the hard limit

Creation is blocked when usage reaches the full limit. A Free team must delete an existing resource or upgrade to Pro.

For credentials, remove enough keys or connected apps to bring usage below the limit before creating another.

API creation requests generate `409 limit_exceeded`. Retrying the same request cannot succeed until capacity is available.

## Pro capacity

The app shows usage and allowance. At 80% usage, select **Request increase** for Qubrics admin review, then request another increase at 80% of the approved allowance. Contact support for advance approval of higher limits to avoid interruptions.

Provider-accepted recipients don't use resource allowances. Provider quotas, API rate limits, safety controls, account health restrictions and managed Amazon SES safeguards still apply on Pro.

## Email volume

Free teams can send to at most 50 accepted recipients per UTC day across all sending routes. A message with one To recipient and two CC recipients counts as three accepted recipients.

Qubrics reserves capacity before accepting the message. Just before a queued message reaches its provider, Qubrics assigns that capacity to the current UTC day. If that day is already full, the queued message waits for the next UTC reset.

In-flight recipients count towards the limit until their provider outcome is known, so concurrent sends cannot cross the cap. A reservation is not a usage charge. Outgoing usage is charged only for provider-accepted recipient occurrences.

When a Free team has no daily capacity left, the HTTP Sending API returns `429 daily_limit_exceeded` before queueing the message. SMTP returns `550 5.7.1 Daily sending limit reached. Upgrade to Pro to continue.` The HTTP response includes `Retry-After` for the next `00:00 UTC` reset. Messages already accepted into the queue wait instead of crossing the new day's limit.

Managed Amazon SES adds these safeguards:

| Plan | Hourly limit | Daily limit | More capacity |
| - | - | - | - |
| Free | 2 accepted recipients | 50 accepted recipients | Upgrade to Pro |
| Pro | No Qubrics speed cap | Team's current daily allowance | Request a review from **Accounts** at 80% usage |

Pro managed sending has no per-second, per-minute or per-hour Qubrics cap. Your team's current daily allowance, approved increases and shared Amazon SES account and regional sending limits still apply.

Your own providers on Pro and Enterprise have no Qubrics sending caps. Any quotas you configure, provider limits and account health controls still apply.

## Related guides

> [card] [Domains](https://sendmux.ai/docs/domains.md)
>
> Add and verify custom domains.

> [card] [Sending accounts](https://sendmux.ai/docs/sending/accounts)
>
> Add providers and review managed sending limits.

> [card] [Webhooks](https://sendmux.ai/docs/webhooks/setup.md)
>
> Subscribe to delivery and mailbox events.

> [card] [API keys](https://sendmux.ai/docs/account/api-keys.md)
>
> Create, rotate, and revoke scoped keys.

> [card] [API errors](https://sendmux.ai/docs/api/errors.md)
>
> Handle `limit_exceeded` responses in API clients.


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