Composer and Drush, on a stack cut for Drupal

Recent releases are entirely at home. Drupal 10 and Drupal 11 both run on our modern PHP 8.x stack with OPcache, and 9.x installations remain supported while you work out an upgrade timetable. Because every install and update runs through Composer, you decide which core release and which contrib module versions live on your account, and you move to a new major version when the project is ready rather than on somebody else's schedule. Older Drupal 7 sites still function, though that branch is past its end-of-life date, so we would point you towards 10 or 11 — a move our team will carry out at no charge. Full SSH access, as many as 100 MySQL/MariaDB databases and backups taken automatically every day make it straightforward to rehearse an upgrade on a duplicate first, so a major version jump never has to be a bet placed on your live site.

Yes — Composer is preinstalled and works over SSH from the first minute, which matches exactly how the Drupal project recommends building a site today. One command pulls in core, contrib modules, themes and the Symfony components underneath them, while composer.json and composer.lock stay entirely in your hands, keeping every build repeatable and every dependency pinned to a known version. Updates stay simple as a result: run one command to lift core or a module, read what changed, commit the lock file. Combine Composer with the Git access bundled into every plan and the workflow becomes code-first rather than a matter of shuffling files by hand. Would you rather stay away from the terminal? Our team will install or migrate a Composer-managed Drupal site for you and hand it back ready to run.

It does. Every plan carries full SSH access, so installing Drush through Composer and driving the entire site from the command line is straightforward work. Clear caches straight after a deploy, apply database updates with one command, move configuration between environments, create accounts, reset passwords, generate one-time login links — none of it needs the admin screen. On a content-heavy Drupal build that saves real time, because clicking through menus for routine upkeep wears thin quickly. Git and Composer are part of the same package, so you can script a repeatable deployment: fetch the latest code, run composer install, apply database updates, import configuration, in that order. Automatic daily backups run underneath the whole time, which means an unexpected command result is a rollback rather than a crisis. Our support team is reachable around the clock if something looks wrong.

Drupal executes a lot of code on every request, so the platform underneath earns its keep. Your account sits on pure NVMe SSD storage running a current PHP 8.x build with OPcache, which holds compiled code in memory instead of recompiling it for each visitor. LiteSpeed caching with HTTP/2 delivers cached pages and static files straight out of memory, and Drupal's own object and page caches stack cleanly above that, so signed-in dashboards and content-heavy pages stay responsive. Up to 100 MySQL/MariaDB databases plus phpMyAdmin leave room to index and tune queries as the content library grows. CPU and RAM rise with each tier, so a traffic increase means a couple of clicks rather than a rebuild somewhere else. The result is a quick editorial experience for your team and fast page loads for readers, even on module-heavy builds.

Drupal's security team is among the best in open source, and staying current is the single biggest safeguard you have. Our job is making 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 a recent restore point always exists. When an advisory lands, applying the fix through Composer is usually one command against core or the affected module, with a fresh backup already sitting behind you, then a Drush cache clear to finish. Because dependencies stay pinned in composer.lock, you can read exactly what an update touches before it reaches production, and rehearse it on a duplicate site over SSH. If it goes sideways, our team is on call 24/7 to help restore or roll back, so patching promptly never has to feel risky.

Yes, and the managed move costs nothing. Once you have signed up, open a ticket telling us where the site currently lives; our team copies the files, database, settings and media library, rebuilds everything on our stack, and checks that modules, views and cron jobs all behave before your readers notice a thing. Most transfers finish in about 24 hours. We agree the final DNS change with you so the switch happens without downtime, and your previous host stays untouched until you have confirmed the new copy looks right. Sites already managed through Composer travel especially smoothly, since the whole build is described in code. Planning to step up to a newer Drupal release or PHP 8.x version at the same time? Tell us and we will fold that into the plan. Daily backups start immediately, so the transferred site is protected from its first day here.