Medplum in Europe: where your data lives and what to check
Building on Medplum for patients in Europe? Its hosted service keeps data in the US. Your EU options, and the GDPR checks to run first.
If you are building a health app for patients in Europe and you like Medplum, your first question is not about features. It is about where the patient data will live. Medplum's hosted service keeps customer data in the United States. To keep data in the EU, you either self-host Medplum's open-source server or use a managed platform that runs it in an EU region. This guide sets out what Medplum's own pages say, the checks a European team should run, and the options that follow.
Key takeaways
- Medplum's hosted platform runs in AWS US East (N. Virginia) and replicates to US West (Oregon). Its documentation says hosted customer data does not leave the United States.
- None of Medplum's public plans (Free, Production, Premium, Enterprise) lists an EU region. Enterprise can be self-hosted, with setup help from Medplum.
- Self-hosting puts Medplum in any EU region you choose, but you then run the database, upgrades, backups and security controls yourself.
- Medplum's compliance page lists US frameworks such as HIPAA, ONC and HITRUST, plus SOC 2 Type II. It lists no EU-specific certification.
- Ovok is a managed platform built on Medplum's open-source FHIR server. Paid plans run in AWS Frankfurt and include a GDPR Article 28 data processing agreement.
What Medplum says about where hosted data lives
Medplum is an open-source healthcare developer platform under the Apache 2.0 licence, with a FHIR R4 API, WebSocket subscriptions and Bots for custom server-side logic. You can use it as a hosted service or run it yourself.
For the hosted service, Medplum's page on high availability, backup and retention is explicit. The primary region is AWS US East (N. Virginia), replicated continuously to a second US region, US West (Oregon). In its own words: "All hosted customer data remains within the United States." For US healthcare that is a strong design: the replica survives the loss of a whole region, and HIPAA customers get what they need.
For a European product it means the hosted service stores patient data outside the EU. Your legal team has to treat every hosted environment, including staging, as a transfer of health data to a third country.
The pricing page, as of November 2026, lists Free ($0 per month), Production (from $2,000 per month), Premium (from $6,000 per month) and Enterprise (contact sales). Free, Production and Premium are hosted by Medplum. Enterprise can be hosted or self-hosted, and includes optional help with setup, provisioning and upgrades when you self-host. None of the plans mentions an EU region, data residency or GDPR.
Why location matters under GDPR
Health data is a special category of personal data under GDPR Article 9. Storing it with a processor in the US is not forbidden, but it adds work:
- A transfer mechanism. Chapter V of the GDPR needs a lawful basis for the transfer, such as the EU–US Data Privacy Framework if the recipient is certified, or standard contractual clauses with a transfer impact assessment.
- Customer due diligence. Hospitals, care providers, insurers and public payers in Europe often ask for EU hosting in their procurement checklists. A US data location can end a deal before anyone looks at your product.
- National rules on top. Some member states add their own requirements for health data, for example on where it may be processed or which security attestations a cloud provider needs. They vary by country and by customer type, so check each market you sell into.
This is not legal advice. Ask your data protection officer or counsel what applies to your product and your customers.
Your options for running Medplum's server in Europe
1. Self-host Medplum in an EU region
Medplum documents several self-hosting paths: AWS with CDK and CloudFormation templates (its recommended option, and the one it uses for its own hosted service), Ubuntu through an APT repository, Google Cloud and Azure through Terraform (both marked beta), or a build from source. You can choose an EU region, such as Frankfurt.
What you take on:
- Running Postgres, Redis, the API servers and file storage, with high availability and backups.
- Upgrades. Medplum releases often; v5.2.18 was the latest release when we wrote this.
- Security operations: patching, monitoring, incident response and access reviews.
- Your own compliance evidence. Medplum's certifications cover its hosted service, not your deployment.
Self-hosting suits a team that already runs production infrastructure and wants to change the server's code.
2. Ask Medplum about Enterprise
Medplum positions its Enterprise plan for organisations with complex workflow, integration or hosting needs. If you want Medplum as your vendor, ask its sales team in writing whether it can host in the EU, where exactly, and under which contract terms.
3. Use a managed platform that runs in the EU
Ovok is a managed FHIR R4 backend built on Medplum's open-source server, behind Ovok's own API gateway. Paid plans run in AWS Frankfurt (eu-central-1), and the free Developer sandbox runs in the EU too. Every paid plan includes a data processing agreement under GDPR Article 28. You don't operate the server: you create a project and call the FHIR API.
Because the data layer is Medplum's server, your FHIR resources keep their standard R4 shape. What changes is the layer around it: Ovok has its own authentication, Access Policies, SDKs and Console. We compare the two side by side on our Medplum alternative page.
A checklist before you commit
Whichever path you choose, get these answers in writing:
- Region. Which region holds the primary database, the replicas, the backups and uploaded files? Is any of it outside the EU?
- DPA. Is a GDPR Article 28 data processing agreement included, and on which plan?
- Sub-processors. Who are they, where do they process data, and how are you told about changes?
- Transfers. If anything leaves the EU, which Chapter V mechanism covers it?
- Audit trail. Can you show who read or changed a patient's record, and how long are those logs kept?
- Exit. How do you export all your data as standard FHIR, and how long does it take?
- Operations. Who patches, scales, backs up and restores the server? What are the recovery time and recovery point objectives?
When Medplum is the better choice
Medplum is an excellent platform, and for many teams it is the right one:
- Your patients and customers are in the US, and you need a HIPAA BAA, SOC 2 or ONC certification today.
- You want to self-host the open-source server and change its code.
- You are building an EHR with e-prescribing, labs or claims.
When a European managed platform fits better
- Your patients are in Europe, and you want their data in an EU region without running the server yourself.
- Your customers' procurement asks for EU hosting and a DPA before it looks at features.
- You build remote monitoring and want devices, wearables and alerting next to the FHIR store.
FAQ
Does Medplum offer EU hosting?
As of November 2026, Medplum's documentation says hosted customer data remains in the United States, and its pricing page lists no EU region. You can self-host Medplum in an EU region, and the Enterprise plan includes help with self-hosting. Ask Medplum for current terms.
Is Medplum GDPR compliant?
GDPR compliance depends on how a product is hosted, contracted and operated, not on the software alone. Medplum's public pricing and compliance pages do not mention GDPR or a data processing agreement; its Trust Center may hold more, so ask. If you self-host, showing that your deployment complies is up to you.
Can I run Medplum in Frankfurt?
Yes, by self-hosting it in a Frankfurt region of AWS, Google Cloud or Azure and operating it yourself. Or use Ovok, which runs Medplum's open-source server for you in AWS Frankfurt on paid plans.
How is Ovok related to Medplum?
Ovok uses Medplum's open-source FHIR server as its data layer, under the Apache 2.0 licence. It adds its own API gateway, authentication, SDKs, Console, device and wearable integrations, and hosting in the EU. Ovok is a product of ACTIMI GmbH and is not affiliated with or endorsed by Medplum.
Does using Ovok make my app a medical device?
No. ACTIMI Signals, an optional component for enrolled patients, is an MDR Class IIa medical device. Ovok itself is not, and your app's regulatory status depends on its own intended purpose.
Conclusion
If you would pick Medplum for a US product, the European decision comes down to two questions: where the data lives, and who runs the server. Self-hosting answers both if you have an operations team. If you would rather build the product, try the free Developer sandbox, read the Ovok docs, and compare pricing.
Medplum is a trademark of its owner. Facts about Medplum come from its public website as of 20 November 2026.