SendGrid alternatives: how to choose, by why you're leaving

There is no single answer among SendGrid alternatives. The right one depends on why you are leaving: the pricing model, transactional and marketing split across two systems, inbound replies, agent safety or procurement paperwork. Each reason points to a different checklist.

SendRaven is one option, and it covers four of those five reasons. It is also new (built in 2026), and we say below what we do and don't claim. Use the table to find your reason, then read the matching section.

The short answer: pick by the reason you're leaving

SendRaven fits the first four rows. For procurement, it publishes a DPA and a subprocessor list. SOC 2 is in progress, and there is no data residency. If either is a hard requirement, read the procurement check first.

A few terms, glossed once. DMARC and DKIM are DNS-based checks that show a message really came from the domain it claims. Message-ID is the unique ID every email carries. An idempotency key is a token that lets you retry a request without sending twice.

Why people leave SendGrid

The reasons tend to be practical, not dramatic. Here is the lens we use. It describes what you may want from a provider, not a claim about any one of them: We were paying for rows, not for mail.

Reasons people give for switching providers:

• A different pricing meter. Some teams want to pay for mail sent, not for contacts stored or a plan tier.
• One system instead of two. Transactional and marketing on one API, one plan and one suppression list.
• Replies as conversations. A reply that arrives already tied to the message it answers.
• Limits on the key. Useful when an agent, not a person, holds the credential.
• Paperwork. A DPA, a subprocessor list and a clear compliance status for procurement.

One documented, dated example from the migration guide: SendGrid keeps contacts in Marketing Campaigns and opt-outs in five suppression lists, and each exports separately (export steps checked 6 September 2026 against sendgrid.com). That matters when you move, because you need every list.

For a dated feature and price comparison, use SendRaven vs SendGrid, with dated prices. It is re-verified monthly and every figure carries its check date. We quote no competitor prices here, because a number without a date goes stale.

What to check in any SendGrid alternative

These seven checks apply to every provider on your shortlist, including us. Each one says what SendRaven does, so you have something concrete to compare against.

1. The pricing meter

Ask what is counted and what happens at the limit.

In SendRaven, the meter is outbound emails sent. One counted email is one outbound recipient, so To, Cc and Bcc each count. Retries are not counted twice. Contacts are never counted. Inbound replies are free.

At the limit, an out-of-plan request returns 402 plan_limit_reached. It does not return 429, which is for rate limits. That matters in retry logic: a 402 will not clear if you wait a minute.

On Free, sending pauses at the limit. It is never auto-upgraded.

2. Transactional and marketing: one system, two reputations

One system is convenient. One reputation is a risk. You want the first without the second.

SendRaven uses two sending identities per domain: mail. for transactional and news. for campaigns. Each has its own reputation, so a newsletter cannot trash the reputation of your password resets. Read more in one plan for transactional and marketing email.

There is one suppression list, scoped by kind. Only permanent bounces are suppressed.

3. How replies arrive

Sending is table stakes. The conversation is the job.

In SendRaven, inbound replies are joined to the original message on Message-ID, never on subject, and they arrive as threads. The text field has quoted history and signature stripped, with raw_text as a fallback. sender_authenticated reflects DMARC or aligned DKIM.

One query lists what is waiting on you: GET /v1/threads?awaiting_reply=true. When you are done, POST /v1/threads/:id/handled clears the flag. Reply in thread with reply_to_message_id.

4. What unsubscribe does

Suppressing an address is half the job. The other half is whatever is still scheduled for it.

In SendRaven, unsubscribe cancels queued sends. Automations have five automatic exits: unsubscribe, reply, suppression, topic opt-out and tag rule. Topics let people opt down instead of out, so a reader who wants less mail has a choice other than the spam button.

5. Safety controls, if an agent holds the key

A credential handed to an agent can send to anyone, as often as it likes. A workspace quota only trips after the mail has gone.

SendRaven puts three limits on the API key:

• Daily send limit. Counted per UTC day in recipients. Over it, you get 429 daily_limit.
• Recipient allowlist. Addresses or domains. Anything else returns 403 recipient_not_allowed.
• requires_approval. Sends return pending_approval with an approval_id. A person releases them from a queue. Held drafts expire after 72 hours, and a key cannot approve its own drafts.

A key also cannot change its own limits. A held send is not a failure. It is the system doing its job.

6. Procurement

The facts, plainly:

• GDPR: we make GDPR claims, and the paperwork is public.
• DPA and subprocessors: both are published on the website: DPA and subprocessors.
• SOC 2: in progress. Not certified, not audited.
• Data residency: not offered. We do not claim EU, US or any other regional hosting.
• Enterprise: custom. Negotiated rates, SLA, invoicing and net terms, procurement review.

We claim no other certification or attestation.

7. Interfaces

SendRaven is a REST API at https://api.sendraven.ai/v1, with an OpenAPI document at https://api.sendraven.ai/openapi.json. There is also a remote MCP server at https://mcp.sendraven.ai/mcp (55 tools, open source). Runnable examples for Node, Python, Claude over MCP and OpenAI Agents live in the examples repo.

