Study guide · Hosting, Versions and Maintenance
Hosting, versions and maintenance: running TYPO3 safely and predictably
A website is not a project that ends at launch. It runs on a server, needs updates and sooner or later has to move to a new TYPO3 version. On this page you guide a client through exactly these questions. Afterwards you can assess hosting offers, explain support periods and set up a maintenance plan.
The example: the Seetal holiday region
The Seetal holiday region is having its website rebuilt, and you advise it on behalf of the agency. The management asks three questions. Where do we host? What happens when a TV programme sends ten times as many people to the site? And how long will TYPO3 14 last if we postpone the next upgrade? Anyone who leaves these questions out of the proposal will have an annoyed client with an insecure website three years later.
What TYPO3 needs on the server
At its core, TYPO3 needs three things: a web server, PHP and a database.
- Apache, NGINX or IIS work as the web server. For Apache, TYPO3 ships a ready-made
.htaccessfile, which was revised in TYPO3 14. - TYPO3 14 runs on PHP 8.2 to 8.5.
- For the database, get.typo3.org lists MySQL from 8.0.17, MariaDB from 10.4.3 to 10.x, PostgreSQL from 10 and SQLite from 3.8.3. MySQL and MariaDB must use the InnoDB storage engine.
- For image processing you add GraphicsMagick or ImageMagick. GraphicsMagick is the recommendation.
- For Composer installations the server needs Composer version 2.1 or later.
PHP extensions are add-on modules for PHP. Without them TYPO3 does not start, or parts are missing. Required are, among others, pdo, session, xml, filter, SPL, standard, tokenizer, mbstring, intl and sodium. The TYPO3 environment check also expects gd, zip and zlib. Recommended are fileinfo for detecting file types, exif for the orientation of uploaded images and openssl for encrypted mail delivery. Xdebug, on the other hand, is a debugging tool for developers. It slows things down and does not belong on the live server. TYPO3 does not need the PHP extension imagick either. For images, it calls the programs GraphicsMagick or ImageMagick.
The settings in php.ini matter too. The TYPO3 documentation recommends these values:
memory_limit = 256M
max_execution_time = 240
max_input_vars = 1500
pcre.jit = 1The environment check in the install tool is stricter about memory. Below 256 megabytes it reports an error, and it advises at least 512 megabytes. You set the upload limits to match the files editors upload. The live server never shows error messages publicly. They reveal paths and versions to attackers.
Beyond the minimum requirements, an environment that is easy to run needs more:
- SSH access and Composer, so deployments can run from the command line.
- A cron job that starts the TYPO3 scheduler regularly. The scheduler then handles tasks such as cleaning up old data, publishing from workspaces on a schedule or checking links. Without a cron job none of this happens.
- HTTPS with a valid certificate.
- Write permissions for the web server only where TYPO3 needs them, for example in the folder
varand infileadmin, not on all system directories.
Unencrypted FTP as the only access is considered insecure and does not fit with Composer.
Three hosting models
The learning objectives distinguish three ways to host TYPO3. TYPO3 runs in all three. They differ in control, scalability, responsibility and cost.
Traditional hosting provider: It offers shared hosting, managed servers or dedicated servers. It provides proven infrastructure. Specialised providers with TYPO3 experience offer suitable PHP versions, cron jobs, SSH and often staging environments. A service level agreement, SLA for short, governs availability and response times. Content and development still remain the job of the project. No hosting provider maintains your content or guarantees first place in search engines.
In-house hosting, also called on-premises: the client runs the servers itself. That gives the most control over data, systems and compliance requirements. In return, the client carries the responsibility for operations, updates, security, backups and staff.
Cloud hosting: Computing power can be added when needed and removed again, for example during a campaign. Billing is often based on usage. The cloud still needs configuration, though. You have to clarify where the data lives and how dependent you become on the provider.
Seetal has no IT department of its own, but strong traffic peaks. Managed hosting with caching layers fits well there.
Containers: the same environment everywhere
A container is a self-contained runtime environment. It bundles an application with everything it needs, such as the web server and PHP in fixed versions. That way you can rebuild exactly the same environment at any time. The best-known tool for this is Docker, often used locally through DDEV. In production, platforms such as Kubernetes run and scale many containers.
Three advantages matter most for TYPO3 projects:
- Development, testing and production run in identical environments. The “works on my machine” problem becomes rare.
- Under load, you can quickly add more instances.
- The versions of the server components are clearly defined and traceable.
But containers are short-lived. Whatever is stored inside a container is gone at the next restart. Persistent data such as fileadmin, the database, logs and sessions must therefore live outside, in persistent storage or separate services. Operations and orchestration require extra know-how. And container images need updates too. No container is secure without updates, and TYPO3 still needs a database.
If a website is to run on several containers in parallel, all instances must see the same data. You then need the database, a shared storage for uploaded files such as fileadmin, and a concept for caches and sessions that all instances use. A separate database per container would be wrong: visitors would see different content depending on the container. The domain stays the same as well. A load balancer distributes the requests across the containers.
Caching and load time
Rendering a page in TYPO3 takes time. That is why TYPO3 stores the finished result in the cache and delivers it directly on the next request. When an editor changes the page, TYPO3 clears its cache.
The caching framework separates the caches from their storage location, the so-called cache backend. Besides the database, the file system, Redis, Memcached and APCu are possible, among others. Fast in-memory stores such as Redis take load off the database when traffic is high, but they need a matching service on the server. Backend and frontend sessions can live in Redis too. Since TYPO3 14, this also applies to the sessions of the install tool. Several servers then no longer need a shared file system for them.
Uncached areas are the most common brake. TYPO3 renders a plugin that is not output as cached on every request, and that slows down the whole page. Adding the URL parameter no_cache to links or switching the cache off completely makes everything slower, not more current.
Other levers for a fast website:
- Deliver images in a suitable size and in modern formats.
- Compress static files such as CSS and JavaScript and let browsers cache them for a long time. Since TYPO3 14, compression is handled by the web server alone, for example with gzip or Brotli. TYPO3 itself no longer compresses its responses. TYPO3 14 has also removed the concatenation and pre-compression of CSS and JavaScript from the Core.
- Include as few external scripts as possible. Every third-party script costs load time.
You should measure before and after. Tools such as Google PageSpeed Insights and Lighthouse rate the load time and give hints. They also show Google's Core Web Vitals. These three values measure the user experience while loading, when responding to input and in terms of visual stability. They are called Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Because results vary, you measure regularly.
Scaling: when everyone shows up at once
An online magazine or the Seetal site usually has little load, but briefly ten times as much during campaigns. What matters then is that resources can be scaled quickly, for example in the cloud or with caching layers. A large hard disk does not help, and permanently oversized servers would be expensive.
There are two directions for scaling:
- Vertically, you make one server more powerful, with more CPU cores and more memory. That is simple, but it hits limits at some point.
- Horizontally, you add more servers and distribute the load with a load balancer. For that, all servers need a shared database, shared files and shared caches.
The two can be combined. On top of that come caching layers in front of TYPO3.
Varnish is a reverse proxy cache. It sits in front of the web server, stores finished pages and answers repeated requests very quickly from its memory. As a result, TYPO3 receives the load less often.
A content delivery network, CDN for short, is a network of distributed servers. It keeps copies of images, scripts or whole pages in many locations and delivers them close to the visitors. That shortens load times and takes load off your own server. You have to clarify data protection questions along the way.
If you cache whole pages in Varnish or a CDN, two rules apply:
- Personalised content and areas behind a login must not be cached for everyone. Otherwise visitors see other people's data. Forms and login areas need exceptions.
- When an editor changes a page, it must be possible to clear the upstream cache selectively. Extensions provide integrations for this.
Versions and release cycle
LTS stands for Long Term Support. An LTS version is maintained with bug and security fixes for several years. That is why the current LTS is the usual choice for projects.
A new major version comes together in steps:
- First come the sprint releases. For TYPO3 14 these were 14.0 in November 2025, 14.1 and 14.2. They bring new features and restructuring. Each sprint release is supported only until the next one.
- At the end comes the LTS version. For TYPO3 14 this is internally 14.3, released on 21 April 2026. For TYPO3 13 it was 13.4, released in October 2024.
- After that, no new features are added to this branch, only fixes in patch releases such as 14.3.6 and 14.3.7.
In everyday use people simply say “TYPO3 14 LTS”. A new LTS is planned roughly every 18 months. The current and the previous LTS are supported free of charge. After TYPO3 14 LTS is released, these are version 14 and version 13. Version 12 and older no longer receive free updates.
How long does an LTS last? About three years. For roughly the first year and a half there are bug fixes, after that only security and critical fixes. According to get.typo3.org, as of September 2026, TYPO3 14 is regularly maintained until 30 June 2029, with ELTS until 30 June 2032. For TYPO3 12, free maintenance ended on 30 April 2026. ELTS runs there until 30 April 2029 for everyone, and with the fourth year for partners until 30 April 2030. Always check such dates against the current source for your clients.
Maintenance releases follow a published schedule and usually come out on a Tuesday. Security releases come out for all supported versions at the same time. That lets site owners plan their updates.
Where do you find what is new? In the release notes, in the news on typo3.org and in the changelog of the TYPO3 documentation. There are also “What's new” overviews, and the roadmap on typo3.com shows planned versions. The changelog assigns each change a type:
- Feature: a new function.
- Deprecation: A function is marked as outdated. It still works, but it will be removed in a later major version. If you remove deprecated calls early, the upgrade is less work.
- Breaking: A change makes existing code or existing configuration incompatible. Extensions, templates or TypoScript have to be adapted. Breaking changes come mainly in major versions, and removals of deprecated functions are listed here.
- Important: an important notice.
PHP has an expiry date too. Each PHP version is actively maintained for a few years and then receives only security fixes. After that its support ends completely. At the same time, every TYPO3 version supports only certain PHP versions, TYPO3 14 for example PHP 8.2 to 8.5. When support for a PHP version ends, PHP has to be raised, and the new version has to match the TYPO3 version. Both therefore belong in maintenance planning.
TYPO3 does not bring its own PHP. It uses the PHP of the server.
ELTS: buying time, not skipping upgrades
A version without support no longer receives security updates. Known vulnerabilities stay open, and attackers look specifically for old versions. Matching PHP versions and extensions also disappear. The website is not switched off, it just becomes less and less secure.
For the transition period there is Extended Long Term Support, ELTS for short. It is a paid service of the TYPO3 GmbH. After free maintenance ends, it continues to deliver security and compatibility updates. The terms:
- ELTS extends support by up to three years for all organisations. A fourth year is available only to TYPO3 partners. This gives a major version up to seven years of support.
- An ELTS plan covers exactly one defined instance. The live, staging and development environments of the same installation count together as one instance. The instance can only be changed by agreement.
- Using one plan for further instances breaches the terms and leads to permanent exclusion from the programme. So a plan does not cover several installations, such as separate installations for different clients of an agency. If several websites run in one single installation, however, that is one instance.
- In a Composer installation, you create an access token for the instance and add the dedicated Composer repository at elts.typo3.com.
What does ELTS cost? Since April 2026, the list price for TYPO3 12 has been 3,200 euros per year and instance, and 2,800 euros for versions 10 and 11. Members of the TYPO3 Association get a discount: Silver 25 percent, Gold 30 percent, Platinum 45 percent. Prices can change, typo3.com is authoritative.
What happens after ELTS? Then there are no security updates at all. The version is not updated automatically, and support does not continue for free. Running it is only possible at high risk, and an upgrade is mandatory.
Maintenance: updates and upgrades
Regular updates close security holes, fix bugs and keep the system compatible. They are not only needed when someone wants new features. There are two kinds:
- A patch update, for example from 14.3.6 to 14.3.7, brings bug and security fixes without major changes. The database structure and the backend usually stay the same, and essentially new code is deployed.
- An upgrade to a new major version, for example from 13 to 14, can contain breaking changes. Then extensions, TypoScript, templates and server requirements need adapting, and sometimes editors need training.
In a Composer installation, Composer manages the Core and the extensions. A clean update process looks like this:
- Run the update locally or on the staging environment with Composer, for example with the command composer update.
- Run the upgrade wizards and the database comparison if needed, and test the website.
- Bring the tested state to the live system with a deployment.
The file composer.lock makes sure that exactly the same versions are installed on live as on staging. Updating directly on the live server without tests is risky. Replacing single Core files over FTP or uploading new files into fileadmin is not a way to update. In classic installations without Composer, the Extension Manager in the module “System > Extensions” and the install tool take on similar tasks.
TYPO3 ships tools for a major upgrade in the backend:
- The upgrade wizards in the module “System > Upgrade”. They migrate data to the new format.
- The database comparison, called “Analyze Database Structure” in the module “System > Maintenance”. It compares the database schema with what the Core and extensions expect.
- The scan of extension files, called “Scan Extension Files” in the Upgrade module. It finds calls in the code that are affected by breaking changes or deprecations.
TYPO3 does not adapt third-party extensions automatically, though. Their authors have to do that.
Before a major upgrade you check three things. Are all extensions in use available for the target version? Does the server meet the new requirements, such as the PHP version? Which breaking changes affect your own templates and configuration? An upgrade check in advance shows effort and risks.
The maintenance plan with the client
Seetal's management wants to update “only when needed”. Three arguments speak for a fixed rhythm:
- Small, regular updates are less risky than big jumps after a long break.
- Security holes are exploited quickly once they are published.
- Costs and dates become predictable.
Updates still require testing.
A good maintenance plan combines routine, emergencies and the long term:
- Regular dates for patch updates of the Core and extensions, for example a monthly maintenance window.
- A quick response to security bulletins, that is, the security announcements of the TYPO3 Security Team.
- Timely planning of the next LTS upgrade based on the roadmap.
- Tests on a staging environment and backups before every update.
Key points in brief
- TYPO3 14 needs a web server, PHP 8.2 to 8.5 and a database, plus cron job, SSH, Composer and HTTPS for good operation.
- The documentation recommends in php.ini: memory_limit 256 megabytes, max_execution_time 240, max_input_vars 1500.
- Containers need persistent data outside. Several containers share the database, files, caches and sessions.
- Uncached plugins slow things down. Varnish and a CDN must not deliver personalised pages to everyone.
- TYPO3 14 LTS is 14.3 from 21 April 2026, regularly maintained until 30 June 2029, with ELTS until 30 June 2032.
- The current and the previous LTS are supported, for about three years each.
- ELTS is charged per instance and year, covers exactly one instance and lasts up to three years, four for partners.
- A fixed maintenance plan is safer and more predictable than updates only when needed.
Terms
- LTS
- Long Term Support, a version that is maintained for about three years.
- Sprint release
- Interim version before the LTS, supported only until the next sprint release.
- ELTS
- Paid extension of support by the TYPO3 GmbH, per instance.
- Breaking change
- A change that makes existing code or configuration incompatible.
- Deprecation
- Notice that a function that still works will be removed later.
- Container
- Self-contained runtime environment that bundles an application with its dependencies.
- Varnish
- Reverse proxy cache that stores finished pages in front of the web server.
- CDN
- Network of distributed servers that delivers content close to the visitors.
- Core Web Vitals
- Three Google metrics for loading, responsiveness and visual stability.