Cloudways Pricing: What I Actually Paid Migrating My Site, Mistakes Included

A 30-day tracked experiment

A reader messaged me asking one specific question: “what does Cloudways actually cost, after everything, not the homepage number.” I didn’t have a confident answer. I’d read the pricing page, I’d read other people’s reviews, and none of it matched what I suspected the real bill would look like once add-ons, currency conversion, and my own bad decisions were factored in. So I stopped guessing and actually tracked it. This is that 30 days, dollar for dollar.

A note before any of the numbers below: Cloudways bills globally in US dollars, there’s no Australian pricing option. Every figure on this page is USD, labelled that way throughout rather than just once here, since it’s easy to skim past a single disclaimer and assume AUD. At the time of writing, roughly 1 USD = 1.43 AUD, so a US$11/mo plan works out to somewhere around A$16 once converted, plus whatever your own bank charges on the international transaction.

The Problem: I Didn’t Actually Know What I’d Pay

Here’s what was actually broken, and it wasn’t a technical problem, it was an information problem. I’d already decided, for scalability reasons rather than because my current host was failing me, that Cloudways was worth migrating to. What I hadn’t done was work out what that decision would genuinely cost month to month, once you got past the “starting from US$11” headline number every review, including my own first draft of this page, tends to lead with.

That mattered for a boring but real reason: budgeting. I run more than one site off the same infrastructure decisions, and “starting from” pricing that turns into something 40% higher once you’ve added the things you actually need isn’t a rounding error, it’s a real monthly line item I have to plan for.

Cloudways pricing specifically has a reputation, deserved or not, for being harder to pin down than a flat shared-hosting plan, because it’s genuinely two costs bundled into one number: raw cloud server cost plus Cloudways’ own management layer on top. I wanted the real number, not the marketing one.

What I’d Tried Before, and Why It Didn’t Work

My first attempt at answering this was the obvious one: read the pricing page carefully, read a handful of other Cloudways reviews, and try to mentally reconstruct a realistic monthly total. That approach failed for a specific reason. Every published breakdown I found, including plenty of well-meaning ones, quoted the base server price and stopped there, treating add-ons as a footnote rather than something that actually shapes the real bill.

None of them had tracked an actual account for a full billing cycle and reported what genuinely showed up on the invoice. That gap, between “here’s the pricing page” and “here’s what I actually paid,” is exactly what triggered the experiment below. If nobody had published the real number, the only way to get one honestly was to run the test myself and report it, failures included.

The Experiment: Step by Step

I treated this like an actual test, not a purchase. One pilot site first, a full 30 days of tracking every charge that hit the account, and a deliberate decision to try the optional add-ons I was curious about rather than skip them just because I suspected they weren’t necessary. Guessing they weren’t worth it isn’t the same as testing it.

Step 1: Choosing the Provider (Diagnostic Intent)

Cloudways doesn’t own servers, it partners with five cloud infrastructure providers, DigitalOcean, Vultr, Linode, AWS, and Google Cloud, and layers its dashboard, security, and support on top of whichever one you pick. That’s the actual thing driving Cloudways pricing variation, not Cloudways’ own fee, which stays roughly consistent, it’s which underlying provider you choose.

I picked DigitalOcean Standard, ~US$11/mo, deliberately not the fastest option on the table. AWS and Google Cloud exist for genuinely large, enterprise-scale applications, not a small business site or a growing blog, and I didn’t want the experiment’s honesty compromised by starting on infrastructure nobody in my actual situation would realistically choose.

Step 2: Sizing the Server (Informational Intent)

Entry-tier specs, 1GB RAM, 1 core, 25GB SSD, sound small on paper. For a straightforward WordPress site without huge existing traffic, they’re genuinely adequate, not a compromise. I resisted the urge to size up “just in case,” since that urge is exactly how a US$11/mo decision quietly becomes a US$24/mo one before you’ve proven you need the extra headroom.

Step 3: Migrating a Pilot Site First (Solution Intent)

