Cloud WordPress hosting is one of two paths: cloud VMs (AWS, GCP, Azure, DigitalOcean) with full control and full ops burden, or a managed alternative (RunxBuild, Cloudways, Pressable, WP Engine) with less control and less ops. The right pick: managed if you have a budget and want zero ops, cloud VMs if you want full control and have ops time. Most agencies use both - cloud VMs for high-traffic or custom sites, managed for standard client sites.
Table of contents
- The two paths
- The cloud VM options
- The managed alternatives
- The cost comparison
- The features that matter
- How this fits the rest of the stack
- FAQ
The two paths
Path 1: cloud VMs (AWS, GCP, Azure, DigitalOcean, Vultr, Linode, Hetzner). You run WordPress on a VM, you manage the OS, the database, the backups, the updates. Full control, full ops.
Path 2: managed (RunxBuild, Cloudways, Pressable, WP Engine, Kinsta). The host runs the OS, the database, the backups, the updates. Less control (you cannot tweak nginx.conf), less ops (you do not patch WordPress).
The right pick: managed if you have a budget and want to focus on the content, not the infrastructure. Cloud VMs if you have ops capacity, want to learn the stack, or need features the managed hosts do not offer (custom PHP extensions, specific database version, etc.).
The cloud VM options
AWS (EC2 + RDS for MySQL + S3 for media + CloudFront CDN). The most powerful, the most complex. The team that already has AWS infra uses it; the team that does not find it overwhelming for a single WordPress site.
GCP (Compute Engine + Cloud SQL + Cloud Storage + Cloud CDN). Similar to AWS. The team that uses GCP for other apps uses it for WordPress too.
Azure (VMs + Azure Database for MySQL + Blob Storage + Azure CDN). The team that is on Microsoft uses it.
DigitalOcean (Droplets + Managed MySQL + Spaces + CDN). The team that wants cloud simplicity uses it. $6-24/month for a small WordPress site.
Vultr, Linode, Hetzner - the smaller, cheaper alternatives. The team that is budget-conscious uses one of these. Same model as DO, often slightly cheaper or faster in specific regions.
The managed alternatives
RunxBuild - the team’s platform. WordPress one-click install, automatic backups, scaling, monitoring. The team that already uses RunxBuild has it here.
Cloudways - managed cloud. Pick your underlying cloud (Vultr, DO, Linode, AWS, GCP), they run it. The team that wants managed with a choice of cloud uses Cloudways.
Pressable - managed WordPress on WordPress.com infrastructure. Premium, white-label available, agency-friendly. The team that wants the most WordPress-native managed host uses Pressable.
WP Engine - the most polished managed WordPress. Premium pricing, agency features, the most mature platform. The team that has the budget for it uses WP Engine.
Kinsta - managed Google Cloud. Premium, fast, developer-friendly. The team that wants GCP under the hood uses Kinsta.
The cost comparison
Small site (1-10k visits/month):
-
Cloud VM: $6-30/month (DO droplet, AWS t3.micro, etc.) + $15-30/month for managed MySQL + $5-10/month for object storage.
-
Managed: $15-50/month (entry tier of most managed hosts).
Medium site (10k-100k visits/month):
-
Cloud VM: $50-200/month for a 2-4 vCPU VM + $50-100/month for managed MySQL + CDN $20-50/month.
-
Managed: $50-200/month (mid tier).
Large site (100k+ visits/month):
-
Cloud VM: $200-1000+/month, with horizontal scaling, read replicas, CDN, etc.
-
Managed: $200-1000+/month, usually enterprise tier.
The team that is at the small end saves money with cloud VMs and accepts the ops burden. The team that is at the medium or large end usually gets more value from managed (less ops, more features).
The features that matter
Automatic updates - WordPress core, themes, plugins. The team that has automatic updates for everything patches within hours of a CVE.
Automatic backups - daily backups, point-in-time recovery. The team that has a backup but has not tested the restore has a backup that may or may not work.
Staging environments - one-click clone to a staging URL. The team that has staging tests major updates before pushing to prod.
CDN - Cloudflare, Fastly, or the host’s own CDN. The team that has a CDN serves static content from the edge, the origin handles dynamic.
Monitoring - uptime monitoring, performance monitoring, security monitoring. The team that has monitoring finds out about issues before the client does.
FAQ
Is managed hosting worth the cost?
For most teams, yes. The team that does not want to patch WordPress, manage backups, debug server issues, and tune performance pays $20-50/month for someone else to do it. The team that has the ops capacity saves the money.
Can I move from managed to self-hosted?
Yes - most managed hosts have export tools. The team that wants to leave a managed host uses the same migration plugin approach as a self-hosted-to-self-hosted move.
What is the cheapest cloud WordPress option?
Hetzner or DigitalOcean, ~$5-10/month for a small site. The team that is on a tight budget uses one of these and accepts the ops burden.
Should I use a CDN with WordPress?
Yes for any site with global visitors. Cloudflare’s free tier works for most small sites. The team that has visitors in multiple continents uses a CDN; the team that has only local visitors can skip it.
What is the difference between Cloudways and Pressable?
Cloudways is managed cloud (you pick the underlying cloud provider). Pressable is managed WordPress on WordPress.com infrastructure (no choice of cloud). The team that wants the choice uses Cloudways; the team that wants the most WordPress-native managed host uses Pressable.
How this fits the rest of the stack
For a sense of what the full project costs before it commits, the RunxBuild hosting calculator shows the line items together. The API, the database, the storage, the worker, the bandwidth - each one is a separate number, and the team’s mental model for the platform is the sum of those numbers.
Useful related references: