When we launched Cloudways Autonomous, we set out to solve a problem that had frustrated WordPress users for years: easy scalability without complex infrastructure management or contacting support.
Traditional managed hosts handle traffic growth by forcing you to upgrade to larger plans, often 5–10x more expensive, even if you only need that capacity occasionally. The alternative (managing your own scalable infrastructure) requires DevOps expertise most teams don’t have or want to maintain.
We built Cloudways Autonomous to be truly managed: handling both the infrastructure and the scaling to accommodate the traffic automatically. You hand off your website and everything is taken care of. No manual upgrades, no technical overhead to manage autoscaling or a complex Kubernetes infrastructure, and no paying for unused capacity.
The response validated what we believed: developers, agencies, and businesses needed truly managed autoscaling without the complexity of configuring servers, load balancers or guessing when to upgrade plans.
Since launch, our community has deployed thousands of WordPress sites on Autonomous, from personal blogs to high-traffic eCommerce stores, and have found immense value with built-in features such as Redis, Object Cache Pro with Relay, and Cloudflare Enterprise with Edge caching at no extra cost to the plans.
But as our community grew, we heard consistent feedback on how we could offer a better pricing structure that’s more transparent. Today, we’re introducing new pricing that removes arbitrary visit charges entirely and is based on actual infrastructure usage.
What You Can Do With Autonomous Today
Cloudways Autonomous customers benefit from capabilities that were previously accessible only to teams with dedicated technical resources or huge budgets. They can:
- Scale automatically with Kubernetes-based true autoscaling that adjusts to traffic or resource usage in real-time
- Deploy multiple applications across your plan’s allocated resources
- Handle traffic without artificial visit caps your sites can serve as many visitors as your site is getting
- Protect your sites with Cloudflare Enterprise, daily backups, and free SSL certificates
- Speed up delivery with Redis, Object Cache Pro + Relay and global CDN with Edge caching included in every plan
We’ve seen businesses handle Black Friday traffic surges, content creators manage viral posts, and agencies deploy client sites, all without infrastructure concerns. The platform has proven that autoscaling doesn’t need to be complicated.
Updates to Autonomous Pricing
As Autonomous grew, we heard a consistent concern: when autoscaling kicked in during traffic spikes, it wasn’t clear what was driving the costs.
Visit-based pricing added another layer of confusion, users couldn’t predict when they’d hit limits or understand why their analytics showed different numbers than our billing.
The new pricing structure removes the visit confusion entirely. Instead of arbitrary visit counts, you pay based on actual server resources: dedicated baseline pods plus per-hour charges when additional pods spin up to handle traffic.
Combined with the autoscaling activity logs now visible in the Autonomous, you’ll be able to see when your site scaled and correlate it with your traffic patterns.
We’ve also made disk storage 100x more affordable ($0.04/GB vs $0.40/GB).
New Pricing Structure
| New Single-Site Plans | ||||
|---|---|---|---|---|
| Growth | Scale | Plus | Custom Enterprise | |
| Pricing | $100/Month | $200/Month | $400/Month | – |
| Best for | Growing businesses that need autoscaling | Small WooCommerce stores | LMS & large WooCommerce stores | Needs beyond standard plans |
| Websites | 01 | 01 | 01 | 01 |
| Baseline Autoscale servers | 01 | 02 | 03 | Custom |
| Bandwidth | 150 GB | 250 GB | 1000 GB | Custom |
| Disk space | 20 | 50 | 100 | Custom |
| Visits | Unmetered | Unmetered | Unmetered | Custom |
| PHP Workers | 100/server | 100/server | 100/server | Custom |
Additional charges (all plans):
- Disk Space: $0.04/GB
- Bandwidth: $0.40/GB
- Autoscaling: $0.07/hr (Growth), $0.10/hr (Scale), $0.12/hr (Plus) per pod beyond baseline
Features included in all plans:
- True Autoscaling
- Cloudflare Enterprise CDN
- Redis Caching
- Object Cache Pro + Relay
When Does the New Pricing Take Effect?
For Current Customers: Your pricing doesn’t change. You’re grandfathered into your current pricing structure and your current monthly rate and overage charges stay as-is as long as you don’t unsubscribe.
What stays the same:
- Your monthly plan cost and overage rates
- All existing features
- Site performance and autoscaling behavior
- Support level
For New Customers: New pricing is live and available as of November 12th, 2025. Anyone signing up on or after this date will be on the new plan structure with baseline autoscale servers and transparent hourly scaling charges.
Understanding How the New Pricing Works
What Are Autoscale Servers?
Your baseline autoscale servers are Kubernetes-powered virtual servers dedicated to running your WordPress site. Think of them as your site’s guaranteed computing capacity, they handle your typical traffic load and are included in your monthly plan price.
Here’s how they work:
During normal traffic periods, your baseline servers handle all requests. A site on the Growth plan gets 1 autoscale server, Scale gets 2, and Plus gets 3. These autoscale servers are always available, running your site regardless of traffic levels.
When traffic spikes or resource-intensive operations occur (like processing multiple WooCommerce checkouts simultaneously), additional servers automatically spin up within seconds. These extra servers work alongside your baseline servers to handle the increased load. You’re charged $0.07-$0.12 per hour for each additional server, and only for the hours they’re actually running.
Example: Growth plan ($100/month, 1 baseline server). During a product launch, your site scales to 3 servers for 4 hours. You pay: $100 (base) + $0.56 (2 extra servers × 4 hours × $0.07/hr) = $100.56 that month.
The Autonomous dashboard shows current usage and projected monthly cost in real-time.
When traffic normalizes, the extra servers automatically scale back down. If your traffic surge lasted 3 hours, you only pay for those 3 hours of additional capacity.
This is powered by Kubernetes pods, isolated containers that function as virtual servers. Each pod runs a complete instance of your WordPress site with its own allocated CPU, memory, and PHP workers. When we say “server” in your pricing, we’re talking about these Kubernetes pods orchestrating behind the scenes to give you seamless, automatic scaling.
Unlike traditional hosting where you’d need to manually upgrade your plan (and pay for a higher tier all month), autoscale servers give you burst capacity only when you need it. A site that’s normally quiet but has occasional traffic spikes pays baseline costs most of the time, with hourly charges only during those peak periods.
What Are PHP Workers?
Each autoscale server includes 100 PHP workers, the processes that execute your WordPress code. When a visitor requests a page, a PHP worker handles it: connecting to the database, running plugin code, generating the page, and sending the response.
If you have 2 baseline servers, you have 200 PHP workers available. When an additional server spins up during scaling, you get another 100 workers. More workers = more simultaneous requests your site can handle before visitors wait in a queue.
The built-in Redis and Object Cache Pro help significantly. Instead of running database queries for every request, cached results are served from memory. This frees up PHP workers to handle more traffic on your baseline servers before needing to scale.
What Triggers Autoscaling?
Cloudways Autonomous monitors your site’s CPU and memory usage in real-time. When these resources reach certain thresholds, additional autoscale servers (Pods) automatically spin up to handle the load. When usage drops, autoscale servers scale back down.
This means autoscaling responds to actual server demand, not visitor counts. What matters is what your site is doing, not just how many people are visiting.
Common Scenarios That Trigger Autoscaling:
1) WooCommerce stores during checkout: Processing payments, calculating taxes, updating inventory, and sending order confirmations are all resource-intensive operations. A store processing 50 simultaneous checkouts will scale up even if overall traffic is moderate. Black Friday sales, flash deals, or product launches often trigger scaling.
2) Sites with heavy plugins: Page builders (Elementor, Divi), form plugins processing submissions, membership plugins checking user permissions, or security plugins scanning requests all consume CPU and memory. A site running 20+ active plugins will likely need more resources than a lean site with 5, even at the same traffic levels.
3) Dynamic content and database queries: Sites that generate personalized content, run complex product filters, or execute unoptimized database queries will scale more aggressively. A real estate site showing custom property listings based on user filters might scale with just a few hundred visitors if queries aren’t cached properly.
4) Image processing and media-heavy sites: Sites that resize images on-the-fly, serve unoptimized media, or process user uploads consume significant resources. A photography portfolio or user-generated content platform might scale during upload-heavy periods regardless of visitor counts.
5) Background tasks and cron jobs: Scheduled tasks like sending bulk emails, generating reports, backing up databases, or syncing with third-party APIs can trigger scaling even during low-traffic periods.
Built-in optimization helps, but doesn’t eliminate the need for efficiency
Every Autonomous plan includes Redis and Object Cache Pro with Relay, which can materially reduce database load by caching query results in memory. This means repeat requests are served instantly without hitting your database.
However, caching doesn’t fix underlying inefficiencies. Poorly written database queries, unoptimized plugins, or unindexed tables will still consume resources on first execution. A complex WooCommerce query might take 3 seconds to run initially, but Object Cache Pro ensures the next 1,000 requests get cached results in milliseconds.
This is why a well-optimized site with proper caching, efficient queries, and lean plugin usage might serve 100,000 visits without scaling beyond baseline pods, while a poorly optimized site might need to scale with just 10,000 visits. Visit-based pricing didn’t reflect this reality, two sites with identical traffic could have completely different infrastructure costs.
Controlling Your Autoscaling Costs
We’ve added Autoscaling Budget Control to help you manage costs predictably. Set a monthly spending cap for autoscaling charges beyond your baseline servers. When you approach your limit, you’ll get alerts. When you hit it, autoscaling pauses until you either increase the cap or the next billing cycle starts.
This gives you control: scale aggressively during launch periods by raising your cap, or set conservative limits during predictable traffic periods. Your baseline servers continue running regardless of your budget setting, the cap only affects additional servers beyond baseline.
Find it in your Autonomous dashboard under Settings → Autoscaling Budget.
Why We’re Making This Change
When we launched Autonomous, we used visit-based pricing because it felt familiar, most hosting providers charge by visits or traffic tiers. But as our community grew, we heard consistent feedback: visit-based pricing doesn’t align with how modern WordPress sites actually consume resources.
A site with 50,000 visits might use minimal resources if it’s well-optimized with caching, while another site with 10,000 visits could require significant server capacity if it’s running complex queries or processing large images. Charging by visits penalized efficient sites and didn’t reflect the actual infrastructure costs.
From your feedback and our data:
- Users on the entry plan with consistent base usage, indicated that they don’t need aggressive scaling, just reliable performance with autoscaling as protection
- Users told us they wanted unmetered visits so they could focus on growing traffic without worrying about arbitrary thresholds
- The technical reality: Kubernetes infrastructure scales based on CPU and memory demand, not page views
- Many users found visit tracking confusing“What counts as a visit? Why did I hit my limit when my analytics show different numbers?”
The new structure removes visit limits entirely and introduces transparent, usage-based autoscaling charges. You get dedicated baseline pods (guaranteed server resources) and only pay for additional pods when your traffic genuinely requires them. No more guessing which visit tier you need.
This change lets us:
- Remove the visit confusion and give you truly unmetered traffic within your resource allocation
- Reduce disk space charges from $0.40/GBto $0.04/GB, making storage 100x more affordable
- Provide dedicated baseline resources so you know exactly what server capacity you’re guaranteed
- Build better visibility tools showing when and why your site scales
- Invest in performance improvements across all plan tiers based on your feedback
What Happens Next
We’re committed to making Autonomous the best fully managed autoscaling platform for WordPress. Over the next year, we plan to ship features that make resource usage clearer, costs more predictable, and scaling more intelligent.
With the new pricing along with the enhanced analytics dashboard we’ve been building, showing you near real-time scaling activity, resource usage trends, and projected costs with the real time billing feature, you’ll finally have visibility into when your sites scale and why.
Thank you for being part of making autoscaling accessible. We’re just getting started.
Got questions about the pricing changes? Visit our Support Center or contact our support.
Saad Khan
Muhammad Saad Khan is the Director of Product Marketing at DigitalOcean, focusing on Cloudways, where he has over a decade of experience. He has a strong background in product marketing, particularly in creating effective positioning and messaging strategies. Saad is passionate about building products for customers with customers.
