Solution

The EU Resend alternative – same API, data in Germany

ridu is API-compatible with Resend but runs entirely in Germany. Switch with one line, DPA included, no US providers in the data path.

Resend showed how pleasant an email API can be: clear endpoints, good SDKs, a tidy dashboard. For many companies in the EU one question remains: where does the data live, and which law applies? Resend is a US company. Even when mail is routed through a European region, the provider is subject to US law such as the CLOUD Act. That makes data protection impact assessments laborious and conversations with data protection officers long.

ridu follows the same developer-first approach but runs its entire infrastructure in Germany – with no US providers in the data path.

Switch with one line

ridu speaks the Resend API: the same paths, fields, error codes and webhook signatures. The official Resend SDKs for Node.js, Python, PHP and Go work unchanged. Replace the API key and set the base URL:

RESEND_API_KEY=rd_live_…
RESEND_BASE_URL=https://api.ridu.ai   # Node.js, PHP
RESEND_API_URL=https://api.ridu.ai    # Python

Then verify your sending domain at ridu once. It takes two DNS records: a TXT record for DKIM and one CNAME that covers return path, bounce handling and SPF.

What stays the same

  • Emails: POST /emails, batches of up to 100, scheduled sending with scheduled_at, idempotency keys, attachments, tags.
  • Domains and API keys with the same permissions (full_access, sending_access).
  • Contacts, segments, topics and broadcasts – including the older /audiences paths.
  • Templates with {{{VARIABLE}}} syntax and publishing.
  • Webhooks signed like Svix: your verification code stays.

What is different at ridu

ridu
Company and jurisdictionGermany, EU law
Data centerHetzner, Falkenstein (ISO/IEC 27001)
US subprocessorsNone
Data processing agreementConcluded at signup, version recorded
Open/click trackingOff by default
Email content retention7 days, down to “right after delivery”
Proof of consent for newslettersBuilt in, with double opt-in
BillingEuro, XRechnung e-invoices, EU reverse charge

Who benefits most

Teams processing customer data from the EU, agencies working for public clients, health and finance applications, and anyone whose customers ask about data location in procurement. “Servers in Germany, German provider, no third-country transfer” saves weeks in those conversations.

How to move

  1. Create a free account – 3,000 emails per month are free.
  2. Add your sending domain and set the two DNS records.
  3. Check your integration in test mode with an rd_test_ key; nothing is delivered.
  4. Swap key and base URL in production.

Bring your email to Europe.

Start free, send within five minutes, switch any time.