WordPress hosting in Germany, with the data staying here.
German sites rarely have a speed problem. They have a paperwork problem, and most of it comes from where the bytes go rather than how fast they get there.
Where the data sits is the question.
Everything below is about being able to answer a question a German customer or auditor will eventually ask.
The site, the backups and the logs, all in the EU
Data residency that only covers the live site is not residency. The origin, every backup copy and the request logs stay inside the EU, and we will name the location rather than describe a network.
An AVV you can actually file
German businesses need a processing agreement on paper before they can use a supplier. We sign one, and we will tell you which subprocessors are involved rather than leaving you to find out.
Visitor IPs truncated before they are stored
Access logs record an IP address by default, which is personal data sitting in plain files. It is shortened at write time, so the log is still useful and no longer a retention problem.
Frankfurt-close delivery for DACH readers
German, Austrian and Swiss visitors are served from the nearest edge, so the legal answer does not cost you the performance one.
Nothing loaded from outside without you asking
We do not inject fonts, analytics or tag scripts into your pages. Every outbound call from your site is one you added, which is the only way the transfer question stays answerable.
Two answers that have to match.
The site is in the EU and the backups are somewhere else is the answer that fails an audit, and it is the common one. Both halves are handled here.
- Origin, backups and logs all inside the EU
- AVV signed and subprocessors listed
- IP addresses truncated before logging
- No third-party assets added by the platform
Close to Munich, not to Virginia.
An origin outside Europe adds a transatlantic round trip to every request a cache cannot answer - which is checkout, admin and anything logged in.
What we change for German sites
Little of this is performance work. It is the set of defaults that decide whether you can answer where the data went.
| Setting | What we do | Why |
|---|---|---|
| Data residency | Origin, backups and logs pinned to the EU together | Residency that covers the live site and not the backup copies is the version that fails an audit, and it is the arrangement most providers actually ship. |
| Access log IPs | Truncated before the line is written | A raw IP address is personal data, and logging it in full means months of it sitting in plain files nobody decided to keep. |
| Platform assets | No fonts, analytics or tags injected by us | Every outbound request a page makes is a transfer somebody has to account for, so the platform must not add ones you did not choose. |
| Processing agreement | AVV signed with subprocessors named | A German business cannot onboard a supplier without one on file, and an unnamed subprocessor list makes the agreement unusable. |
| Edge routing | DACH traffic served from the nearest European edge | Keeping data in the EU should not mean routing a Swiss reader through another continent to reach it. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Where exactly is my site hosted?
Do you sign an AVV?
Are visitor IP addresses stored?
Does the platform load anything from outside the EU?
Answer the residency question once.
Move the site to an EU origin - migration is free, backups included.