Whatever you shortlist, check that the API is documented in a form you can read end to end. It saves an afternoon.

Where SendRaven fits (and where it doesn't)

What it does

One API and one plan for transactional email and campaigns. Pay for emails sent. Never for contacts stored. Inbound replies are free.

Only three plans exist:

Standard's published points: $19 at 50K, $35 at 100K, $109 at 250K, $199 at 500K, $379 at 1M, $699 at 2M and $999 at 3M. After that it is $0.50 per additional 1,000. There is no tier to pick.

A payment method is required to activate sending, even on Free. There is no daily cap on Free for now.

Check your own volume with the email pricing and savings calculator, or see SendRaven pricing.

Campaigns are refused before they start if the bounce or complaint rate says so. A campaign send cannot be recalled, so preview first. (The API path says broadcasts. The product word is campaigns.)

What we don't claim

We would rather you hear the limits from us:

• Deliverability figures. We will not quote one until we have earned one.
• Dedicated IPs. We do not claim self-service dedicated IPs. Enterprise can include dedicated sending infrastructure where it helps.
• Integrations. We claim no native integrations beyond MCP.
• Data residency. Not offered.
• SOC 2. In progress, not done.

We do not have a decade of warm IPs or an abuse team of forty. If your decision rests on those, weigh it honestly.

The other usual suspects

Roundups position the common alternatives like this. These are how roundups describe them, not our verdicts:

• Postmark: reliability and inbound.
• Mailgun: inbound routing and validation.
• Amazon SES: low cost.
• Resend: developer experience.

For dated detail, see the compare pages. They hold the checked numbers, so we do not repeat them here. Comparing providers can feel like email archaeology: five pricing pages, one line that matters.

How to move off SendGrid without dropping mail

The full walkthrough is in migrating from SendGrid to SendRaven. The short version:

1. Add your sending domain and verify DNS. SPF, DKIM and DMARC should pass and align before you send real mail.
2. Send a test with POST /v1/emails.
3. Batch with POST /v1/emails/batch. Up to 100 per call. You get a 207 when some entries fail, so check each entry, not just the status.
4. Use idempotency keys. A retry with the same key delivers once. Nothing to retry, in the double-send sense.
5. Import contacts through audiences, up to 5,000 at a time. The dashboard's CSV import also takes exports from SendGrid and others, with a column-mapping step.
6. Bring your suppression data. SendGrid exports contacts and its suppression lists separately (export steps checked 6 September 2026). Import both before your first campaign.
7. Set up signed webhooks so you can verify events come from SendRaven.
8. Cut over in stages. Move transactional mail first. Campaigns can wait a week.

Warm up new sending domains gradually. See our sender's checklist for stopping emails going to spam. Nobody can guarantee inbox placement, and we will not pretend otherwise.

One more point: marketing-class email has exactly one recipient per message. If you send one message to a list in a single call, plan to split it.

FAQ

What is the best alternative to SendGrid?

It depends on why you are leaving. Match your reason (cost model, two systems, inbound replies, agent safety, procurement) to the checks above, then test the shortlist with your own traffic.

Is there a free alternative to SendGrid?

SendRaven's Free plan is $0/month for 3,000 emails, with unlimited contacts and inbound included. A payment method is required to activate sending. Sending pauses at the limit and is never auto-upgraded.

What is a good SendGrid alternative for transactional email?

Look for idempotency keys, batch sending, scheduling and a separate transactional reputation. SendRaven offers POST /v1/emails, batches of up to 100 per call, scheduled_at and a mail. identity for transactional mail.

Can one platform handle both transactional and marketing email?

Yes. SendRaven runs both on one API, one plan and one suppression list. Each domain gets two sending identities, mail. and news., so each class of mail has its own reputation.

How do I migrate from SendGrid without losing my contacts or suppression list?

SendGrid exports contacts and suppression lists separately (export steps checked 6 September 2026). Import both before your first campaign. The migration guide has the steps.

What should I check before switching email providers?

Check the pricing meter, whether transactional and marketing share a reputation, how replies arrive, what unsubscribe cancels, limits on the API key and the compliance paperwork. Then run a staged cutover.

Do I pay for contacts or for emails sent?

At SendRaven, you pay for emails sent. Never for contacts stored. Inbound replies are free. For other providers, check the dated figures on SendRaven vs SendGrid, with dated prices.

What happens when I hit my plan limit?

An out-of-plan request returns 402 plan_limit_reached, not 429. On Free, sending pauses at the limit and is never auto-upgraded.

Which SendGrid alternative handles inbound replies?

SendRaven joins replies to the original message on Message-ID, never subject, and returns them as threads. GET /v1/threads?awaiting_reply=true lists conversations waiting on you, and replies are free.

Is SendRaven GDPR compliant, and does it have SOC 2?

SendRaven makes GDPR claims, and a DPA and subprocessor list are published on the website. SOC 2 is in progress, not certified or audited. Data residency is not offered.

Next step

Estimate your cost at your own volume with the email pricing and savings calculator, then follow the SendGrid migration guide. Start free: 3,000 emails a month, unlimited contacts.