Rather than moving griffithpromarketing.com straight over, I migrated a smaller, lower-stakes site in my own stack first. If something in the pricing or the migration process went sideways, I wanted to find out on a site where a mistake cost me an afternoon, not my main source of traffic.

Step 4: Tracking Every Dollar for 30 Days

This was the actual experiment. I opened a spreadsheet, logged the base plan charge on day one, and checked the Cloudways billing dashboard every few days rather than waiting for a single end-of-month invoice to summarise everything for me. Anything that showed up got a line in the ledger, with a note on why it was there.

What Changed First, Even Before Anything Else Moved

The very first thing I noticed had nothing to do with the invoice. Time to first byte dropped noticeably within the first week on the pilot site, a real, measurable improvement in raw server response. Search rankings, predictably, didn’t move at all in that same window.

I want to be honest about why: I already knew from a separate investigation that TTFB wasn’t actually my bottleneck going in, render-blocking CSS was. So a faster server fixed a problem I didn’t have yet, while the problem I did have sat untouched. That’s not a hosting-cost issue, it’s a sequencing lesson: infrastructure spend and content/structure fixes solve different layers, and paying for one doesn’t substitute for doing the other.

The Add-On That Didn’t Help: Cloudflare Enterprise CDN

Here’s the honest failure, the part most pricing pages quietly skip because it doesn’t sell anything. Cloudways offers a Cloudflare Enterprise CDN add-on, roughly US$5/mo, and I added it deliberately to test whether it was worth the recurring cost rather than assuming either way.

That’s a real, specific example of an add-on that looks reasonable on the pricing page and turns out to be dead weight for a specific, ordinary use case, a regionally concentrated small business audience rather than a global one. If your traffic is genuinely global, this same add-on might earn its keep. Mine wasn’t, so it didn’t.

The Other Mistake: Premium Support I Never Used

Second honest admission. Migration anxiety got the better of me in week one, and I paid for a month of Cloudways’ premium phone support, priced between US$100 and US$500/mo depending on the tier, as a safety net in case something went badly wrong during the pilot migration.

The Real Ledger: What 30 Days Actually Cost

Here’s the actual tracked total for Cloudways pricing on this specific pilot, not the theoretical entry number, the real invoice-by-invoice figure with every add-on I tested included and then removed where it didn’t earn its place.

Month one cost US$116 once every experiment I ran is counted honestly. The ongoing, steady-state monthly cost for this specific pilot site, once I’d actually tested and removed what didn’t earn its place, landed almost exactly on my original hypothesis: roughly US$11-14/mo base, no CDN, no premium support. The hypothesis was right about the destination and wrong about assuming I’d get there without spending on a couple of things I didn’t end up needing.

What’s Actually Included That Surprised Me

Not everything in this experiment was a mistake. A few inclusions turned out to be genuinely worth more than I expected going in, and none of them cost extra.

That last one is worth pausing on, since it directly affects your monthly cost if you’re running more than one site, which I am. Pricing is per-server, not per-site, so a single server can host griffithpromarketing.com alongside the pilot site and anything else I add later, no separate fee stacked on per domain the way some hosts structure it.

Object Cache Pro is worth flagging too, it comes bundled free on 4GB+ servers, a caching tool that normally costs around US$95/mo bought separately. My pilot server wasn’t large enough to include it yet, but it’s a real, non-trivial saving worth factoring in once a site’s traffic justifies sizing up.

The Annual Billing Question

Cloudways offers roughly 25% off for paying annually instead of monthly, DigitalOcean’s US$11 becomes roughly US$8.25/mo, Vultr and Linode’s US$14 becomes roughly US$10.50/mo. I deliberately didn’t commit annually during this 30-day window, and that turned out to be the right call for a reason I hadn’t fully appreciated going in.

A Decision Framework, Based on What Actually Happened

If you’re weighing Cloudways plans for your own site rather than taking my numbers as gospel for yours, here’s the actual test I’d suggest running, based on what worked and what wasted money in mine. Cloudways pricing rewards testing over guessing, in both directions, mine turned out cheaper on the base tier than I feared and more expensive in month one than I hoped, both true at once.

Run a real pilot before committing annually

