Security whitepaper
Architecture, shared responsibility, identity, data protection, network, operations.
What it is
How Deutsche Cloud is built to keep your workloads and data safe: the architecture, who is responsible for what, and how identity, data, networks and operations are protected. It is written for the security and compliance reviewers who assess Deutsche Cloud as a provider. The measures in contract form are the TOMs; the companies involved are on Sub-processors.
Last reviewed: 13 November 2026.
1. The platform in one page
Deutsche Cloud is a cloud platform operated by DeutschlandGPT GmbH, Germering, Germany. It offers virtual machines, volumes, networks, load balancers, managed PostgreSQL and Valkey, Kubernetes, object storage, file storage, Git, CI, container and npm registries, app hosting, functions, queues, e-mail, DNS, KMS and secrets, monitoring and a VPN, all under one IAM model.
| Layer | Who builds and runs it |
|---|---|
| Data centres and hardware | Hetzner Online GmbH, Falkenstein and Nuremberg, Germany (ISO/IEC 27001:2022, BSI C5:2020 Type 2) |
| Virtualisation, block and object storage | Hetzner Cloud and Hetzner Object Storage |
| Control plane | Deutsche Cloud: console, API, IAM, audit log, KMS, billing, the S3 gateway, Git, the registries, DNS servers. Written and operated by Deutsche Cloud on machines in Falkenstein and Nuremberg, with a three-node PostgreSQL cluster |
| Managed services | Deutsche Cloud: the software on managed machines (PostgreSQL with Patroni and PgBouncer, Valkey, WireGuard, the deploy agent), configured, patched and monitored by Deutsche Cloud |
| Your workloads | You: your instances, your apps, your data and how you configure access to them |
Every interface (console, REST API, CLI, Terraform provider, SDKs, MCP for AI assistants) calls the same API, so the same permission check and the same audit trail apply whichever one you use.
2. Shared responsibility
| Area | Deutsche Cloud | You |
|---|---|---|
| Physical security | Through Hetzner, under its certificates | — |
| Control plane and managed services | Build, run, patch, monitor, back up the platform | — |
| Identity and access | The IAM engine, SSO, two-factor sign-in, the audit log | Who gets which policy; enforcing two-factor or SSO; rotating access keys; reviewing access |
| Managed databases and caches | Machines, OS patches, replication, failover, encrypted backups, TLS | Topology (single or cluster), backup retention, keeping TLS required, database users and schemas |
| Your instances | The hypervisor and network (Hetzner); an encrypted volume on request | The operating system, its patches (or turn on Keep OS patched), software, firewall rules |
| Apps and functions | Build machines, runtime hosts, TLS, rollout and rollback | Your code and its dependencies, the images you push, the location you choose for an app |
| Data | Encryption at rest for managed disks, buckets and backups; key custody | Classifying it, choosing a customer-managed key, versioning or object lock, retention, deletion |
| Network | Private networks, firewalls on managed machines, TLS endpoints | Security group rules, what you expose publicly |
| Compliance | Deutsche Cloud's own controls and this documentation | Your own ISMS, policies and records; how you use Deutsche Cloud within them |
3. Identity and access
- One policy engine. Each request is evaluated against the caller's policies, AWS-IAM style:
default deny, explicit deny wins, actions named
service:Action, resources named by Deutsche Cloud Resource Names. The organization owner has anAdministratorAccesspolicy and no other privilege. - Conditions on source IP range, time, two-factor sign-in, region and zone. They fail closed.
- Sign-in: password with scrypt hashing, TOTP or passkey as a second factor, an organization-wide two-factor requirement, OIDC and SAML single sign-on enforced per verified domain, rate limits per account and per address.
- Short-lived credentials: 90-day CLI keys, GitHub Actions OIDC federation (at most one hour), one-hour MCP tokens with read, write and destructive scopes, temporary S3 credentials.
- Sensitive reads (secret values, source code) are authorized and audited like writes, and are left out of the read-only presets.
- Staff access to the control plane goes through the same engine, with policies that live in the platform's own organization and that no customer organization can grant.
- Staff SSH to a managed machine is a 15-minute certificate for that one machine, issued to a
person signed in with a second factor who gives a reason, usable only from the control plane. It
is recorded in your audit log before it is issued. There is no shared key; managed machines
accept no
authorized_keysand no passwords.
4. Audit and evidence
- Every change, every refused change, every sensitive read and every sign-in event is written to the organization's audit log with who, from where, what and the outcome.
- Tamper evidence: a per-organization SHA-256 hash chain, with the chain head signed (Ed25519) every hour. The verification procedure and the public key are documented, so your auditor can check an export without trusting Deutsche Cloud.
- Retention 400 days by default, adjustable from 90 days to 10 years.
- Delivery to your own S3 bucket, webhook or syslog server, plus alarm e-mails, and export as JSON lines or CSV.
5. Data protection
Encryption at rest. Managed database, cache and file-storage disks are always encrypted with LUKS2 (AES-256-XTS); compute volumes and Kubernetes volumes are encrypted by default. Each disk has its own key, wrapped by the platform key or by your KMS key, and released only to the machine the disk is attached to. Buckets are encrypted per bucket. Database backups and cache snapshots are encrypted on the machine before they are uploaded. Secrets are encrypted with AES-256-GCM under your KMS key.
Key management. KMS keys are AES-256-GCM keys held by the control plane, wrapped by the installation's platform key. You can create, disable, grant, rotate and schedule deletion of your keys (7 to 30 days' waiting period), or import your own key material (BYOK). There is no hardware security module: keys are held in software, and the platform key can be rotated by the operator.
Encryption in transit. TLS on every public endpoint, HSTS and a Content Security Policy on the console, TLS required by default for PostgreSQL and Valkey with the platform CA, WireGuard for the VPN, SSH with public keys for Git.
Deletion. Deleting a disk deletes its key, so its contents cannot be read again. Deleting a database deletes its backups (or keeps one final backup if you ask for it, until its retention ends).
Location. Resources are created in region de1: Falkenstein or Nuremberg, Germany. An app
can be placed in another Hetzner location if someone in your organization chooses one; see
Data location.
6. Network
- A VPC is a private network of its own. Security groups filter traffic to your instances.
- Managed databases and caches have no public address by default; they are reached from your VPC, or by a person through the Client VPN, one granted target at a time.
- Load balancers can run without a public interface.
7. Operations
- Patching: managed machines install operating-system security updates automatically; restarts are scheduled by the control plane, and database services are not restarted by updates. Kubernetes nodes are patched by replacing their image.
- Vulnerability scanning: every pushed container image is scanned; the platform's own dependencies are checked every six hours and on every change, and updates are proposed automatically.
- Change management: every change runs automated checks; automatic deployment requires them to pass. Production releases are started by hand.
- Monitoring: health checks of the control plane, of every managed database every two minutes, metrics and alarms for your resources.
- Backups of the platform: the control-plane database is backed up nightly, encrypted, and the restore procedure has been rehearsed.
- Isolated builds: builds and CI runs each get a new machine, deleted when they finish.
8. Incidents and vulnerability reports
Report a vulnerability to the address in /.well-known/security.txt. How and when we inform
you about an incident affecting your data is set in the DPA.
9. Certifications
Deutsche Cloud holds no certificate or attestation of its own yet. Hetzner's ISO/IEC 27001:2022 certificate and BSI C5:2020 Type 2 attestation cover the data-centre and infrastructure layer Deutsche Cloud runs on; see Sub-processors.
10. What is not covered
The limits are listed under TOMs → What is not covered.