- Free allowance
- 300 email sends per day with no time limit; 100,000 contacts stored
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, phone unknown
- Binding limit
- request-rate300 sends per day, resetting daily, with no carry-over; a campaign to more than 300 recipients delivers to 300 that day and needs a manual requeue, so the daily send counter is the campaign's limit too
- Evidence
- documented14 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-30checked 2026-10-30 (live); stale on 2026-11-30
| Free tier | 300 email sends per day with no time limit; 100,000 contacts stored unit requests; metered on request-count; Every email sent from the Free plan carries the Sent with Brevo sticker; up to 2,000 unique contacts can enter active automations; one user. Once the 300 daily sends are used, no campaign can be scheduled for the next day. The Free plan's limits page names no restriction on recipients. |
|---|
| Price | none stated |
|---|
| Limits | - request-rate (binding) 300 sends per day, resetting daily, with no carry-over source
- request-rate (binding) a campaign to more than 300 recipients delivers to 300 that day and needs a manual requeue, so the daily send counter is the campaign's limit too source
- write-gated transactional sending over SMTP or the API needs a separate activation by the vendor, requested by a support ticket from the account, before the first send; the time it takes is unverified: behind a sign-up source
counts of things, not rates, so no vocabulary kind names them: 100,000 contacts stored on the free plan. The campaign entry is a rate: the same 300-a-day counter is what a campaign meets, so it stays request-rate |
|---|
| Binding | request-rate 300/day. The campaign path is the trap: a 1,000-contact list takes four days. |
|---|
| Identity | email Signup asks for an email and a password, or a Google or Apple sign-in, with no card; the account then verifies the email and asks for basic business information. Whether a mobile phone number with an SMS code is also required is unverified: behind a sign-up; users on the vendor's community forum report a phone number and SMS code step during registration. A sender on a free domain such as gmail.com cannot be authenticated, and the vendor states that mail from a free address is rejected or filtered to spam, so delivery needs a domain the sender controls. |
|---|
| Egress | not applicable: an outbound sender |
|---|
| Per-object cap | not applicable: a send count rather than an object |
|---|
| Retention | unused sends do not roll over |
|---|
| Interface | rest, cli the SMTP relay and the transactional API; SMTP is the documented path |
|---|
| Tooling | any SMTP client, or the Brevo API |
|---|
| Composes with | the highest card-free daily cap found: 300/day, which is three times Resend's. It is the outbound half of the inbound-plus-outbound chain and its scarce link is the day. |
|---|
| Reliability | once the daily limit is hit, up to 1,000 transactional emails are held in a retry queue and anything beyond that is not delivered |
|---|
| Notes | The help page states the campaign behaviour explicitly, which is why the 300/day figure is not the whole answer for a marketing send. |
|---|
| Evidence note | documented no message was sent, so no delivery is proved. The submission path was probed: smtp-relay.brevo.com:587 answered 250, STARTTLS completed against the system trust store, and AUTH LOGIN returned 334 |
|---|
| Parsed numbers | |
|---|