Drupal hosting: Drupal 10 and 11 deployed from Git | Vallic

Skip to main content

Drupal hosting · Vallic Cloud

Drupal hosting from a company that has built Drupal since 2008.

Drupal 10 and 11 on machines no other customer shares, deployed from Git with drush deploy, with Solr, Varnish and Valkey when the site needs them. One console for environments, backups, your team and support.

On Vallic Cloud

What runs your Drupal site

Machines from €13.75 a month, including 25% VAT

You choose

Runtime

PHP 8.5 8.4 8.3 8.2

Database one of

MariaDB 11.8 11.4 10.11
MySQL 8 8.4 8.0
PostgreSQL 18.6

Cache one of

Valkey 9.1 9.0 8.1 8.0
Redis 8.10 8.6 8.4 8.2
Memcached 1.6

You can add

Reverse proxy

Vinyl Cache (Varnish) 9.1 8.0

Search

Meilisearch 1.55 1.53 1.52
Solr 10.0 9.11 9.10

Time series

InfluxDB 2.9 2.8

Background work

RabbitMQ 4.4 4.3

The default, unless vallic.yaml names another version.

Done for you

Scheduled

Runs drush cron every hour, without a crontab of yours.

Caches

Rebuilds them with drush cache:rebuild from the console, a button rather than a shell.

Kept between releases

web/sites/default/files and private, so a deploy never loses what the site wrote.

Why here

Built around how Drupal deploys.

drush deploy, in Drupal’s order

Database updates, configuration import and the cache rebuild run on the machine once the new release is live. A deploy that fails rolls back to the release before it.

Composer in the build

Dependencies install in a build that has no database. What Composer installed is kept for the next build, which fetches only what changed.

Cron on one machine

However many web servers a site has, cron runs on one of them, so a job never runs twice at once.

Restores that clear the cache

After a backup is restored the platform runs drush cache:rebuild, so nothing cached from the replaced database is served.

Search and caching beside it

Solr for Search API, Varnish in front and Valkey for the cache: on the web machine, or each on a machine of its own.

Support from Drupal developers

The people who answer a ticket build and run Drupal sites for a living.

Our services

Moving a Drupal site here.

Bring the repository and a database dump. Add a vallic.yaml and the settings file from the handbook’s Drupal page, import the database with vallic db import, and deploy. The first deploy is a drush deploy like every one after it.

Rather we did it? Moving Drupal sites is part of what our team does.

Questions

Which versions of Drupal run here?

Drupal 10 and 11, on any of the PHP versions above. vallic.yaml names the version, and that is the one the platform builds.

What changes in my code?

A vallic.yaml at the top of the repository, and a settings file that reads the environment, included last from settings.php. Off the platform it does nothing, so it can be committed.

Do you charge per request or per visit?

No. Machines are billed by the month, and traffic past what a machine includes by the terabyte.

Where can it run?

In any of the platform’s datacentres. The configurator shows each one’s machines and prices before you sign up.

Price your Drupal site.