Quotas & limits
The daily send quota and how it ramps, the automatic bounce and complaint pauses, message size and recipient caps, how long metadata and content are kept, and why receiving is unmetered.
The numbers that bound sending and receiving, in one place. Sending is quota-limited and metered; receiving is neither. The controls here are structural — they cap volume and protect shared reputation automatically, and no one reads your mail.
Early access. Email is being rolled out behind an Org flag. If you don’t see it in the Console, it isn’t enabled for your organization yet.
Daily send quota
Every Org has a daily send quota — the number of messages it can have accepted in a rolling day. It’s charged atomically at accept, so it caps how much a misbehaving sender can push before it’s stopped.
| Default for a new Org | 500 messages/day |
| Ramp | Rises automatically as clean sending history accrues |
| Manual raise | Staff can raise it on request |
| Scope | Per Org, across all its domains and send keys |
Read your current quota and today’s accepted count on the Sending page, or with
lbr email settings. Sending over quota is rejected with 429 and a Retry-After
header (over SMTP, 452 4.5.3). The quota is a ceiling, not a target — staying well
under it keeps your ramp healthy.
Automatic pauses
Two thresholds pause an Org’s sending automatically to protect the shared sending reputation. They’re measured over a trailing 7-day window, with a floor of 50 accepted messages so a tiny sample can’t trip them:
| Trigger | Threshold |
|---|---|
| Bounce rate | above ~5% |
| Complaint rate | above ~0.1% |
While paused, every send is rejected (403, or SMTP 554). Unpausing is a
manual staff action once the cause is understood — the fix is almost always
cleaning your list and your sending practice, which the suppression
list helps with. Keeping both rates low is the single best
thing you can do for deliverability.
Message limits
| Limit | Value |
|---|---|
| Maximum raw message size | 10 MiB |
| Maximum recipients per message | 50 (across to, cc, and bcc) |
A message over the size limit is rejected with 413 (SMTP 552); too many
recipients returns 400 (SMTP 452 4.5.3).
Retention
Two layers of a message are kept for different windows — long enough to debug, support, and redeliver, short enough to keep the data footprint small. Both are fixed product policy, not paid tiers.
| Layer | What it is | Kept for |
|---|---|---|
| Metadata | Addresses, subject, timestamps, delivery events — the log and debug surface | 90 days |
| Content | The full raw message: body, headers, attachments | 30 days |
Fetching a message’s raw content after its 30-day window returns 404; the
metadata remains for the full 90 days. Webhook redelivery is bounded by the same
content window.
Metering
Sending is metered on one dimension, email-sent — a daily count of accepted
outbound messages — priced per 1,000 over a monthly free floor.
Pricing is not yet published. Email is in early access, so sending is metered but not charged: the counts accrue, but there’s no bill for them yet. The per-1,000 rate and the free floor are set before general availability. We’ll confirm before anything is charged.
Receiving is unmetered. Inbound mail is bounded by your send quota’s sibling controls and abuse thresholds, not by price — receiving costs nothing per message.
Where to next
- Sending mail — how accepts, rejects, and events work.
- Suppression — what feeds the bounce and complaint rates.
- Webhooks — delivery events and redelivery within the content window.