MCP-native for Cursor, Claude Code, and Windsurf
Product

Send from the region
closest to your users

Posthawk dispatches mail through two AWS regions — US East (N. Virginia) and EU North (Stockholm). Pick a region per domain when you add it, and every send through that domain stays on the regional SES path you chose. GDPR-friendly by design.

Two regions, one platformdata stays in the region you pickUS-EastN. Virginia · us-east-1EU-NorthStockholm · eu-north-1
Pick a region

Latency you can
actually measure

Click a region to see roundtrip latency from every other region to that endpoint. These are real SES-to-SES times measured from AWS backbone, not marketing estimates.

Click any region below
Region picker
eu-north-1
Data residency
EU only · GDPR compliant
Latency from EU North
🇺🇸US East102ms
🇸🇪EU North11ms
How it works

Region per domain,
locked at creation

01

Pick a region per domain

When you add a sending domain, choose where it lives — US East or EU North. The region is locked to that domain for life.

02

Add the DNS records

Posthawk shows you the SPF, DKIM, and DMARC records for the region you picked. Same setup flow either way — only the MAIL FROM host differs.

03

Send from the closest SES identity

Every send through that domain dispatches via an SESv2 client in your chosen region. No trans-Atlantic hops for EU sends.

04

Mix regions in one workspace

Run a US domain and an EU domain side by side in the same Posthawk workspace. Each domain stays in its own region — pick at creation, immutable after.

Per-Domain Residency

Sends from an EU domain dispatch through SES eu-north-1; sends from a US domain dispatch through us-east-1. Outbound delivery never crosses the boundary you set.

Lower Latency

Hand-off to SES happens in the closest region to the recipient infrastructure. EU recipients get an EU-region send path, no trans-Atlantic detour.

Region-Locked at Creation

Domain region is set when you add the domain and never changes. Re-adding under a different region is a fresh setup, by design — DKIM and BYODKIM keys are region-scoped.

Per-Region SES Pool

Posthawk maintains dedicated SESv2 clients and BYODKIM identities in each region. Sender reputation is scoped per region — no cross-contamination.

Mix in One Workspace

Run a US domain and an EU domain together in the same workspace. Choose at send time which from-domain (and therefore which region) to use.

Same Pipeline Everywhere

Every region runs the same worker, the same BullMQ queue, the same suppression logic and the same webhook delivery — only the SES endpoint changes.

Built on a compliance-friendly foundation

EU sending stays on EU SES. Posthawk runs on AWS, which holds GDPR, SOC 2 and ISO 27001 attestations — your sends inherit that infrastructure.

GDPREU residencyBYODKIMTLS 1.2+

Send where it matters

Pick a region when you add a domain. Mix US and EU in one workspace.

Cookie Preferences

I use analytics cookies to understand how you use the site and improve your experience. Privacy Policy