TYPO3 Hosting on Your Own VPS
Enterprise CMS with multi-site and granular permissions, on a server sized for it.
Size a server for TYPO3
Every stop is a real configuration you can deploy. Priced per month and billed monthly, exclusive of 18% GST.
What TYPO3 is
TYPO3 is an enterprise PHP content management system, widely used in Europe and particularly in the German-speaking market. It is built for large editorial organisations: granular per-user and per-section permissions, workspaces with staged publishing, and multi-site installations sharing one backend.
It is heavier than WordPress in every dimension. The backend is a substantial application in its own right, TypoScript configuration is compiled and cached, and installations routinely serve dozens of sites from one instance. PHP memory limits and execution times need raising above defaults, and the scheduler needs real cron.
The LTS cycle is worth planning around. TYPO3 releases follow a fixed schedule with defined support windows, and major upgrades are genuine projects rather than a click. Running it on your own server means those upgrades happen when you are ready, not when a platform decides.
“TYPO3 is an easy-to-use, flexible, professional CMS and open source project offering services and solutions for the whole team across industries, organization sizes, and use cases.”
Why run TYPO3 on a VPS
Raised PHP memory and execution limits, which TYPO3 needs above stock defaults.
A real cron entry for the scheduler, indexing and cache warming.
Root access for the opcache and PHP tuning the backend depends on.
Multi-site on one machine with a certificate per domain.
TYPO3 features
Multi-site and multi-language from one installation
Granular editorial permissions and workspaces
TypoScript configuration with caching
Extension ecosystem via Composer
Staged publishing and versioning
Full-text indexed search
TYPO3 hosting requirements
The recommended starting point for TYPO3, not a hard floor — size it on the sliders.
| Memory | 8 GB — the backend and cache compilation are what drive it |
|---|---|
| CPU | 4 vCPU for a multi-site installation |
| Storage | 80 GB; file storage across many sites accumulates |
| Operating system | Ubuntu 22.04 LTS or Debian 12 |
| Installs on | Ubuntu 24.04 LTS, Ubuntu 22.04 LTS, Debian 13 (Trixie), Debian 12 Bookworm |
| Ready in | About 6 minutes |
| Smallest server | 2 vCPU · 4 GB memory · 20 GB disk |
How deployment works
TYPO3 is installed via Composer with PHP-FPM at raised memory and execution limits, MariaDB, and the scheduler on system cron. Opcache is configured with enough memory for the compiled configuration — undersizing it is a common cause of a backend that feels slow for no obvious reason.
What people run it for
Multi-site organisations
Many domains and languages sharing one editorial backend.
Editorial workflows
Workspaces and approvals, which most CMSes need plugins for.
Public sector and universities
Accessibility and permission requirements TYPO3 targets directly.
Long-lived sites
A defined LTS cycle you upgrade on your own timetable.
TYPO3 hosting questions
Related applications
WordPress Hosting WordPress on a server you control, with no plugin blocklist and your own PHP and caching stack. 
Umbraco Hosting A .NET CMS running on Linux — no Windows Server licence in the price. 
Ghost Hosting Publishing, memberships and newsletters without per-member pricing. 
Moodle Hosting An LMS sized for concurrent students, with the cron and caching Moodle depends on. 
WooCommerce Hosting A store on your own server, tuned for the pages a CDN cannot cache. Deploy TYPO3 on your own server
Root access, your choice of size, and no container between you and the application.