Deutsche Cloud
Menu

Infrastructure

Your workloads run in data centre parks in Falkenstein and Nuremberg, Germany, on a platform we build and operate ourselves. Helsinki, Finland, only where you choose it.

Where it runs

Every machine, volume, database, cache and bucket you create is in region de1, Germany, unless your organization decides otherwise. Nothing moves to another region by itself, not even when a location is full.

Region
de1, Germany
Zones
de1a Falkenstein (Vogtland), Saxony, the default; de1b Nuremberg, Bavaria.
Data centre operator
Hetzner Online GmbH, Gunzenhausen, Germany
Helsinki (`fi1`)
Region fi1 (Helsinki, Finland, EU) opens only after an administrator turns on “Allow EU locations outside Germany”, and then only for a resource someone places there. The console marks such resources “outside Germany”.
Apps across zones
An app can spread its replicas over Falkenstein and Nuremberg. All of an app’s locations are in one region, never in Germany and Finland at once.

Between the zones

Measured 13 November 2026, not guaranteed

One client committing one row at a time to a PostgreSQL cluster through the pooled endpoint, with the database leader in Falkenstein or in Nuremberg:

Leader in Latency per commit Commits per second
de1a Falkenstein 9.3 · 8.5 · 6.8 ms 108 · 118 · 148
de1b Nuremberg 11.6 · 12.1 ms 86 · 83

PostgreSQL benchmarks, with the setup to run them yourself

Platform

The hardware is rented. The platform software on it is ours: written by us, run by us, on machines in Germany. The service providers below supply the rest.

Our own control plane
The console, the API, IAM, billing, the Git server, the container and npm registries, the S3 gateway, the DNS servers and the agent on every app machine are software we wrote. It runs on machines in Falkenstein and Nuremberg, in front of a three-node PostgreSQL cluster.
Open source we run ourselves
PostgreSQL with Patroni and PgBouncer, Valkey, Caddy, WireGuard and KumoMTA for mail. None of it is a managed service of another cloud.
Backups of the platform
The platform database is backed up nightly, encrypted, to a versioned bucket in Nuremberg. The restore procedure has been rehearsed.
Your own Hetzner project
If you prefer, machines run in a Hetzner Cloud project of your own, billed to you by Hetzner, and Deutsche Cloud manages them there.

Service providers

The companies other than Deutsche Cloud that are involved in running the platform, and what each of them receives.

Provider Purpose and data When
Hetzner Online GmbH, Germany Data centre, machines, disks, networks and the storage behind object storage, and so the data stored on them. Always
Amazon Web Services (Amazon SES, Frankfurt region) Delivery of the e-mails Deutsche Cloud itself sends you: sign-up codes, password resets, invitations and notifications. Your name and e-mail address. Mail you send with our Email product goes through our own relays. For each such e-mail
Amazon Route 53 DNS for the platform’s own host names. Your hosted zones are served by our own nameservers. For each lookup of a platform name
Let’s Encrypt (ISRG) The domain names of your apps, to issue TLS certificates. For each certificate
DeutschlandGPT model API (DeutschlandGPT GmbH), models hosted in Germany or the EU What you type into the console assistant, the page you are on, and the resource data it reads to answer. The providers that run each model are named in the data processing agreement. Only when someone uses the assistant
European Commission (VIES) Your VAT ID, to validate it. At sign-up and on billing changes
GitHub Hosts the platform’s own source code and runs the jobs that build and install new releases on the control plane. No customer content. For each release
1Password Holds the platform’s own credentials, loaded when the control plane starts. No customer content. At start-up
Your identity provider, your 1Password Only if you connect them for single sign-on or secret sync. If you set it up

Invoices are paid by bank transfer, so no payment processor receives card data.