Should you build your own Brevo?
Send a low-volume newsletter and transactional messages with clear consent records
The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Brevo, send a low-volume newsletter and transactional messages with clear consent records. The hard boundary is deliverability infrastructure, multichannel messaging, crm, automation, and support, plus deliverability, growth network, and integrations.
ENOriginal research content in English. Original prompt preserved in English.
Build a personal replacement for Brevo in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Amazon SES; do not offer alternative stacks.
The core loop is: collect subscribers with clear consent records, compose and send a low-volume newsletter and transactional messages, publish a web archive, and report basic delivery and click events.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Implement subscriber import, double opt-in, unsubscribe, suppression, tags, and consent timestamps.
Create a Markdown campaign editor with HTML and plain-text previews.
Queue sends through SES with retries, rate limits, idempotency, and resumable batches.
Process delivery, bounce, complaint, open, and click webhooks without logging message content.
Publish a simple issue archive and subscriber preference page.
Add test sends, seed-list checks, DNS setup guidance, exports, and backups.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out a newsletter recommendation marketplace.
Deliberately leave out ad sales and payment infrastructure.
Deliberately leave out complex lifecycle automation and enterprise deliverability support.
Finish by running the tests and listing the exact commands used.The prompt opens pre-filled in your agent. Review it before running. · this prompt is generated from the build plan · improve it via PR
What would building your own look like?
Collect subscribers with clear consent records, compose and send a low-volume newsletter and transactional messages, publish a web archive, and report basic delivery and click events.
What you will need
- Amazon SES account
- verified sending domain
- PostgreSQL
- public HTTPS deploy target
- DNS access
People still pay for Brevo because newsletter operators pay for inbox placement, growth mechanics, and operational confidence on publication day. The recurring cost buys DNS authentication, reputation, bounces, complaints, unsubscribe compliance, templates, queues, analytics, backups, and support, not just the visible interface.
xdeliverability infrastructure, multichannel messaging, CRM, automation, and support
xinbox-placement expertise
xadvanced automations
xcommerce integrations
xrecommendation and ad networks
Prefer something ready-made?
listmonkFast campaigns plus a transactional API and explicit subscriber states; the visual polish is utilitarian.Open source↗
PlunkTransactional and campaign email with workflows; self-hosting is free, sending is not magic.Open source↗
NotifuseCampaigns, transactional API and subscription records in one compose stack; delivery still needs an SMTP provider.Open source↗View all 6 alternatives to Brevo →· Licença, instalação e limitações em cada alternativa.
How much does Brevo cost?
- Monthly billing
- $9/mo$9/mo
- Per year
- $108/yr$108/yr
- Annual billing
- $96.96/yr10% cheaper than paying monthly
- On a Brazilian card, with 3.5% IOF
- R$47.03/moR$507/yr
Saved to My list. You will see a notice on this site when the price changes.
You complete the purchase on Brevo’s site. Vibe Radar does not handle payments.
| Plan | Monthly | Annual (per month) | What is included |
|---|---|---|---|
| free | $0/workspace | $0/workspace | 300 email sends/day, up to 100,000 stored contacts, 1 user, automation up to 2,000 contacts, basic reporting. |
| starter | $9/workspace≈ $9 | $8.08/workspace≈ $8.08 | Starts at 5,000 monthly emails; no daily send limit; contact tiers from 500 to 500,000 depending email volume. |
| standard | $18/workspace≈ $18 | $16.17/workspace≈ $16.17 | Starts at 5,000 monthly emails; up to 3 user seats via add-on, 1 landing page, unlimited automation contacts, A/B testing, AI send time. |
| professional | $499/workspace≈ $499 | $449.10/workspace≈ $449 | Starts at 150,000 monthly emails; up to 2,000,000 contacts, 10 user seats, 10 landing pages, 1 custom object. |
| enterprise | custom | - | Custom volume, unlimited contacts, unlimited seats, 40,000 push target limit, 1 dedicated IP included, SAML, SLA, CSM. |
Free tier$0; 300 emails/day, up to 100,000 contacts, 1 user, automation up to 2,000 contacts.
Billing termsmonthly + yearly (-10%); yearly paid upfront; plan credits renew monthly
Additional costsUnused monthly email credits expire; paid contact overages can trigger auto-upgrade; remove-logo add-on $9/mo, extra Standard seats $9/mo, dedicated IP $251/year, SAML $324/mo, SMS/WhatsApp priced separately.
verified 2026-10-20 · source ↗
Is it cheaper to build or buy Brevo?
Adjust the numbers: hours to build, your hourly rate, running costs and the subscription price.
Over 24 months, subscribing is cheaper.
Starting hours estimated from the analysis (multi-day). Does not price what you give up (support, integrations, security).
Can I rebuild Brevo?
Kinda. The core of Brevo is buildable in a weekend with the prompt on this page, but there are real gaps: deliverability infrastructure, multichannel messaging, CRM, automation, and support, inbox-placement expertise. Read the honest list above before committing.
How much does Brevo cost?
Brevo costs about $9/mo (Starter, checked 10/20/2026), which is $96.96 per year.
What do I lose by replacing Brevo?
Honestly: deliverability infrastructure, multichannel messaging, CRM, automation, and support; inbox-placement expertise; advanced automations; commerce integrations; recommendation and ad networks. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Brevo?
Yes: listmonk (Fast campaigns plus a transactional API and explicit subscriber states; the visual polish is utilitarian.) Plunk (Transactional and campaign email with workflows; self-hosting is free, sending is not magic.) Notifuse (Campaigns, transactional API and subscription records in one compose stack; delivery still needs an SMTP provider.) All 6 curated free alternatives are at https://viberadar.si/brevo/alternatives. The prompt is for when you want it exactly your way.