Data residency & EU hosting
Mildport is built and operated by Capitality from Germany, and runs in two modes: an EU-hosted cloud, or a self-hosted deployment inside your own infrastructure. This page describes where customer data lives in each mode.
This page is the public RFP and security-review summary. It names the infrastructure providers and regions buyers ask about, without exposing operational internals.
At a glance
Section titled “At a glance”| Area | Mildport posture |
|---|---|
| Company | Capitality, based in Germany (EU). |
| Legal framework | GDPR. |
| Cloud compute | Civo Kubernetes, region FRA1 (Frankfurt, Germany). |
| Cloud file storage | Cloudflare R2 with the EU jurisdiction — data at rest stays in the European Union. |
| Self-hosted mode | All data stays inside your infrastructure; nothing touches our cloud. |
| Licensing | Offline signed keys, verified locally — no license server, no phone-home calls. |
| Live demo | Runs entirely in the browser; demo files are never uploaded. |
Cloud mode
Section titled “Cloud mode”In cloud mode, customer data is processed and stored on infrastructure located in the European Union:
- Compute. The import engine runs on Civo Kubernetes in the FRA1 region — Frankfurt, Germany.
- File storage. Uploaded files and import artifacts are stored in Cloudflare R2 buckets created under the EU jurisdiction, which keeps data at rest inside the European Union.
- Import state. Mapping sessions, decisions, and delivery logs live in MongoDB on the same Civo cluster in FRA1.
- Backups. Database backups are stored in the same Cloudflare R2 storage under the EU jurisdiction — they stay in the European Union too.
- Delivery. Clean records leave the platform only through the delivery channels you configure: HMAC-signed apply webhooks to your endpoint, or the API.
Self-hosted mode
Section titled “Self-hosted mode”In self-hosted mode, no customer data touches our cloud at all. The engine, the import-state database, and the blob storage run wherever you deploy them — your VPC, your data center, or an isolated environment.
- Files, intermediate results, and final records stay inside your infrastructure.
- Licensing is offline: signed keys are verified locally, with no license server and no phone-home calls.
- If AI assist is enabled, you bring your own model endpoint, so the model vendor and region also stay under your control.
Start with the Self-hosting overview.
Sub-processors (cloud mode)
Section titled “Sub-processors (cloud mode)”The list is short by design:
| Provider | Role | Location |
|---|---|---|
| Civo | Compute and database (Kubernetes, MongoDB) | FRA1 — Frankfurt, Germany |
| Cloudflare | Object storage and backups (R2) | EU jurisdiction |
| CloudMailin | Transactional email — waitlist and licensing notifications | United Kingdom (EU adequacy) |
Email is used only for notifications and licensing correspondence. Import data never travels by email.
AI assist
Section titled “AI assist”AI assist is optional and off by default. In supported deployments you configure the model endpoint yourself, which keeps the LLM vendor, region, and data-processing agreement under your control. See AI transparency for the full posture.
For enterprise diligence, pilots, and licensing questions: [email protected].