Why Europe now
For the past two years, the loudest signal in our pipeline has come from one place: Europe. About a third of our paid revenue already comes from customers headquartered between Lisbon and Helsinki, and almost none of it came from us pushing — it came from finance leads in Munich, RevOps teams in Amsterdam, and support managers in Barcelona finding us on their own and asking when we'd take them seriously.
The honest answer was: when we could do it properly. That meant a real entity, real data infrastructure on the continent, real people in regional time zones, and a real answer to the question every European procurement team asks within the first ten minutes. That work is now done.
Today we're announcing Wonderful Agent EMEA, headquartered in Dublin, with engineering and go-to-market hubs in Berlin and Madrid. We've signed our lease, we've shipped our infrastructure, and we're hiring across thirty-two roles between now and the end of the year.
EU data residency — what it really means
Every vendor selling into Europe right now claims data residency. Most of them mean one of two things: a single region in a US-controlled cloud account, or a routing layer that pretends to be European while the real processing happens in Virginia. We didn't want to be either of those.
Our EU stack runs in two AWS regions — Frankfurt (eu-central-1) and Dublin (eu-west-1) — under a separate AWS Organization owned by our Irish entity. Workloads from EU customers stay in EU regions for all stages of the pipeline: ingestion, retrieval, model inference, audit logs, backups, and analytics. Our model providers in this region are configured for EU-only routing, with contractual restrictions backed by audit access.
Practically, that means a German customer's Slack message, the embedding we generate from it, the prompt we send to a model, and the response that comes back never touch infrastructure outside the EU. We've documented this in a public architecture diagram and a third-party-attested data flow map, and we're happy to walk your DPO through it line by line. If you want BYOK with a key in your own AWS KMS instance in Frankfurt, we support that too.
The regional team we're hiring
A region without people in it isn't a region. Over the next nine months we're hiring across four functions. Engineering in Berlin: a platform team focused on EU-specific infrastructure, plus an applied AI pod working on multilingual grounding. Go-to-market in Dublin and Madrid: account executives covering DACH, the Nordics, Iberia, France, Benelux, and the UK, paired with solutions engineers fluent in the local stacks each region actually uses.
We're also building out regional customer success — every Team and Enterprise customer in EMEA gets a CS lead in their timezone, not a Slack ping that bounces around until someone in San Francisco wakes up. And we're staffing a local security and compliance function in Dublin to own the conversations with European auditors, regulators, and procurement teams directly.
If you've worked on AI products for European enterprises and the role descriptions you're seeing elsewhere feel like American job posts with the dates translated, we'd love to talk.
Localization for Spanish, French, German
All four agents — Aria, Atlas, Sage, Theo — already work across 95+ languages. But "works" and "feels native" are different bars. Through the rest of Q2 we're rolling out a focused localization pass for Spanish, French, and German that goes beyond translation.
That means: customer-facing email and chat copy reviewed by native-speaker copy editors, not just our models; locale-aware date, currency, and address handling in Atlas (so a French invoice with the date in DD/MM/YYYY and the comma decimal stops confusing the parser); CRM stage names and terminology aligned to how each market actually talks; and a region-specific compliance vocabulary in Theo for hiring and HR workflows.
Italian and Dutch ship in Q3. Polish, Portuguese, and the Nordics follow in Q4. We'll publish the localization status of every agent on a public page so you can track exactly what's been reviewed, what's machine-translated, and what's still on the roadmap.
What customers can expect this quarter
If you're already a customer in EMEA: nothing breaks. Your data stays where it is unless you actively migrate, and we'll walk you through it. EU-region migration goes live for self-serve customers in June and for Enterprise contracts on a rolling basis through July and August.
If you're evaluating us: the Dublin team is open for business. Book a walkthrough with a regional AE, request our EU architecture pack, or sign your DPA with our Irish entity directly. Pricing is unchanged in euros and pound sterling.
This is the start of a long investment, not a launch announcement. We'll write more here as the team grows and the infrastructure matures. Bis bald, à bientôt, hasta pronto.