Email infrastructure built and operated inside the European Union.
The thing that decides whether your email lands is not a clever feature — it is where your data sits, how cleanly your IPs reach each mailbox provider, and whether the platform stays up when volume spikes. Our infrastructure is EU-resident, the dedicated IPs are yours, and the deliverability relationships with the major providers are already in place.
We publish where our datacenters are below. What we do not publish is the internal topology — addressing, peering, and routing detail — because that is operational surface, not a buyer's decision input. What matters to you is here: locations you can map to a jurisdiction, data residency you can put in a contract, and resilience that does not depend on filing a ticket to learn the platform is healthy.
Seven locations across Europe, North America, and Panama.
Owned bare-metal hardware operated directly by our team. Five EU-resident locations cover European deliverability and data residency; Dallas handles North-American senders; Panama serves the offshore-hosting product under a documented non-EU/US jurisdiction. You choose which location your traffic originates from during configuration.
| # | Location | Country | Role | Status |
|---|---|---|---|---|
| 01 | London | United Kingdom | UK + EU edge | Operational |
| 02 | Amsterdam | Netherlands | High throughput | Operational |
| 03 | Frankfurt | Germany | EU central | Operational |
| 04 | Strasbourg | France | Schrems-safe · France | Operational |
| 05 | Vienna★ | Austria | Headquarters | Operational |
| 06 | Dallas | United States | North America gateway | Operational |
| 07 | Panama | Panama | LATAM · offshore | Operational |
Where your data lives, written down rather than implied.
Data stays in the EU
Message content, recipient data, and engagement events are processed on EU-resident infrastructure by default. The processing locations you have selected are recorded in your DPA, and customer data is never copied outside that scope to provide the service.
EU-only routing option
Enterprise contracts can pin sending and routing to EU-resident infrastructure only. When that option is enabled, traffic is kept within the European Union end to end rather than transiting non-EU networks.
Documented transfer posture
Where any non-EU element is involved for a specific customer, the Transfer Impact Assessment for that arrangement is documented under Schrems II and provided under NDA, so your DPO has referenceable text rather than a verbal assurance.
Austrian operating entity
OS Domains GmbH is incorporated in Austria and operates under EU law, which removes US CLOUD Act and FISA 702 exposure by construction for the data we process on your behalf.
How we reach Gmail, Outlook, Yahoo, and the major regional ISPs.
Connectivity to mailbox providers is the part of email infrastructure that actually moves the inbox rate. The relationships and configuration below are in place before you send your first message, not assembled reactively after a deliverability problem.
Mailbox-provider programs
We are enrolled in the major mailbox-provider feedback and reputation programs — Google Postmaster Tools, Microsoft SNDS, and the JMRP-style feedback loops offered by Yahoo, Apple, and the large regional ISPs — so complaint and reputation signals flow back into the platform automatically.
Dedicated IP pools
Sending happens from dedicated IP addresses you control, separated by stream so that a critical transactional message is never sharing reputation with a marketing campaign. Pool layout is configured per account during onboarding.
Reputation warm-up
New dedicated IPs and domains follow a managed warm-up schedule that raises volume gradually within the tolerances each provider expects, rather than sending at full volume on day one and tripping rate limits.
Authentication by default
SPF, DKIM, and DMARC alignment are configured for every sending domain, with DNSSEC available for the zones we host, so receivers can validate every message you send.
What keeps the platform up and the data protected.
DDoS protection at the edge
Inbound and infrastructure traffic is fronted by edge DDoS mitigation. Routine volumetric noise is absorbed transparently; larger events trigger automated upstream mitigation before they reach sending capacity.
Capacity headroom
Infrastructure runs with deliberate headroom rather than at saturation, so seasonal peaks — Black Friday, end-of-quarter statement runs — are absorbed without re-architecting or emergency provisioning.
Encryption in transit
TLS 1.3 is mandatory for delivery wherever the receiving server supports it, and internal service-to-service traffic is encrypted. Opportunistic TLS is enforced upward, never silently downgraded.
Monitoring and alerting
Delivery, reputation, and platform health are monitored continuously, with the live state of the platform published on the status page rather than kept behind a support ticket.
Live platform status, without a support ticket.
The status page shows the live health of the platform. For data-residency specifics, routing options, or a Transfer Impact Assessment, the engineering and compliance team will give you referenceable text under NDA.