Drupal hosting designed around Composer and Drush

Recent Drupal releases feel completely at home here. Both Drupal 10 and Drupal 11 run smoothly on our modern PHP 8.x stack with OPcache, and 9.x installations are still supported while you work out an upgrade timeline. Since every install and update goes through Composer, you're the one choosing which core release and which contrib module versions run on your account, and you move to a new major version whenever it suits your project rather than on a forced schedule. Older Drupal 7 sites continue to function as well, though that branch is past its end-of-life date, so we'd suggest moving to 10 or 11 — a switch our team can carry out for you at no cost. Full SSH access, as many as 100 MySQL/MariaDB databases, and backups taken automatically every day make it easy to test an upgrade on a duplicate first, so a major version jump never has to be a gamble on your live site.

Yes — Composer comes preinstalled and works over SSH right away, matching exactly how the Drupal project recommends building a site today. A single command pulls in Drupal core, contrib modules, themes and their underlying Symfony components, while your composer.json and composer.lock stay fully in your hands, keeping every build repeatable and every dependency locked to a known version. That keeps updates simple: run one command to bump core or a module, check what changed, then commit the lock file. Combine Composer with the Git access bundled into every plan and you end up with a code-first workflow rather than shuffling files by hand. Prefer to skip the terminal? Our team can install or migrate a Composer-managed Drupal site on your behalf and hand it back ready to run.

It certainly does. Every plan gives you complete SSH access, so installing Drush through Composer and running your entire site from the command line is straightforward. Clear caches right after a deploy, push database updates with one command, move configuration between environments, create accounts, reset passwords or generate one-time login links — none of it requires the admin screen. Drush saves real time on content-heavy Drupal builds, where clicking through menus for routine upkeep gets old fast. Since Git and Composer are also part of the package, you can script a repeatable deployment: fetch the latest code, run composer install, apply database updates and import configuration, all in order. Automatic daily backups run in the background the whole time, so an unexpected command result is just a rollback away. Our support team is also available around the clock if something looks unusual.

Drupal executes a lot of code on every single request, so what's underneath really counts. Your account sits on pure NVMe SSD storage running a current PHP 8.x build with OPcache, which holds compiled code in memory rather than recompiling it on each visit. LiteSpeed caching alongside HTTP/2 delivers cached pages and static files straight out of memory, and Drupal's own object and page caches stack cleanly on top, so signed-in dashboards and content-heavy pages stay responsive. Up to 100 MySQL/MariaDB databases plus phpMyAdmin give you room to index and tune queries as your content library expands. Because CPU and RAM increase with each tier, jumping to a bigger plan takes a couple of clicks when traffic rises instead of forcing a rebuild elsewhere. What you get is a quick editorial experience for your team and fast page loads for readers, even on module-heavy builds.

Drupal's security team is one of open source's best, and keeping current is your single biggest safeguard. We try to make that easy. A web application firewall and network-level DDoS protection sit ahead of every account, a free auto-renewing SSL certificate keeps traffic encrypted, and backups run automatically each day so you always have a recent point to restore to. When a Drupal security advisory drops, applying the fix through Composer usually takes one command against core or the module involved, with a fresh backup already sitting there, then a Drush cache clear finishes the job. Since dependencies stay pinned in composer.lock, you can review precisely what an update touches before it goes live, and try it on a duplicate site first using SSH. If something goes sideways, our team is on call 24/7 to help restore or roll back, so patching quickly never has to feel like a risk.

Yes, and the managed transfer costs nothing. Once you've signed up, open a support ticket with details on where your Drupal site currently lives; our team copies over your files, database, settings and media library, rebuilds everything on our stack, and confirms modules, views and cron jobs all behave correctly before your visitors notice a thing. Most transfers wrap up in about 24 hours. We coordinate the final DNS change with you so the switch happens without downtime, and your previous host stays untouched until you've confirmed the new copy looks right. Sites managed through Composer move especially smoothly since the entire build is defined in code. Planning to jump to a newer Drupal release or PHP 8.x version at the same time? Let us know and we'll build that into the plan. Daily backups kick in immediately, so your transferred site is protected from the very first day.