---
canonical: https://enum.co/use-cases/fintech
locale: en
---

**Fintech & Financial Services**

# Fintech Infrastructure

Run regulated services on EU infrastructure with residency, logging, and isolation you can explain to auditors.

Fintechs, banks, and financial institutions build regulated applications on enum's European public cloud in Frankfurt. Managed Kubernetes, S3-compatible object storage with Object Lock, and VPC networking support GDPR, DORA, and NIS2 readiness, with no US CLOUD Act exposure.


### What fintech teams hit

- Data residency that procurement and regulators will accept
- Low-latency paths for payment and trading-adjacent workloads
- Evidence for access, changes, and retention
- US cloud providers that create CLOUD Act and transfer risk

### What you run on enum

- Frankfurt data centers under German and EU jurisdiction
- High-performance Kubernetes close to your users in Europe
- Infrastructure audit logs plus Object Lock for immutable retention
- No US hyperscaler dependency in the control or data path

### What changes

- A European public cloud story that survives security questionnaires
- Residency and jurisdiction answers without a US cloud parent
- Infrastructure you can operate with standard Kubernetes tooling

### How fintech teams land on enum

From risk assessment to production cutover.

- **Map residency and scope**: Confirm which workloads and datasets must stay in the EU. Frankfurt is the default region for enum today.
- **Deploy on isolated planes**: Each Kubernetes cluster gets its own isolated control plane. Segment environments the way your risk model requires.
- **Lock and log what matters**: Use Object Lock for retention-sensitive artifacts. Keep change and access evidence in your existing SIEM.

### Platform pieces that matter

Building blocks for regulated product and platform teams.

- **enum Kubernetes Engine**: Upstream Kubernetes with an isolated control plane per cluster. Fits DORA and NIS2 operational models.
- **Object Storage**: S3-compatible storage with Object Lock for retention and evidence packages.
- **VPC & Networking**: Private networking, L4 load balancing, and traffic segmentation for regulated services.

### Keep reading

- [NIS2 & DORA](/kubernetes-nis2-dora): How EU Kubernetes maps to the rules
- [Security](/security): How enum approaches platform security
- [enum Kubernetes Engine](/kubernetes-engine): Isolated control planes in Frankfurt
- [Customer stories](/customers): Production teams on enum
- [SaaS use case](/use-cases/saas): Multi-tenant products on the same stack
- [Contact](/contact): Talk through your risk model

### FAQ


**Does enum help with DORA and NIS2?**
enum provides EU-operated infrastructure, isolated control planes, and logging hooks that support how financial entities meet DORA and NIS2. Your policies and oversight stay yours; the platform removes US cloud dependencies from the stack.

**Is customer data subject to the US CLOUD Act?**
No. enum is a German company operating a European public cloud in Frankfurt. There is no US parent that can be compelled to hand over EU customer data under the CLOUD Act.

**Can we keep production and audit trails separate?**
Yes. Run separate clusters and projects for environments, and use Object Lock buckets for retention-sensitive artifacts. Wire logs into your SIEM the same way you would on any Kubernetes platform.

**Where can we read more about NIS2 and DORA?**
See enum's NIS2 and DORA page for how sovereign EU Kubernetes maps to those frameworks.