Kinsta vs WP Engine vs Cloudways: which managed WordPress host fits

Three managed WordPress hosts turn up on almost every shortlist: Kinsta, WP Engine and Cloudways. From the outside they look alike, fully managed WordPress with backups, staging and a CDN. But they charge for two completely different things, and that is the whole decision.

The one difference that decides it

Kinsta and WP Engine sell you a plan capped by monthly visits. Cloudways sells you a server measured in RAM and CPU, billed by the hour, with unlimited sites on it. So the real question is not which sticker is lower. It is whether your cost is driven by traffic or by the resources your site needs.

What each one actually costs

• Kinsta: the entry single-site plan is about 35 dollars a month, roughly 30 on annual billing, which saves about 70 dollars a year. One WordPress site with a monthly visit allowance, and 50 cents per 1,000 visits over the cap. Fully managed with premium support, priced by traffic.
• WP Engine: the Startup plan is 30 dollars a month billed annually, about 35 month to month, for one site, 25,000 visits and 10 GB, with overage around 2 dollars per 1,000 extra visits. Professional is 55 dollars a month annually for 3 sites and 75,000 visits. Also priced by traffic.
• Cloudways: a managed layer over cloud servers, from about 11 dollars a month for an entry DigitalOcean server, billed by the hour with no annual contract and no renewal hike. You can run unlimited sites on that one server until it runs out of resources. Priced by the server, not by visits.

Why we do not print a single winner

It is tempting to line up 35 against 30 against 11 and crown Cloudways. That comparison misleads, because the three prices buy different things. Kinsta and WP Engine bundle the hands-off management, the support and a visit allowance. Cloudways gives you a raw managed server that you size, watch and grow yourself, and its bill climbs when your site needs more RAM, not when it gets more visitors. A high-traffic brochure site can be cheapest on Cloudways; a resource-heavy store that outgrows a small server can be cheaper, and calmer, on Kinsta or WP Engine.

What actually counts as a visit

If two of the three price by visits, it is worth knowing what a visit even is, because the number that decides your bill is not the number in your analytics. On both Kinsta and WP Engine a billable visit is one unique IP address in a 24-hour period, so ten page views from the same person in one day count as a single visit, not ten. Both also strip bot traffic out of the billable count. WP Engine excludes known bot user agents and, since September 2025, suspected bots as well, and it never counts static files such as images, CSS and JavaScript. Kinsta likewise excludes traffic from clearly identifiable bots and crawlers, though it cautions that automated traffic it cannot confidently classify may still count. That gap matters more every year: automated traffic passed half of all web requests in 2024, so a raw visits figure that counts everything can sit well above what either host actually bills you for.

The practical lesson is to budget against the host billable definition, not the visits line in Google Analytics or a raw server log. Kinsta added a second option in late 2025: you can put a plan on a server-bandwidth allowance in gigabytes instead of a visit cap, at the same price (the WP 5 plan, for example, is either 125,000 visits or 65 GB a month), and switch an existing plan between the two measures, with bandwidth overage at 50 cents per gigabyte. If your traffic is heavy on large assets, or hard to pin to clean visit counts, the bandwidth meter can be the fairer one. Cloudways sidesteps the whole question, since it never meters visits at all; its bill tracks the server you rent, so this is a Kinsta and WP Engine decision only.

The other ceiling the visit meter hides: PHP workers

The visit cap is not the only limit on these hosts. Kinsta and WP Engine also cap how many uncached requests your site can process at the same time, through PHP workers, which Kinsta now calls PHP threads. Each worker handles one uncached request at a time, and cached pages bypass them entirely, so a mostly cached blog rarely notices. A store is the opposite: checkout, cart, account and other logged-in pages cannot be cached, so each one ties up a worker for the length of the request. When every worker is busy the next requests queue, and if the queue backs up visitors see slow loads or 502 and 504 errors. That is the ceiling a busy dynamic site tends to hit first, well before its visit count is anywhere near the plan cap.

• Kinsta ties PHP threads to the plan. The entry Single 35k plan includes 2 threads per site, and higher plans add more. Kinsta explicitly does not recommend running eCommerce, membership, LMS or forum sites on its 2-thread plans, and its support steers those sites to a plan with at least 4 threads, so a dynamic store often needs a tier above the cheapest even when its traffic is light.
• WP Engine scales workers with the plan and server tier. When they are all busy it queues requests and prioritises real visitors over bots and background AJAX, then sheds the oldest waiting requests, which surfaces to users as 502 or 504 errors. If you keep hitting the ceiling the fix is a larger plan or server.
• Cloudways sets no small fixed cap. PHP-FPM concurrency is bounded by the RAM and CPU of the server you rent, and you can raise the worker settings yourself in the control panel, so a heavier server buys more headroom. The flip side is the usual Cloudways trade: tuning that ceiling is your job, not the host’s.

So on a cache-friendly content site the visit meter is the number to watch, but on a WooCommerce store, a membership site or anything with heavy logged-in traffic, the worker ceiling can force an upgrade before the visit cap does. Price the plan that gives you enough concurrency, not just enough visits.

Which one fits

• Traffic is your variable and you want it hands-off: Kinsta or WP Engine. You pay for visits and get managed WordPress with support that owns the stack. Kinsta leans premium performance; WP Engine leans agency and developer workflows.
• You are comfortable sizing a server, or you want the lowest sticker and many small sites on one box: Cloudways. You take on more of the management in exchange for a server-priced bill and no visit meter.
• You are cost-sensitive and unsure: put your real traffic, your maintenance hours and your hourly rate into the calculator. The plan price is the smallest of the three lines, and the tool shows which host wins on the 12-month total, not the sticker.

None of these three run the introductory-then-renewal trap that budget shared hosts do, so the number you see is close to the number you keep paying. The variable that moves your bill is your own site: how much traffic it draws and how many resources it needs.