WWW4 — web hosting on our own Belgian servers

Drupal hosting on Belgian servers

Drupal runs with us in a Belgian data center, with a current PHP version, its own database and the ability to run tasks at fixed times. SSL, daily backups and DDoS protection are included. For a Drupal site managed with Composer or needing its own services, a managed VPS is the better foundation.

Drupal is more powerful than most content management systems and asks for that in return: more memory, a cron that actually runs and, depending on how you manage the site, access to the server itself. Here is what to watch.

What Drupal asks of its environment

A current PHP version

Drupal moves ahead on PHP versions and drops older ones sooner than other systems. You set the version per site, so you can keep up.

More memory than average

A Drupal site with many modules needs noticeably more working memory per request than a simple business site. Pick the plan accordingly, or move up to a VPS.

A reliable cron

Drupal relies on periodic tasks for search indexing, cleanup and update notices. If that cron does not run, the site degrades gradually without a clear error.

Composer-based management

If your site is built with Composer, that process does not belong on a shared environment. Build locally or on your own server and publish the result.

Which environment does Drupal belong on?

A simple Drupal site runs fine on shared hosting. As soon as you work with Composer, run your own services or manage a heavier site, a managed VPS is the right base — you keep root access, we keep an eye on the server.

What is a VPS?

What most often goes wrong with Drupal

Postponing a major version jump

Drupal major versions take work. The longer you wait, the bigger the jump and the more modules have disappeared in the meantime. Plan it instead of enduring it.

A cron that stalls

If search shows stale content or update notices go quiet, first check whether the cron is still running.

File permissions after a migration

After a move, permissions on the files directory are sometimes wrong: uploads fail, or everyone can reach them. Check that right after the transfer.

Frequently asked questions about Drupal hosting

A simple Drupal site does. As soon as you work with Composer, run your own services or manage a module-heavy site, a managed VPS is the better base: more memory per request and root access when you need it.
Drupal assembles a page from many separate parts, and every module takes part in that. On a site with dozens of modules, memory use per request runs noticeably higher than on a simple business site.
Yes. Drupal relies on periodic tasks for search indexing, cleanup and update notices. If that cron does not run, the site degrades gradually without a clear error - check it first when search shows stale content.
Build your site locally or on your own server and publish the result; a shared environment is not a build environment. If you work entirely with Composer, a VPS is the right choice.
Drupal major versions take work, and the longer you wait the bigger the jump. Plan an upgrade instead of enduring it, and check in advance which modules still exist in the new version.
Yes, if you respect the order: transfer and test on the new server first, only then switch the DNS. After the move, pay particular attention to the permissions on the files directory - with Drupal that is what goes wrong most often.
Drupal moves ahead on PHP and drops older versions sooner than other systems. Check the documentation for your Drupal version to see which PHP versions were tested and set that; with us you can do so per site.
Trust Guard Security Scanned
Call us
Send an email