One month on the entry tier, tracked honestly, tells you more about your real Cloudways monthly cost than any pricing page comparison will. Resize before you lock in the annual discount, not after.

Test add-ons, don’t assume them either way

I assumed the CDN would help and it didn’t. You might assume it won’t help and be wrong, if your audience is genuinely global rather than regionally concentrated like mine. Test it for two weeks with real before-and-after numbers instead of guessing in either direction.

Separate infrastructure spend from content and speed fixes

A faster server is a real, immediate, measurable thing. It is not automatically better rankings. If your actual bottleneck is somewhere else entirely, structure, schema, render-blocking assets, paying more for hosting won’t reach it. Know which problem you’re actually solving before you spend on solving it.

Don’t buy anxiety insurance you haven’t priced properly

Premium support at US$100+/mo is a real option for a genuinely complex migration. It wasn’t the right call for mine, and admitting that after the fact is more useful to you than pretending every dollar I spent during this test was well spent.

What I’d Do Differently

Skip the premium support trial entirely and lean on standard support first, upgrading only if a specific issue actually demands it, not preemptively. Test the CDN add-on with real traffic-source data in hand before switching it on, rather than switching it on and checking afterward.

Cloudways’ own dashboard shows a rough geographic breakdown of visitors, and I should have pulled that before spending a single dollar on infrastructure meant to serve a distant audience I didn’t actually have. And track the ledger from day one the way I eventually did, instead of only starting properly a week in, since I’m genuinely unsure what the first week cost me in charges I didn’t note down carefully enough to include here with confidence.

One more thing I’d change: I’d set a hard three-day rule for any add-on decision made out of anxiety rather than data. The premium support purchase happened at 11pm the night before migrating my pilot site, precisely the moment I was least equipped to judge whether I actually needed it.

A specific, low-stakes technical question sitting unresolved for a few hours isn’t an emergency, and treating it like one is how a US$100 line item ends up on an invoice for a problem that never actually arrived.

Common Questions About Cloudways Pricing

Does Cloudways have hidden costs?

Not hidden exactly, more like under-tested. This is the real answer to the Cloudways hidden costs question I get asked most often: nothing on the pricing page is deliberately obscured, but most published reviews quote the base server price and never track a real account long enough to report what add-ons actually cost once you’re curious enough to try them.

My month one total, US$116 against an ongoing US$11, is the gap between the sticker price and what a genuinely tested Cloudways pricing account can rack up.

Is Cloudways cheaper than shared hosting?

Not necessarily, and it’s not really the right comparison. The entry-tier Cloudways monthly cost, roughly US$11-14, sits close to a mid-tier shared hosting plan in raw dollar terms. What you’re actually paying for isn’t a cheaper server, it’s not having to be your own sysadmin, managed security, backups, and staging environments bundled in rather than sold separately.

Which provider should I actually pick?

For a normal WordPress site without enterprise-scale traffic, DigitalOcean or Vultr, not AWS or Google Cloud. That’s not a hedge, it’s what the entry-price table above shows plainly, AWS and Google Cloud cost roughly three times as much for infrastructure most small business sites won’t come close to needing.

The Actual Takeaway

Cloudways pricing, tracked honestly rather than quoted from the homepage, landed close to the original hypothesis once the mistakes were stripped out: roughly US$11-14/mo for a straightforward WordPress site on DigitalOcean’s entry tier, no CDN, no premium support, unlimited additional sites on the same server as they get added.

Getting there cost more than that in month one, because testing what you don’t need is part of the actual price of finding out what you do. That’s not a flaw in the pricing model, it’s just what an honest experiment costs, and it’s the number nobody else’s review had actually reported.

All prices on this page are USD, since Cloudways bills globally in US dollars with no Australian pricing option. Sourced and accurate at the time of writing, and reflects one tracked 30-day pilot on one specific site, your own numbers may vary with server size, region, and usage. Cloudways uses pay-as-you-go billing and pricing can change, always check the current plans page for the live figure before purchasing, and factor in your own bank’s foreign transaction fee on top of the exchange rate.