TYPO3 Managed Hosting — v13 LTS and v14, in production.
Hosting that understands TYPO3. Kubernetes-based, GDPR-compliant, hosted in Germany. 24/7 security patches, weekday major upgrades, TYPO3-specific monitoring. No surprise invoices, no 3 a.m. phone calls.
Generic web hosting doesn't understand TYPO3.
The solution
- TYPO3-specific managed hosting: v13 LTS and v14 run in production
- 24/7 security patches automated, weekday major upgrades planned
- TYPO3-aware monitoring: backend login, scheduler, FE/BE caches, indexing
- Kubernetes cluster, automatic scaling, mTLS between services
- CrowdSec WAF, rate limiting, S3-compatible object storage, CDN
- Reproducible deployment pipelines for dev, staging, production
- Restores tested regularly — backups that can actually be restored
The problem
- Standard web hosting with no TYPO3 knowledge — “It's just PHP”
- Security patches arrive late, or only after escalation
- Major upgrades (v11 → v13 → v14) are a project of their own that nobody wants to run
- Monitoring reports server load, not a stalled scheduler
- Backups run, but the restore has never been tested
- No staging, no reproducible deployment pipeline
Four building blocks generic hosting doesn't deliver
What concretely sets our TYPO3 Managed Hosting apart from standard web hosting — every point straight from running hundreds of TYPO3 installations.
GDPR-compliant, hosted in Germany, green energy
Servers run in German data centres, powered by renewable energy. Data processing, backups and logging are set up GDPR-compliant end to end — with a data processing agreement (DPA), processing register and clean deletion concepts.
Kubernetes with reproducible deployments
Every TYPO3 installation runs in its own container, fully isolated. Automatic scaling under load. Dev, staging and production share the same pipeline — “works on my machine” is a thing of the past. Rolling deployments without downtime.
TYPO3-specific monitoring
We don't just monitor server metrics, but the things that actually matter for TYPO3: scheduler tasks, backend login latency, cache hit rates, indexing status, mail queue, Composer health. We notice outages before your editors do.
TYPO3-aware patching
24/7 automated rollout of TYPO3 bug-fix and security releases. Compatibility checks against every extension in use, automatic rollback on anomaly. Major upgrades (v13 → v14) are scheduled on weekdays, documented and reproducible.
What our operations actually look like
Four posts from our blog that don't promise the hosting model but document it — from performance tuning to the patch calendar.
Why we run on AWS
How we use AWS for our hosting — and where we deliberately add other building blocks to avoid vendor lock-in.
The 3-layer model
Why our client CMS installations haven't caught fire in years — the architecture behind our hosting.
24/7 patches and weekday major upgrades
Our patch and upgrade calendar in detail — standardised, documented, reproducible.
TYPO3 backend runs as fast as the frontend
How we made our TYPO3 backend so fast that editors don't notice it any more — including the hosting consequences.
TYPO3 v13 & v14. Kubernetes. CrowdSec. mTLS. Hosted in Germany. Green energy.
Move your TYPO3 installation or set up a new one?
In 30 minutes we look at your TYPO3 installation: version, extensions, performance, hosting situation. You get a concrete proposal on whether moving to Managed Hosting makes sense for you — including a migration plan and a cost frame. Free of charge, no obligation.
Oder direkt schreiben: kontakt@moselwal.de