Thanks for signing up.
", }), }); ``` **Reloop** ```typescript const reloop = new Reloop({ apiKey: process.env.RELOOP_API_KEY! }); const { response, emailError } = await reloop.mail.send({ from: "AcmeThanks for signing up.
", }); ``` | | Reloop | Brevo | |---|---|---| | Send endpoint | `POST /api/mail/v1/send` | `POST /v3/smtp/email` | | Auth header | `x-api-key` | `api-key` | | Body fields | `from`, `to`, `html`, `reply_to`, `scheduled_at` | `sender`, `to[]`, `htmlContent`, `replyTo`, `scheduledAt` | | Template variables | `{{{first_name}}}` | `{{ params.first_name }}` | | Error format | `message`, `why` and `fix` | `code` and `message` | | React Email | Pass a component or rendered HTML | Rendered HTML | Reloop's error shape is our one strong opinion. When a send fails, the error tells you **why** it failed and **how to fix it**: ```json { "message": "Domain not found", "why": "The domain mail.acme.com was not found or is not authorized for your organization", "fix": "Ensure the domain is registered and verified in your dashboard" } ``` --- ## Campaigns, contacts and automations This is Brevo's home turf. It started as a marketing platform and it shows: - **Brevo** has a drag-and-drop email editor, a large template gallery, landing pages, signup forms, A/B testing, send-time optimization, a sales CRM, live chat, and SMS and WhatsApp campaigns in the same account. - **Reloop** has contacts with custom properties, groups, subscription channels, scheduled broadcast campaigns and **event-triggered automations** with delays, conditions and email steps. Reloop's automations are built to be driven from code. Your app reports an event and every automation listening for it starts for that contact: ```typescript const { automationError } = await reloop.automations.start({ event: "user.signed_up", email: user.email, firstName: user.name, properties: { plan: user.plan }, }); ``` If your marketing team builds journeys visually and wants SMS in the same flow, Brevo is the better fit. If your product team wants onboarding and dunning emails triggered by app events, with the same API and suppression list as your transactional mail, Reloop is. See [welcome sequences that convert](/blog/welcome-email-sequences-that-convert) for a worked example. --- ## Receiving email and agent inboxes **Brevo** supports inbound parsing: mail sent to your domain is posted to your webhook. Storage, threading and replies are up to you. **Reloop** receives mail into **mailboxes**. Messages are stored, threaded, spam-scored with Rspamd, and readable over the API, the [MCP server](/docs/integrations/ai-tools/mcp-server) or IMAP. You can reply in-thread with one call, and there's an `email.received` webhook for push notifications. | | Reloop | Brevo | |---|---|---| | Receive on your domain | Yes | Yes (inbound parsing) | | Stored mailboxes with threads | Yes | No | | Reply in thread via API | Yes | Build it yourself | | MCP access for agents | Yes | No | | IMAP access | Yes | No | That matters if you're building [AI agents that read and reply to email](/blog/build-ai-agent-sends-emails), support inboxes, or reply-to-comment flows. --- ## Deliverability Both handle the fundamentals: SPF and DKIM on your domain, bounce and complaint handling, unsubscribe management and suppression of bad addresses. - **Sending path.** Reloop runs its own MTA (KumoMTA), with per-domain throttling and automatic pauses when bounce or complaint rates spike. Read [how bounce processing works](/blog/email-bounce-processing-automation). - **Dedicated IPs.** Reloop includes one on Growth ($20/mo). On Brevo, dedicated IPs belong to the higher tiers. - **Shared reputation.** Brevo's shared IPs carry a lot of marketing mail. That's fine for most senders, but if your password resets share a pool with newsletters, a dedicated IP or a provider focused on product mail can help. - **Tools.** Reloop ships free [domain reputation](/tools/domain-reputation-checker), [blocklist](/tools/blocklist-checker) and [auth](/tools/auth-checker) checkers. --- ## Self-hosting and lock-in Brevo is hosted-only. Your contacts, templates, logs and suppression lists live in Brevo's database. Reloop is Apache 2.0. Start on Reloop Cloud, move to your own server later with the [one-command installer](/self-host) or [Coolify](/blog/reloop-coolify-setup), and point the SDK's `baseUrl` at your instance. Nothing else in your code changes. Self-hosting isn't free in effort. You own IP reputation, warm-up and uptime. Most teams should start hosted and keep self-hosting as an option. --- ## Where Brevo is the better choice - **Your marketing team runs email without engineers.** The visual builder, templates, forms and landing pages are mature. - **You need SMS, WhatsApp, chat and a CRM** in one bill. - **You send a few hundred emails a day** and the free plan's 300 a day covers you. ## Where Reloop is the better choice - **Developers own your email.** A clean API, SDKs in nine languages, and errors that tell you how to fix them. - **You send real volume.** $10 for 50,000 emails and $20 for 100,000 with a dedicated IP. - **You need inbound mail as real inboxes**, especially for AI agents. - **You want open source or self-hosting** for compliance, data residency or peace of mind. --- ## Switching from Brevo to Reloop 1. **Add your domain in Reloop** and publish the DKIM record (`reloop._domainkey`). Merge `include:reloop.sh` into your existing SPF record. Don't add a second SPF record. 2. **Swap the send call.** Replace `POST /v3/smtp/email` with `reloop.mail.send`, and map `sender` → `from`, `htmlContent` → `html`, `replyTo` → `reply_to`, `scheduledAt` → `scheduled_at`. 3. **Move templates.** Change `{{ params.first_name }}` to `{{{first_name}}}`. 4. **Export contacts** from Brevo as CSV and import them into Reloop, keeping your custom attributes as contact properties. Bring your blocklisted and unsubscribed addresses across so nobody who opted out gets mail. 5. **Rebuild automations** as Reloop automations, and replace Brevo's event tracking with `reloop.automations.start`. 6. **Point webhooks** at a new handler. Reloop events are named `email.delivered`, `email.bounced`, `email.complained` and so on, signed with HMAC-SHA256 in the `Reloop-Signature` header. 7. **Ramp traffic** from 10% to 100% over a week or two, then remove Brevo's DNS records. Our [SendGrid migration guide](/blog/migrating-from-sendgrid) covers the same steps in more detail, including a traffic-split flag and a suppression import script. --- ## FAQ