← Blog
ARCHITECTURE2 min read

Email infrastructure is now portable across the ecosystem

May 5, 2026DekimuAI-generated

Every Dekimu app sends email — magic links, invoice reminders, DSAR acknowledgements, deletion-confirmation cascades. Until last week, every one of them was wired straight to a single email provider. As of today, every place we send email across the ecosystem goes through one provider-neutral layer. The current provider stays the active path. A swap-ready alternative sits dormant alongside it for the day we want to pull the switch.

Why this matters even when nothing changed

Provider lock-in is invisible until the day it isn't. A pricing change, a region outage, a regulatory shift in where transactional email can land — any of those flips email infrastructure from 'works fine' to 'critical migration' overnight. We wanted that switch to be a one-line config change, not a multi-file refactor. The abstraction is small on purpose: a single sender function, a normalized response shape, no provider details leaking past the boundary. Boring is the goal.

Where email is sent from, and where it is stored

Every Dekimu app processes data on EU customers. That's not a marketing claim — it's where the legal exposure lives. Our active provider sends every message from its EU region; we confirmed that setting this week and locked it in. The sending region is not the storage region: the provider is a US company and stores message content, delivery logs and account data in the United States, a transfer that relies on the EU-US Data Privacy Framework. The dormant alternative is an EU-based provider, and the portable layer is what turns moving to it into a config change rather than a migration.

The right time to build a portable infrastructure layer is before you need to be portable. Otherwise you're refactoring under fire.

What this unlocks

Two things, immediately. First, a per-app override — InvoiceUp could route through one provider while miniterms uses another, if regulatory or deliverability data ever justifies it. Second, a clean test surface: every test now asserts against the normalized response shape, not against vendor-specific internals that change across versions. The cleanup that came with this — replacing a stack of provider-specific setup notes with a single shared knowledge note — was its own quiet win.

Stage A is shipped across every app plus the starter template. Stage B (provider cutover) doesn't fire until we see one of three triggers we wrote down up front. Until then, the dormant adapter is a feature flag, not a bet.

ARCHITECTURE

This post was drafted by an AI system from Dekimu's public engineering record and published with automated checks, without per-post human editing.

← Back to blog