TYPO3 Hosting

TYPO3 makes demands of its environment that simple webspace rarely meets. Composer on the server, a matching PHP and database profile, a real cron job, plus a test environment that can be generated from production. We pick the right environment, set it up and, if you want, run your TYPO3 instance for you.

Get expert advice

Official Silver Member of the TYPO3 Association

Why TYPO3 does not run on just any webspace

TYPO3 is an enterprise CMS and behaves like one. It expects a defined environment, and when that environment does not fit, the symptoms look at first like faults in the installation: image processing that breaks off, empty caches, a backend that hangs when you save.

The technical minimum requirements

A PHP version matching the TYPO3 version in use, because every LTS generation has its own window of supported versions.
PHP limits generous enough for memory, runtime and uploads, especially in the backend.
Composer on the server, or a deployment route that rolls out the result. TYPO3 has not been unpacked over FTP for a long time.
An image library such as ImageMagick or GraphicsMagick, because TYPO3 generates image variants server-side.
A real system cron job for the scheduler, which works through indexing, caches and scheduled tasks.
Enough database resources. A grown multi-site network puts noticeable load on the backend.

Deployment instead of moving files around

A TYPO3 installation is managed through Composer these days. Core, extensions and dependencies are declared in a configuration file, and the result is reproducible. What the hosting has to provide is a way to roll that result out, so either SSH access with Composer directly on the server or a deployment route that builds the package elsewhere and transfers it ready. Both work, it just has to be settled beforehand. For a relaunch we pin exactly this down before the implementation starts.

Caching that fits the site structure

TYPO3 comes with its own layered caching system, which can be combined with an upstream cache on the server. With multilingual sites and multi-site networks a lot rides on that configuration. In the bad case visitors are served the wrong language version. We align the cache levels with each other and take personalised areas and form routes out of them.

What we work with

TYPO3 caches configured sensibly rather than maxed out across the board
An optional reverse proxy or server cache for the pages that can be delivered statically
Cache separation by language and domain in multi-site setups
Exceptions for forms, login areas and personalised content
Automated cache clearing in the deployment, so nothing stale survives a release

Staging is part of the setup

TYPO3 projects are rarely small, and updates often touch several languages and sites at once. A staging environment generated from production is therefore the precondition for controlled version updates. We set it up so that it matches production technically, while it stays out of reach of search engines and sends no real email to your customers.

Data protection and the public sector

TYPO3 has always been strong in public authorities and large corporations, and there the way a site is run comes with extra requirements. Server location in Germany or the EU, documented data processing agreements, traceable access and retention rules for backups. In a public tender at the latest, someone asks. We select providers on that basis and document the arrangement, instead of reconstructing it after the fact when it matters. The related question of accessibility under BITV and the BFSG has a page of its own.

Common questions about TYPO3 hosting

Can TYPO3 run on simple shared hosting?

With small sites sometimes, but it gets tight quickly: no SSH access, PHP limits set too low, no real cron job, no staging environment. For productive corporate and public-sector sites we recommend managed hosting with TYPO3 experience or a server of your own, because deployment and maintenance cannot be handled cleanly otherwise.

Can you move an existing TYPO3 installation?

Yes. We take over files, database and configuration, set up Composer and deployment afresh, check the installation fully on the new environment and only then switch DNS and SSL. If the instance is outdated at the same time, we clarify beforehand whether the move should be combined with a version update.

Do you run the servers yourselves?

We work with established hosting partners instead of running a data centre of our own. For our clients that is more reliable and cheaper. Selection, setup, support and monitoring of the environment are on us, so you still have only one point of contact.

What about TYPO3 instances that have run out of support?

Those belong on a supported version soon. If a version update is not possible right away, ELTS bridges the time until the migration, so security updates keep coming. It is a bridge and not a permanent solution.

Ready for your TYPO3 project?

Tell us about your project. We'll get back to you promptly with an honest assessment.

By the way: aceArt is an official Silver Member of the TYPO3 Association.