Written by
Founder & CEO, Gspikes
I own and run Gspikes, the agency I founded in 2018. Before going all-in, I led SEO at Chain Reaction — one of the region's largest digital agencies — and shipped production code at Orange and Forbes. Everything published here comes from projects I've personally built, migrated, or ranked.
Last updated · August 2026
About once a month someone brings us a Drupal site that’s “slow and keeps going down,” and the diagnosis takes one look at the hosting invoice. Drupal is a professional tool with professional infrastructure needs — it will technically boot on a $5 shared plan, the way a truck will technically drive on bicycle tires.
Here’s what it actually needs, what each real option costs, and how to size the decision without overbuying.
What modern Drupal requires
- A current PHP version with headroom. Modern Drupal tracks modern PHP closely. Hosting that lags PHP releases eventually blocks your Drupal updates — which blocks your security updates, and now the cheap host is a security decision.
- Composer-based deployment. Drupal is built and updated through Composer and Git. If the host’s workflow is “upload files through a control panel,” it’s disqualified for anything serious — not as snobbery, but because your patch cadence depends on a deploy pipeline.
- A real database allocation. MySQL/MariaDB with adequate memory. Shared hosts oversell database performance harder than anything else, and Drupal’s entity queries feel it first.
- Memory and process headroom. Cron, migrations, cache rebuilds, and big editorial saves need PHP memory and execution time that budget tiers cap aggressively. This is why cheap-hosted Drupal “randomly” white-screens during routine tasks.
The caching stack is half the performance story
Two identical Drupal sites can differ five-fold in feel purely on caching. The full stack, bottom to top: opcode caching (free, standard), Redis or Memcached for Drupal’s internal caches, Drupal’s own page cache and dynamic-page cache configured properly, a reverse proxy or LiteSpeed/Varnish layer, and a CDN at the edge. None of this is exotic — but only some hosting tiers let you run all of it, and that difference matters more than raw CPU specs. When we take over hosting-troubled sites, configuring this stack correctly is usually the fix, not a bigger server.
The tiers, priced honestly
| Tier | Monthly cost | The honest verdict |
|---|---|---|
| Shared hosting | $5–$25 | Fine for a hobby blog. For a business Drupal site: slow pages, capped processes, blocked updates. Avoid. |
| Unmanaged VPS (you administer it) | $20–$100 | Great specs per dollar — if someone on your team genuinely does server administration, patching, and 3 a.m. incident response. Most teams only think they do. |
| Managed VPS / managed cloud | $50–$400 | The sweet spot for most business sites: real resources, the caching stack available, someone else patching the OS. |
| Drupal PaaS (Pantheon, Platform.sh, Acquia) | $50–$2,500+ | Best developer workflow and Drupal-tuned performance; you pay for the polish. The full comparison is in the Acquia alternatives piece. |
| Enterprise / compliance hosting | $2,000+ | For FedRAMP, healthcare, and audit-heavy environments where the certification is the product. |
How to size it without overbuying
Match the tier to what’s actually at stake, not to traffic vanity. A lead-generating business site earning its keep belongs on managed hosting from ~$50–150/month — the cost of one lost lead per quarter. An institution with compliance obligations belongs on PaaS or enterprise tiers because the audit trail is the requirement. And if you’re paying enterprise prices without enterprise requirements, that’s budget that should be funding development or content instead.
Two adjacent notes worth the click: hosting is one line in the real total cost of running Drupal — patching, module updates, and support are the rest, mapped out in the maintenance cost guide. And if you’re still on Drupal 7, don’t invest in new hosting for it — that money belongs in the migration, and the new platform decision comes with it.
We include hosting architecture in every project and support plan — stack selection, the caching layers, monitoring, and the migration onto it — as part of our Drupal development services. If your current site feels slower than it should, request a free performance review: a senior engineer will tell you whether the problem is the hosting, the caching config, or the code, and what fixing it costs. It’s usually cheaper than the next tier up.
