Drupal VPS HostingComposer, Drush and Redis Ready
Modern Drupal is built and updated with Composer and managed with Drush, which shared hosting rarely supports well. We install Drupal with PHP-FPM, your database, Redis and HTTPS on a hardened KVM VPS, ready for your site and modules.
Full root & SSH NVMe storage Daily backups Anti-DDoS 99.9% uptime SLA 11 locations
-
Root and SSH access
Composer, Drush and cron without limits.
-
Reserved vCores and RAM
PHP workers for editors and visitors.
-
NVMe storage
Fast database queries and file reads.
-
Daily backups
Automatic backup of the previous 24 hours.
Why Run Drupal on a VPS
Drupal sites are often large, multilingual and connected to other systems. They need Composer, the command line and caching that a shared account cannot offer.
-
A Composer-managed codebase
Install and update Drupal core and modules with Composer, the way Drupal recommends.
-
Drush for everything else
Database updates, config imports, cache rebuilds and cron from the command line.
-
Redis caching
Move Drupal's cache bins to Redis to take load off the database.
-
PHP set for Drupal
Memory, OPcache and upload limits sized for large sites and media.
A Drupal Production Stack
A PHP stack with a cache in front of the database and the command-line tools Drupal relies on.
Request from a browser or app (HTTPS)
-
Web server
NGINX or Apache
Serves the web/ directory and passes requests to PHP-FPM.
-
PHP runtime
PHP-FPM + OPcache
Runs Drupal core and contributed modules.
-
Cache
Redis
Cache bins and locks outside the database.
-
Database
MySQL, MariaDB or PostgreSQL
Content, configuration and users.
-
CLI
Composer + Drush
Builds, updates, configuration sync and cron.
Worth knowing
- Point the web root at web/, keeping vendor/ and configuration outside it.
- Keep private files outside the web root and set the private file path in settings.php.
- Use configuration management to move changes from staging to live.
- Check which PHP version your Drupal release requires before upgrading PHP.
What You Can Run
-
Large content sites
Thousands of pages with structured content types.
-
Multilingual sites
Drupal's built-in language and translation modules.
-
Intranets and portals
Role-based access and integrations with other systems.
-
Headless Drupal
JSON:API in core for decoupled front ends.
-
Multisite
Several sites from one codebase.
-
Drupal Commerce
Online stores built on Drupal.
VPS Plans for Drupal
VPS-1 runs a typical Drupal site. Large sites with many modules, editors or languages usually start on VPS-2.
VPS-1
Small websites, APIs, bots and development servers.
- 2 vCores
- 4 GB RAM
- 40 GB NVMe
- 500 Mbps
- Full root and SSH access
- Free initial stack installation
- Server hardening and firewall setup
- Daily backup of the previous 24 hours
- Unlimited traffic *
- Anti-DDoS protection
- Dedicated IPv4 and IPv6
- KVM virtualisation
VPS-2
Production apps, WordPress and online stores.
- 4 vCores
- 8 GB RAM
- 75 GB NVMe
- 1 Gbps
- Full root and SSH access
- Free initial stack installation
- Server hardening and firewall setup
- Daily backup of the previous 24 hours
- Unlimited traffic *
- Anti-DDoS protection
- Dedicated IPv4 and IPv6
- KVM virtualisation
VPS-3
Busy stores, SaaS products and several projects.
- 6 vCores
- 12 GB RAM
- 100 GB NVMe
- 2 Gbps
- Full root and SSH access
- Free initial stack installation
- Server hardening and firewall setup
- Daily backup of the previous 24 hours
- Unlimited traffic *
- Anti-DDoS protection
- Dedicated IPv4 and IPv6
- KVM virtualisation
VPS-4
High-traffic apps, large databases and agencies.
- 8 vCores
- 24 GB RAM
- 200 GB NVMe
- 3 Gbps
- Full root and SSH access
- Free initial stack installation
- Server hardening and firewall setup
- Daily backup of the previous 24 hours
- Unlimited traffic *
- Anti-DDoS protection
- Dedicated IPv4 and IPv6
- KVM virtualisation
* Unlimited traffic in Europe and North America. In Mumbai, Singapore and Sydney a monthly allowance applies (VPS-1 500 GB, VPS-2/VPS-3 1 TB, VPS-4 3 TB), then speed is limited to 10 Mbps until the next month.
Which Plan for Your Drupal Site
Drupal uses more memory per request than lighter CMSs; the number of modules and logged-in editors drives the plan.
| Workload | Start with | Why |
|---|---|---|
| Small site or staging | VPS-1 2 vCores · 4 GB RAM | Drupal, MariaDB and Redis with room to spare. |
| Busy site with many modules | VPS-2 4 vCores · 8 GB RAM | More PHP workers and database memory. |
| Large multilingual or commerce site | VPS-3 6 vCores · 12 GB RAM | 6 vCores and 12 GB RAM. |
| Multisite or several large sites | VPS-4 8 vCores · 24 GB RAM | 24 GB RAM and 200 GB NVMe. |
A starting point, not a limit: every plan upgrades in place, keeping your data, IP address and configuration.
Drupal on Shared Hosting or a VPS?
Small Drupal sites can live on shared hosting; real projects need Composer, Drush and Redis.
| Feature | Shared hosting | Drupal VPS |
|---|---|---|
| Composer | Often unavailable or limited | Full |
| Drush | Limited or none | Full |
| Redis | Rarely available | Installed at handover |
| PHP limits | Capped by the host | Your settings |
| Server administration | Done by the host | Yours, after our free setup |
| Best for | Small brochure sites | Large or complex Drupal sites |
| Explore Shared hosting | See Plans |
Deploying Drupal Changes
The usual sequence after pushing code; drush deploy runs the last three steps in one command.
-
Update code
Pull your changes and install dependencies.
-
Run database updates
Applies update hooks from core and modules.
-
Import configuration
Brings live in line with exported config.
-
Rebuild caches
So the new code and config take effect.
# 1. Update code
cd /var/www/drupal && git pull
composer install --no-dev
# 2. Run database updates
vendor/bin/drush updatedb -y
# 3. Import configuration
vendor/bin/drush config:import -y
# 4. Rebuild caches
vendor/bin/drush cache:rebuild
Example commands; adjust names, paths and versions to your project. Deploying and maintaining your application is yours to do (or ask us for a quote).
Installed and Secured Before You Log In
The VPS is unmanaged: after handover the server is yours to run. Before that, our engineers do the first setup once, free, so you start from a hardened server with Drupal in place.
-
Choose a plan and location
Pick the resources you need and the datacentre closest to your users.
-
Tell us your Drupal setup
Versions, database and domain: at order or right after.
-
We install and secure it
Server hardened, Drupal installed and tested, HTTPS on your domain.
-
You take over with root
SSH access to a working server, ready for your code and data.
Your Drupal stack
- NGINX or Apache configured for Drupal's web/ directory
- PHP-FPM with OPcache and the extensions Drupal requires
- MySQL, MariaDB or PostgreSQL with a database for the site
- Composer, Drush and a cron job
- Redis for caching, and Drupal on your domain with HTTPS
Yours to run after handover
- Ongoing server administration
- Application maintenance and updates
- Debugging your code
- Migrating existing sites or data
Not included in the free setup, but we can quote for it. No control panel by default: CloudPanel, HestiaCP or Virtualmin on request at no cost; cPanel and Plesk need their own licence.
Platform Specs and Locations
The same KVM platform on every plan; only the CPU, RAM, storage and port speed change.
| Virtualisation | KVM with reserved vCores and RAM |
|---|---|
| Storage | NVMe SSD on every plan |
| Network | Dedicated IPv4 and IPv6, 500 Mbps to 3 Gbps per plan |
| Operating systems | Ubuntu 26.04, 24.04 and 22.04 LTS · Debian 13, 12 and 11 · AlmaLinux · Rocky Linux · Fedora · FreeBSD |
| Access | Full root over SSH, key-based login |
| Backups | Automatic daily backup of the previous 24 hours; snapshots and longer retention on request |
| Protection | Always-on anti-DDoS mitigation |
| Availability | 99.9% uptime SLA |
Secured before we hand it over
- Non-root sudo user created for daily work
- SSH key login, password login for root disabled
- Firewall (UFW) open only for the ports you use
- Fail2ban blocking repeated login attempts
- Automatic security updates enabled
- Free Let's Encrypt SSL on your domain
- Timezone, swap and hostname configured
Asia-Pacific
- Mumbai
- Singapore
- Sydney
Europe
- London
- Limburg
- Roubaix
- Gravelines
- Strasbourg
- Milan
- Warsaw
North America
- Beauharnois
Availability per location changes with demand; we confirm your location before setup. In Mumbai, Singapore and Sydney each plan includes a monthly traffic allowance (VPS-1 500 GB, VPS-2 and VPS-3 1 TB, VPS-4 3 TB); beyond it, speed is limited to 10 Mbps until the next month.
Who a Drupal VPS Suits
-
Drupal developers and agencies
Composer, Drush and Git deploys on a server you control.
-
Organisations with large sites
Universities, publishers and companies with complex content.
-
Teams leaving shared hosting
Sites that outgrew shared limits and tooling.
Security and Performance for Drupal
Security
- Apply Drupal security releases promptly; they are usually published on Wednesdays.
- Set trusted_host_patterns in settings.php.
- Keep settings.php read-only and secrets out of version control.
- Remove modules you do not use.
Performance
- Enable the internal page cache and dynamic page cache.
- Store cache bins in Redis.
- Aggregate CSS and JavaScript.
- Run cron from the system instead of on page requests.
Questions Before You Deploy
Not covered here? Ask an engineer before you order.
Run Drupal on Its Own Server
Choose a plan and we hand over Drupal with Composer, Drush, Redis and HTTPS, ready for your modules.