Medtech.
Health data stays in Germany.
Run digital health applications in Frankfurt, with a provider your hospital and insurance customers can check.
What changes.
From doubts to clear answers.
Customers ask where health data is processed
Frankfurt, under German and EU law
A US parent company raises access questions
enum GmbH has no US entity in its structure
Records must stay unchanged for years
Object Lock keeps objects immutable for the retention you set
Environments for different customers must be separate
Separate clusters and projects per customer
How medtech teams run on enum.
From product to rollout.
Keep data in Frankfurt
Applications, databases and files run in Frankfurt on infrastructure enum operates.
Separate what must be separate
Separate clusters and projects per customer or environment, each with its own control plane.
Lock records
Object Lock for records that must not change, and logs shipped to your own tooling.
What you run it on.
enum Kubernetes Engine
Upstream Kubernetes with a highly available control plane per cluster.
Object Storage
S3-compatible storage with Object Lock for records that must not change.
Networking
Private networking to keep sensitive services apart.
Questions.
About medtech on enum.
Where is health data stored?
In Frankfurt, Germany, on infrastructure enum operates itself. enum GmbH is a German company with no US parent.
Which certifications are in place?
The Frankfurt data center is certified to ISO 27001 and EN 50600; those certificates belong to the facility operator. enum's own ISO 27001 certification is in progress, with a target of Q4 2026, and BSI C5 is on the roadmap for 2027.
Can we keep records unchanged for years?
Yes. Object Lock keeps objects immutable for the retention period you set.
Do you provide a data processing agreement?
Yes. We provide a data processing agreement (DPA) under GDPR. Talk to us about your specific requirements.
Building for healthcare?
Talk to us about your requirements.
We go through your customers' provider questions with you.