WP Engine

What WP Engine actually is

WP Engine is a managed WordPress hosting platform, not a general-purpose cloud or VPS provider. That distinction matters more than anything else in this review: you cannot run arbitrary workloads here, only WordPress (and, on the Headless plans, Node front-ends talking to WordPress). In exchange for that restriction you get a platform where WordPress core, PHP and MySQL updates are handled for you, daily backups run without configuration, and the support desk is staffed by people who answer WordPress questions specifically.

The company was founded in 2010 by Jason Cohen and Ben Metcalfe and is headquartered in Austin, Texas. It has been majority-owned by Silver Lake since 2018, when the firm invested $250 million. Over the years it has absorbed StudioPress (the Genesis theme framework), Flywheel, Delicious Brains (WP Migrate, WP Offload Media), and NitroPack. In our view that acquisition trail is visible in the product: the ecosystem tools around the hosting are unusually coherent, and things like Advanced Custom Fields and WP Migrate are first-party rather than third-party plugins you assemble yourself.

The platform also sits at the centre of an ongoing industry dispute — WordPress.org's trademark conflict with WP Engine that became public in 2024 — which we treat as a real ecosystem risk and discuss below rather than as a footnote.

Pricing: what you really pay

WP Engine's public pricing has been reshuffled recently, and the numbers on different pages of their own site do not always agree, which is worth knowing before you budget. The main plans page currently lists Essential starting at $28.00 per month billed annually ($336 paid up front), and the Business tier starting at $400.00 per month billed annually. Enterprise is quote-only. The small-business pricing page shows first-year promotional rates — $29/month for Startup, $55 for Professional, $109 for Growth, $276 for Scale — and the company's own renewal notice (content.wpengine.com) lists subscription prices effective from March 2026: Lite $17, Startup $35, Professional $65, Growth $130, Scale $330 in USD. Treat the headline "from $28" as an entry point and the renewal table as the number you will actually pay in year two.

What you get at the entry tier: one site, roughly 25,000 visits per month (an estimate, not a hard cap), 10 GB storage and 75 GB bandwidth. Extra sites cost $20 per month each. Plans scale through 3 sites / 75,000 visits / 15 GB, 10 sites / 100,000 visits / 20 GB, up to 30 sites / 400,000 visits / 50 GB. Above that, Core Hosting (from $400/month) and Enterprise are sales conversations.

Two pricing habits we dislike. First, visits and bandwidth are metered as plan ceilings on a shared environment, so a traffic spike is a support conversation rather than an auto-scaling event — WP Engine says as much on the plans page ("numbers are estimates only. Get in touch for dynamic sites or traffic spikes"). Second, the advanced DDoS and managed WAF package is an optional add-on on Essential and Business plans, only bundled at Enterprise. A security feature that is standard at many competitors being an upsell is the kind of thing we flag.

There is no free tier and no hourly billing; it is a monthly or annual subscription. There is also no per-core or per-GB-of-RAM pricing, because WP Engine does not publish resource allocations at all — see below.

Performance & infrastructure

WP Engine runs its shared plans on Google Cloud, and Premium tiers on AWS (and Azure, per their own comparison pages). The support documentation lists thirteen Google Cloud regions — Iowa, South Carolina, Montreal, Belgium, London, Frankfurt, Netherlands, Finland, Taiwan, Tokyo, Sydney, Singapore and Tel Aviv — and nine AWS regions (Virginia, Ohio, Oregon, Montreal, Ireland, London, Frankfurt, Singapore, Sydney). Frankfurt and some APAC Google regions carry an extra fee or Premium-plan requirement. That gives you genuine EU, US and APAC coverage with a region choice at signup, and support will migrate you between regions on request.

Caching is EverCache, WP Engine's own multi-layer platform cache, plus an edge CDN. Daily automated backups are included on every plan, with on-demand backups and staging environments for testing changes before they go live. Automated WordPress and PHP updates are managed, free SSL certificates auto-renew, and SSH access is included. The Business tier and above get isolated resources; Essential plans run on shared infrastructure.

