Send from the region
closest to your users
Posthawk runs in two AWS regions — US East (N. Virginia) and EU North (Stockholm) — with full data residency in each. Pick one, point your SDK at it, and your email, logs, and contacts never cross the Atlantic. GDPR-clean by default.
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.
One signup flag,
zero config elsewhere
Pick a region at signup
Choose where your data lives — US East or EU North. Everything you send, every log line, every contact stays in that region.
Point your API at the region
Use the regional endpoint — us.posthawk.dev or eu.posthawk.dev. Same SDK, same keys, different data plane.
Send from the closest SES identity
Posthawk routes your email through an SES identity in your chosen region. No trans-Atlantic hops, no latency tax.
Stay compliant, automatically
EU customers never see US infrastructure. Logs, templates, contacts, and webhooks all honor the boundary.
Data Residency
Full regional isolation. EU data never touches US servers. Required for GDPR, common for SOC 2, mandatory for public-sector buyers.
Lower Latency
Send requests resolve in under 50ms when your app and Posthawk are in the same region — versus 100ms+ when you have to hop across the Atlantic.
Regional Storage
Every email log, template, contact, and webhook payload is stored in the region you picked. No cross-region replication unless you opt in.
Per-Region SES Pool
Posthawk maintains dedicated SES sending identities in each region. Sender reputation is scoped per region — no cross-contamination.
Cross-Region Failover
Opt in to cross-region failover for critical transactional mail. If us-east-1 has an incident, traffic hops to eu-north-1 until it recovers.
Same SLA Everywhere
Every region runs on identical infrastructure. 99.99% uptime, 30-day log retention, real-time event delivery — regardless of which one you pick.
Compliance-ready out of the box
Run in the EU region for GDPR, or in US East for SOC 2 workloads. The same Posthawk workspace can satisfy both.
Send where it matters
Pick your region at signup. Change it never.