Uptime commitments are tiered: 99.95% on Essential, 99.99% on Core and Enterprise. That is honest, published, and accompanied by a real SLA document with credit terms (5% of the monthly fee per full hour of excess downtime on Essential, 3% per 30 minutes on the enhanced tier). We prefer this to hosts that quote "99.99% uptime" in marketing copy with no agreement behind it.

The one place infrastructure transparency stops is resource allocation. WP Engine publishes no vCPU counts, no RAM per plan, no storage I/O figures. The plan table tells you visits, storage and bandwidth and nothing else. If you are the kind of buyer who compares cores-per-euro, this is not your platform; if you want a WordPress site that stays up and loads fast without server administration, the abstraction is the point.

Where it falls short

Cost, plainly. Entry pricing around $28-35 per month for one WordPress site on shared infrastructure is several times what a comparable workload costs on Hetzner Cloud or a managed VPS, and you could run ten small sites on a €8-15 cloud VM for less than one WP Engine Startup plan. You are paying for the managed layer, the WordPress expertise on the support desk, and the ecosystem tooling — not for raw compute. Buyers who are comfortable with server administration will find the value proposition hard to justify.

Resource ceilings on visits and bandwidth create overage anxiety that unmetered competitors avoid. And the plugin restrictions are real: caching and backup plugins that duplicate WP Engine's own platform functions are blocked, because they conflict with EverCache and the managed backup pipeline. For most customers that is sensible engineering. For a site with a specific workflow that depends on a blocked plugin, it is a hard stop.

The trademark dispute with WordPress.org, running since 2024, introduces a category of risk we have not seen before in this market: a managed WordPress host whose relationship with the project's governing entity is adversarial. So far customers have been served normally and the platform's releases have continued, but plugin-directory access and ecosystem dynamics are genuinely uncertain. We would not refuse to buy WP Engine over it, but for a long contract we would want it acknowledged in writing.

Finally, the fragmented pricing across WP Engine's own pages (plans page, small-business page, and the renewal table disagreeing on the entry price) makes budgeting harder than it should be for a vendor at this price point.

Who should pick this

Our pick for agencies and businesses running revenue-critical WordPress sites where nobody on the team wants to be a sysadmin. Multi-environment workflows (dev/staging/production), managed migrations, the StudioPress/Genesis and ACF toolchain, and a support desk that speaks WordPress natively are the reasons to pay the premium. The Business tier and above make sense when you need isolated resources and the 99.99% SLA; the Core tier is where dedicated account management and pre-launch technical review start.

We would not pick it for a personal blog, a brochure site with modest traffic, or any team with Linux skills — those workloads are dramatically cheaper elsewhere, and we'd rather see the budget spent on content or design. Nor is it for anything that is not WordPress.

If you are choosing between WP Engine and Kinsta, the honest summary is that both are credible managed WordPress platforms with similar prices and different architectures (layered platform isolation versus per-site containers), and WP Engine's edge is the acquired tooling ecosystem. Against Cloudways, WP Engine costs more and does more of the operational work.

Key takeaways

• Managed WordPress only, since 2010, Austin-based, Silver Lake-owned since 2018 — a mature platform, not a startup bet.
• Entry pricing around $28/month billed annually, with renewals higher; no free tier, no hourly billing, no published CPU/RAM allocations.
• 22 documented Google Cloud and AWS regions across North America, Europe, Asia-Pacific and the Middle East; EU, US and APAC all covered.
• Real SLA: 99.95% on Essential, 99.99% on Core and Enterprise, with published credit terms.
• Strength is the managed layer and WordPress-native support and tooling; the cost is price-per-workload and metered visit/bandwidth ceilings.
• Watch the WordPress.org trademark dispute as ecosystem risk on any multi-year commitment.

Sources

• https://wpengine.com/plans/
• https://wpengine.com/small-business-pricing-plans
• https://content.wpengine.com/wp-engine-updated-pricing
• https://wpengine.com/support/servers
• https://wpengine.com/blog/wp-engine-vs-kinsta
• https://wpengine.com/blog/cloudways-vs-wpengine
• https://en.wikipedia.org/wiki/WP_Engine
• https://wpengine.com/blog/milestone-announcement