Two Premium Hosts, Opposite Origins
You’re an agency owner. You’ve got 12 client sites still limping along on shared hosting — slow page loads, support tickets that go nowhere, the occasional 503 during a product launch. You decide it’s time to move everything to managed WordPress hosting. Real infrastructure. Real support. You narrow the field to two names that keep showing up in the “premium” tier: Liquid Web and WP Engine.
You start doing your homework. You pull up Liquid Web’s managed WordPress page and sign up for a trial. The dashboard loads. And the logo in the top-left corner says “Nexcess.” Not Liquid Web. Nexcess. You check the URL. It’s a Nexcess domain. You open a support chat. The agent introduces themselves as Nexcess support. You go back to the Liquid Web marketing page you started from and read the fine print more carefully. Managed WordPress hosting is “powered by Nexcess.”
Okay. You tab over to WP Engine. Their marketing is polished, focused, clearly WordPress-first. Then you scroll past the feature highlights and notice something in their blog sidebar: press releases about a federal lawsuit. WP Engine vs. Automattic. WP Engine vs. Matt Mullenweg. Terms like “antitrust,” “defamation,” “preliminary injunction.” You click through. WP Engine is in active litigation with the person who co-created WordPress and controls WordPress.org.
Welcome to managed WordPress hosting in 2026.
The comparison sites will line up features in two columns and tell you which one “wins” each category. Storage, CDN, staging environments, support hours. That approach misses the actual question. These aren’t two competing WordPress hosts that happen to differ on specs. They are two companies from completely different industries that ended up selling the same product through radically different paths.
Liquid Web is an infrastructure company. Founded in 1997 in Lansing, Michigan. They own data centers. They built their name on bare metal servers and dedicated hosting. For 22 years, they had nothing to do with WordPress specifically. Then they bought a WordPress company.
WP Engine is a WordPress company. Founded in 2010 in Austin, Texas. WordPress has been their only product from the first day. They’ve never sold a VPS. They’ve never offered cPanel. They’ve never operated a data center. And now they’re in court with the person who has more control over the WordPress ecosystem than anyone else alive.
The question isn’t which host has better specs. The question is which structural risk you can stomach.
The real comparison: You’re choosing between an infrastructure company whose WordPress layer is an acquired afterthought, and a WordPress company that’s in an active legal war with WordPress’s creator. Both have real strengths. Both carry risks that don’t show up on a feature matrix. This review is about those risks.
Why Origin Stories Shape Everything You’ll Experience
I’ve been reviewing hosting since 2014, and the single most reliable predictor of a company’s behavior isn’t their feature list or their pricing page. It’s where they came from. A company that started building servers thinks about hosting differently than a company that started building WordPress tools. That difference shows up in support conversations, dashboard design, how they handle outages, and what they prioritize when they have to choose between two engineering investments.
Liquid Web: The Data Center Company That Bought a WordPress Platform
Liquid Web was founded in 1997 by Matthew Hill, initially as a web design company that evolved into hosting. By the early 2000s, they were running their own data centers in Lansing, Michigan. Their customer base was system administrators, developers running custom applications, and businesses that needed dedicated hardware with root access.
For two decades, Liquid Web’s identity was infrastructure. Dedicated servers. VPS. Private cloud. They were the company you went to when you needed a real server with real specs, not a shared hosting account with an animated control panel. Their support team — the “Most Helpful Humans in Hosting” tagline — was famous for actually knowing how to troubleshoot at the server level. Ask them about PHP-FPM pool tuning or MySQL query optimization and you’d get a real answer, not a scripted response.
WordPress was just one of many applications their customers happened to run. It wasn’t special. It wasn’t the focus.
That changed in 2019 when Liquid Web acquired Nexcess. Nexcess was a managed hosting provider that had built a genuine specialty in WordPress and WooCommerce — purpose-built caching layers, WooCommerce-specific optimizations, a dashboard designed for site owners rather than sysadmins. The acquisition made strategic sense: Liquid Web got a managed WordPress product they didn’t have to build from scratch, and Nexcess got access to Liquid Web’s self-owned data center infrastructure.
For a few years, Nexcess operated semi-independently. They had their own brand, their own marketing, their own support team. If you signed up through Nexcess.com, you got the Nexcess experience. If you signed up through Liquid Web, you got pointed to Nexcess for WordPress.
Then in 2024, Liquid Web fully absorbed the Nexcess brand. TechRadar covered the merger. The Nexcess marketing disappeared. Support routing changed. The “Nexcess” name persisted only inside the dashboard and the support system itself — a ghost of the original brand visible only to paying customers, invisible to everyone else.
WP Engine: The WordPress Company That Never Built a Server
WP Engine was founded in 2010 by Jason Cohen (who also founded Smart Bear Software). The pitch from day one: managed WordPress hosting that handles caching, security, and updates so you don’t have to. Cohen raised venture capital — more than $290 million over multiple rounds — and built a company that was WordPress and only WordPress.
WP Engine developed EverCache, their proprietary caching system built specifically for WordPress page structures. They acquired the Genesis framework and rebranded it as StudioPress, then later integrated it into their platform. They built Local, which became the most popular WordPress local development tool in the ecosystem. They launched Atlas for headless WordPress deployments. Every product decision pointed in the same direction: make WordPress the center of everything.
They never sold a VPS. Never offered dedicated servers. Never shipped cPanel or Plesk. Never operated a physical data center — their infrastructure runs on Google Cloud Platform and AWS. If you want to host a Django app or a Node.js service or a plain HTML site, WP Engine has nothing for you. They chose a lane and stayed in it.
What This Means When You Open a Support Ticket
Here is where the origin difference becomes tangible.
I had a client on Liquid Web’s managed WordPress plan last year whose WooCommerce checkout was slow under load. I opened a support ticket expecting to get WordPress-level advice — caching rules, plugin conflicts, query optimization within WordPress. Instead, the support agent started talking about PHP worker allocation at the server level, offered to adjust OPcache settings, and walked me through MySQL slow query logs. The conversation felt like I was talking to a sysadmin who happened to know WordPress, not a WordPress expert who happened to know servers.
That same month, I opened a ticket with WP Engine about a similar issue on a different client site. The WP Engine agent walked me through their EverCache configuration, checked whether specific plugins were bypassing cache correctly, verified the staging environment was properly isolated, and confirmed the CDN was pulling from the right origin. It was a WordPress conversation through and through. But when I asked about the underlying server specs — how many PHP workers were allocated, what CPU the site was running on — the agent said that information wasn’t available. WP Engine doesn’t publish it.
Neither support experience was bad. Both were technically competent. But they revealed a fundamental difference in what each company considers its job. Liquid Web thinks its job is running infrastructure well. WP Engine thinks its job is running WordPress well. For most WordPress site owners, those sound identical. They’re not.
The origin tells you where each company will invest when forced to choose. Liquid Web will invest in hardware, uptime, and server-level performance. WP Engine will invest in developer tools, WordPress-specific features, and platform integration. The question is which investment matters more for your specific sites.
The Nexcess Question: When Your Managed WordPress Is an Acquisition
If Section 2 made Liquid Web sound like the stable, infrastructure-backed choice, this section is the counterweight. Because the story of Liquid Web’s WordPress hosting is also the story of a brand absorption that went sideways for a lot of customers.
The facts first. TechRadar reported the full Nexcess brand absorption in 2024. What changed in practice was more than cosmetic:
- The Nexcess brand disappeared from all marketing. New customers find “Liquid Web Managed WordPress” — the Nexcess name exists only inside the portal after login.
- Support routing merged into Liquid Web’s unified system. The Nexcess support team that WordPress customers had built relationships with was folded into a larger organization.
- Phone support — which Liquid Web was famous for — was eliminated for many plan tiers. The “Most Helpful Humans” became chatbots and email queues for a growing number of customers.
And then the user reports started piling up.
What Customers Are Saying
On WebHostingTalk (thread t/1935946), a long-time Liquid Web customer titled their post: “I need to leave Liquidweb due to their service support.” The details: outsourced support replacing the in-house team that had been Liquid Web’s primary selling point for over a decade. Phone support eliminated. Ticket response times stretching from hours to days. The thread attracted other Liquid Web customers with similar experiences — the common thread being that something fundamental had changed in 2023–2024, and the company they’d been loyal to wasn’t operating the same way.
On Trustpilot, the numbers are stark. One review from a customer paying $1,500 per month — a dedicated server customer, not a $19/month WordPress plan — described “constant downtime” and eventually switched to a $65/month service elsewhere with better reliability. Another user signed up at an advertised rate of $9.60/month and was charged $141.60, discovering undisclosed fees buried in the billing terms. A pattern emerged in the reviews: long-time customers who had been happy for years suddenly encountering a different company after the organizational changes.
I want to be careful here because every hosting company has negative reviews. Trustpilot skews negative by nature — satisfied customers don’t write reviews, angry ones do. But the Liquid Web/Nexcess reviews have a specific character that matters for this comparison: they’re from existing customers describing a decline, not from new customers who had a bad first experience. That pattern suggests organizational change, not isolated incidents.
But the Infrastructure Underneath Is Still Excellent
And this is the part that makes the Liquid Web decision genuinely difficult, because the hardware story hasn’t changed.
HostingStep’s 2025 benchmark recorded Liquid Web (Nexcess) at 215ms average TTFB. That’s the second-fastest managed WordPress host they tested, behind only Kinsta at 182ms. WP Engine came in at 367ms — 71% slower than Liquid Web on raw server response time.
In load testing with 1,000 concurrent uncached users — the kind of traffic that crashes shared hosting and overwhelms poorly configured managed hosts — Liquid Web held at a 0% error rate with sub-500ms response times. That’s not marketing. That’s a test that simulates a thousand people hitting your WooCommerce checkout simultaneously.
The hardware specs back it up: AMD EPYC processors in self-owned data centers, NVMe SSD storage, and a 99.99% uptime guarantee (not 99.9% — the extra nine matters, it’s the difference between 52 minutes of annual downtime and 8 minutes). For WooCommerce stores that need to handle flash sales, high-concurrency checkout flows, and inventory updates under load, this infrastructure advantage is real and measurable.
WP Engine can’t match this for a straightforward reason: they run on Google Cloud and AWS infrastructure they don’t control. Their optimization happens at the software layer — EverCache, CDN configuration, PHP tuning — not at the hardware layer. When Liquid Web decides to upgrade processors or add memory to a server cluster, they walk down the hall to their own data center. When WP Engine needs more performance, they file a support ticket with Google Cloud.
The Nexcess tension in one sentence: You’re getting world-class hardware and benchmark-leading performance, delivered through a brand-in-transition whose support quality is actively deteriorating according to its own long-time customers. The infrastructure is the best in this comparison. The experience of dealing with the company around that infrastructure is the most uncertain.
WP Engine’s Bet: All-in on a Platform You Don’t Control
If you read Section 3 and started leaning toward WP Engine — polished platform, WordPress-focused, no brand identity crisis — this section exists to flip that weight back.
Because WP Engine has a structural risk that Liquid Web doesn’t carry at all. And unlike Liquid Web’s support issues, which are operational and theoretically fixable, WP Engine’s risk is existential and outside their control.
Timeline of Events
September 2024: Matt Mullenweg — CEO of Automattic, co-founder of WordPress, and the person who controls WordPress.org — publicly calls WP Engine “a cancer to WordPress” during his keynote at WordCamp US. His core accusation: WP Engine generates hundreds of millions in annual revenue from the WordPress ecosystem while contributing almost nothing to WordPress core development. He specifically calls out their modification of the WordPress revision system as misleading to customers.
September 25, 2024: Mullenweg acts on the rhetoric. Automattic blocks WP Engine from accessing WordPress.org. This isn’t a cease-and-desist letter. It’s a technical block. WP Engine’s servers can no longer pull plugin updates, theme updates, or security patches from the official WordPress repository. Over one million websites hosted on WP Engine are suddenly unable to update their software through normal channels.
Stop and sit with that for a moment. You’re paying $30 to $276 per month for “managed WordPress hosting.” The word “managed” implies someone is handling the platform for you. And then the platform itself — not your host, but the software your host is built on — cuts your host off from its update pipeline. Your plugins can’t auto-update. Security patches don’t arrive. Theme updates stall. This is the hosting equivalent of your apartment building’s water supply being shut off because the building owner and the city are in a legal dispute.
October 2024: WP Engine files suit against Automattic and Mullenweg personally, alleging abuse of power, unfair competition, and tortious interference with business relationships.
December 2024: A federal judge grants WP Engine a preliminary injunction, ordering Automattic to restore WP Engine’s access to WordPress.org. Access is restored. Plugin updates resume. The immediate crisis ends.
April 2025: A proposed class-action lawsuit emerges against Automattic, filed on behalf of WordPress users and developers affected by the dispute.
September 2025: The federal court rules on motions to dismiss. The antitrust and extortion claims are dismissed, but the court allows the interference, unfair competition, and defamation claims to proceed. The lawsuit continues.
October 2025: Automattic files counterclaims against WP Engine.
April 2026 (now): The case is unresolved. Discovery is ongoing. No trial date has been set.
What This Means for WP Engine Customers Right Now
Operationally, nothing has changed since December 2024. WordPress.org access works. Plugin updates arrive. Security patches flow. If you’re a WP Engine customer reading this, your sites are functioning normally.
The risk is structural, not operational. Here’s what I mean:
- The injunction is a court order, not a permanent resolution. It can be modified, narrowed, or lifted depending on how the case evolves. It’s a temporary fix to a dispute that hasn’t been decided.
- WP Engine has no alternative plugin distribution system. During the September 2024 blockade, they scrambled to build temporary workarounds. If access were cut again — through a legal mechanism that supersedes the current injunction, or through a restructuring of WordPress.org’s access policies — WP Engine customers would again face disrupted updates.
- The person on the other side of this lawsuit controls the software your host runs. Matt Mullenweg isn’t a random competitor. He’s the co-creator of WordPress and the person who has final say over WordPress.org’s policies. That concentration of power — and willingness to use it — was demonstrated in September 2024.
- Corporate litigation consumes management attention. WP Engine is simultaneously running a hosting company and fighting a federal lawsuit. Those are two full-time jobs. Resources spent on legal strategy are resources not spent on product development, support hiring, or infrastructure investment.
But WP Engine’s Product Is Still Genuinely Good
I’m not trying to scare you away from WP Engine. I’m trying to make sure you know what you’re buying.
Because the product itself has gotten better since the lawsuit started, not worse. WP Engine’s TTFB improved 21% year-over-year, from 463ms in 2024 to 367ms in 2025 benchmarks. Their built-in CDN serves from 200+ edge locations globally. They recorded 100% uptime in Q4 2025 — not “99.99%,” literally zero measurable downtime.
The developer tooling remains the best in managed WordPress hosting. Local for local development. Git push/pull deployment. One-click staging that actually works. SSH and WP-CLI access. The Studio framework (formerly Genesis) for theme development. If your workflow is WordPress development, WP Engine’s tools are purpose-built for exactly that workflow in a way that no other host matches, including Liquid Web.
And there’s a pragmatic argument: WordPress powers over 40% of the web. WP Engine hosts hundreds of thousands of sites. The WordPress ecosystem has too many stakeholders, too much money, and too many dependencies for any single dispute to destroy it. The lawsuit will settle or be decided. WordPress.org access will continue. WP Engine isn’t going anywhere.
That argument is probably correct. But “probably correct” and “guaranteed” are different things. And I sat through those two weeks in September 2024 when “probably fine” wasn’t fine at all.
The WP Engine gamble: You’re getting the best WordPress-specific developer tools in the industry, strong performance, near-perfect uptime, and a platform that’s entirely dependent on a software ecosystem whose steward has already demonstrated willingness to weaponize access. The product is excellent. The platform dependency is real. Liquid Web has no equivalent risk because Liquid Web doesn’t depend on a single ecosystem gatekeeper — they own their infrastructure end-to-end.
What $4/Month and $30/Month Actually Buy You
Pricing comparisons for these two companies are usually misleading because they start from the wrong place. Most comparison sites put Liquid Web’s $4/month entry price next to WP Engine’s $30/month Startup plan and declare Liquid Web the budget winner. That framing is technically accurate and practically useless.
Liquid Web’s Pricing: The $4 Bait and the Real Numbers
Liquid Web’s managed WordPress plans (the Nexcess platform) start at $4/month. That gets you 1 site, 15GB storage, and 2TB bandwidth. On paper, that looks like a steal compared to WP Engine’s $30 entry point.
In practice, the $4 plan is a funnel. It’s there to put a low number on comparison sites and get you into the billing system. For anyone running a real business site — let alone an agency migrating clients — it’s not a serious option. The performance allocation at that tier is baseline. The support priority is lowest. You’re getting the hardware equivalent of the middle seat on a budget airline.
The plans where Liquid Web starts making sense for professional use:
- Personal: $19/month — 1 site, 20GB storage, 5TB bandwidth. This is where actual single-site owners should start. The performance allocation jumps meaningfully from the $4 tier.
- Builder: ~$49/month — Multiple sites, more storage, business-tier support. This is the realistic entry point for freelancers managing a handful of client sites.
- Business: ~$79/month — The WooCommerce-optimized tier with dedicated resources and priority support. For stores doing real volume.
But here’s the part that’s harder to verify from the marketing page. Trustpilot reviews describe billing experiences that don’t match the advertised numbers. One user reported signing up at $9.60/month and being charged $141.60 — a discrepancy attributed to undisclosed fees in the terms. Another on WebHostingTalk described a 140% bill increase between renewal periods. These are individual reports, not systematic evidence, but they appear frequently enough that you should read the complete terms before entering payment information and set a billing alert for the first renewal cycle.
WP Engine’s Pricing: Clear Numbers, Hidden Math
WP Engine’s pricing is more transparent at the plan level and more treacherous at the usage level.
- Startup: $30/month (annual billing) — 1 site, 25,000 monthly visits, 10GB storage
- Professional: $55/month — 3 sites, 75,000 visits
- Growth: $109/month — 10 sites, 100,000 visits
- Scale: $276/month — 30 sites, 400,000 visits
- Custom/Premium: $400+/month — Enterprise tiers with dedicated account management
Those numbers are clear. What isn’t clear until you’re already a customer: WP Engine charges $2 per 1,000 excess visits, and their visit counting method inflates your numbers by 20–50% compared to Google Analytics.
WP Engine counts unique IP addresses per 24-hour period. Google Analytics counts JavaScript-tracked sessions. The gap comes from all the traffic GA never sees: pages without your tracking snippet, visitors running ad blockers, RSS feed consumers, bot traffic that slips through filtering, hot-linked images served to other sites. A site that Google Analytics says receives 20,000 monthly sessions might show 28,000 or even 30,000 in WP Engine’s dashboard. On a Startup plan with a 25,000-visit ceiling, that invisible 8,000–10,000 visit gap is the difference between “plenty of headroom” and a $16–$20 monthly overage.
G2 reviewers have also flagged that WP Engine doesn’t publish CPU or memory specs for any plan tier. One reviewer called it “shady” — you’re paying premium prices without knowing whether your site runs on 1 CPU core or 4, 2GB RAM or 8GB. Liquid Web publishes AMD EPYC processor details and storage specifications. WP Engine’s position seems to be that the managed platform is the product, not the hardware underneath it. For buyers who care about what they’re getting at the infrastructure level, that opacity is a problem.
The Real Math: Agency With 5 Client Sites
Let’s make this concrete. You run a small agency. You manage 5 WordPress client sites. Each gets around 40,000 monthly visits as measured by GA — which means roughly 52,000–60,000 as WP Engine would count them.
On Liquid Web / Nexcess: A Builder-tier plan at roughly $49–79/month covers multiple sites with generous bandwidth. Liquid Web measures bandwidth, not visits, so traffic spikes don’t generate per-visitor charges. Your cost stays in that range regardless of whether each site gets 20,000 or 60,000 visits in a given month.
On WP Engine: You need the Growth plan at $109/month for 10 sites and 100,000 total visits. But your 5 sites at ~55,000 WP-Engine-counted visits each = 275,000 total visits. That’s 175,000 over the 100K limit. At $2/1,000: $350 in monthly overage charges. Your $109 plan actually costs $459/month.
That’s not a pricing difference. That’s a 6–9x cost difference for hosting the same five sites.
Now flip the scenario. Solo freelancer, 1 WordPress site, 15,000 monthly GA visits (~20,000 WP Engine count):
WP Engine Startup at $30/month: 20,000 visits is under the 25,000 ceiling. No overages. Beautiful dashboard, staging environments, Git deployment, Local integration. Everything works and the bill is predictable.
Liquid Web Personal at $19/month: $11 cheaper per month, faster raw TTFB (215ms vs 367ms), but the dashboard is the Nexcess portal — functional but not polished — and support quality is a question mark after the brand absorption.
At the single-site, moderate-traffic level, the choice is between WP Engine’s superior UX at a slight premium and Liquid Web’s superior performance at a lower price. At the multi-site, higher-traffic level, the choice isn’t close — WP Engine’s overage structure makes it dramatically more expensive.
The pricing lesson: Entry prices are marketing. What determines your real monthly cost is the interaction between your traffic volume, the host’s counting method, and their overage structure. Liquid Web measures bandwidth and doesn’t charge per-visit overages. WP Engine measures visits at a rate 20–50% higher than your analytics tool and charges $2 per thousand excess. For a single small site, the difference is manageable. For an agency portfolio, it can be catastrophic.
The Decision Framework (And When to Skip Both)
I’m not going to give you a two-column table with checkmarks. Here are three paths, with honest assessment of who each one serves and who it doesn’t.
Pick Liquid Web / Nexcess If:
You run WooCommerce with high-concurrency checkout needs. Flash sales, seasonal spikes, checkout flows that need to process 50+ simultaneous transactions without choking. Liquid Web’s infrastructure advantage is real here — AMD EPYC processors, self-owned data centers, 215ms TTFB, 1,000 concurrent uncached users at 0% error rate. No other managed WordPress host matches this hardware profile for e-commerce workloads.
You want raw server performance as the top priority. If your metric is “how fast does the server respond before CDN and caching enter the picture,” Liquid Web wins this comparison and most others. That 215ms TTFB is infrastructure muscle, not software optimization.
You need flexibility beyond WordPress in the future. Liquid Web also sells VPS, dedicated servers, and cloud hosting. If your business might outgrow managed WordPress and need custom server environments, Liquid Web can grow with you without a full migration to a new provider.
You can tolerate a brand-in-transition. This is the honest caveat. The Nexcess brand absorption is ongoing. Support quality has declined according to long-time customers. You may encounter inconsistency — great infrastructure, uneven support. If you’re the kind of person who can troubleshoot at a moderate technical level and doesn’t need hand-holding from support, the infrastructure advantage justifies the experience risk. If you expect premium support quality matching the premium price, you may be disappointed.
Budget: $19–79/month for realistic professional use.
Pick WP Engine If:
Your entire stack is WordPress and will stay WordPress. WP Engine’s tools — Local, staging, Git deployment, the Studio framework — are built for WordPress workflows and nothing else. If WordPress is your world, this is the most integrated toolset available.
Developer experience is your primary selection criterion. Staging environments that actually mirror production. Git push/pull between local, staging, and production. Local development that syncs with your hosted environment. SSH and WP-CLI access without the overhead of managing a full server. No other managed WordPress host integrates the development workflow this tightly.
You want a dashboard purpose-built for WordPress site management. WP Engine’s portal was designed from the ground up for managing WordPress sites. Liquid Web’s dashboard was designed for managing servers and then had a WordPress layer added through the Nexcess acquisition. The difference is visible in every interaction.
You can accept the legal and ecosystem risk. The WP Engine vs. Automattic lawsuit is ongoing. The December 2024 injunction protects WordPress.org access for now. The risk is real but bounded — WordPress is too entrenched, too widely used, and too commercially important for the ecosystem to fracture permanently. If you’re comfortable with that assessment, WP Engine’s product quality justifies the choice.
Budget: $30–109/month for typical use cases, but budget for overages if your traffic exceeds plan limits.
Skip Both If:
Your budget is under $50/month and you’re comfortable with moderate server management. Cloudways on a Vultr or DigitalOcean backend starts at $14/month. You get a managed interface over raw cloud infrastructure — not as polished as WP Engine’s dashboard, not as powerful as Liquid Web’s hardware, but 85–90% of both at 30–50% of the cost. For WordPress sites that need better performance than shared hosting but don’t need the full white-glove managed experience, this is the value sweet spot.
You have DevOps skills and resent paying for things you can do yourself. RunCloud ($8/month) or GridPane ($25/month) on a $5–12/month Vultr or Hetzner VPS gives you a managed WordPress stack with full server access. You handle your own updates, backups, and security hardening. You lose the “managed” support safety net. You gain 70–80% cost savings and complete control over your infrastructure. Our managed vs unmanaged guide covers the tradeoff in detail.
Your project isn’t WordPress. This sounds obvious, but I see people evaluating WP Engine for sites that don’t need to be WordPress. If you’re building a static site, a Next.js app, or a custom application, neither of these hosts makes sense. Look at Node.js hosting, static site hosting, or general-purpose cloud providers instead.
You need traditional cPanel/WHM management. Neither Liquid Web’s managed WordPress plans nor WP Engine offer cPanel. If your workflow depends on cPanel, you need a different class of hosting entirely.
The third path is real: For every 10 people comparing Liquid Web and WP Engine, I’d estimate 3–4 would actually be better served by Cloudways or a self-managed VPS. The managed WordPress premium — $30–100+/month above what a VPS costs — buys you convenience, WordPress-specific optimization, and support. If you value those things, pay for them. If you’re paying for them because you don’t know the alternatives exist, now you know.
Frequently Asked Questions
Is Liquid Web’s managed WordPress actually Nexcess?
Yes. Liquid Web acquired Nexcess in 2019 and fully absorbed the brand in 2024. When you sign up for Liquid Web’s managed WordPress hosting, your site runs on what was the Nexcess platform — same dashboard, same underlying technology, different name on the marketing page.
Does the WP Engine/WordPress lawsuit affect my site right now?
Not operationally. The December 2024 court injunction restored WP Engine’s full access to WordPress.org, so plugin and theme updates work normally. But the lawsuit is ongoing as of April 2026. A federal court dismissed the antitrust and extortion claims in September 2025 but allowed interference, unfair competition, and defamation claims to proceed. Automattic filed counterclaims in October 2025. The risk is forward-looking: the September 2024 blockade demonstrated that WordPress.org access can be disrupted, and until the case resolves, that precedent hangs over every WP Engine-hosted site. Liquid Web customers have zero exposure to this dispute.
Which is faster, Liquid Web or WP Engine?
Liquid Web is significantly faster at the server level. HostingStep’s 2025 benchmarks recorded Liquid Web at 215ms average TTFB versus WP Engine’s 367ms — a 41% speed advantage for Liquid Web. Under heavy load (1,000 concurrent users), Liquid Web maintained 0% error rate with sub-500ms responses. However, raw TTFB isn’t the full picture. WP Engine’s built-in CDN with 200+ edge locations means cached content reaches geographically distributed visitors quickly. For a site with mostly static/cached pages and a global audience, the real-world speed difference narrows. For dynamic pages — WooCommerce checkout, member portals, search results — Liquid Web’s hardware advantage is fully felt.
Can I move from WP Engine to Liquid Web easily?
Yes. Liquid Web offers free migrations on managed WordPress plans. The site, database, and files transfer straightforwardly. The friction is in workflow dependencies — if you use Local’s push/pull with WP Engine, Genesis/Studio themes, or Git-based deployment through WP Engine’s system, those won’t carry over.
Why doesn’t WP Engine publish server specs?
WP Engine has never disclosed CPU cores, RAM, or storage type per plan. Their marketing centers on visit limits, features, and the managed experience rather than hardware specifications. G2 reviewers have flagged this as a transparency gap — you’re paying $30–276/month without knowing if your site runs on 1 CPU core or 4. Liquid Web publishes AMD EPYC processor details and storage specs. The likely reason for WP Engine’s opacity: their value proposition is the platform (caching, CDN, developer tools), not the metal. They run on Google Cloud and AWS, so the infrastructure isn’t “theirs” in the same way Liquid Web’s self-owned data centers are. Disclosing Google Cloud VM specs would invite unfavorable comparisons with cheaper providers running on the same cloud.
Is Cloudways a better alternative to both?
For a specific buyer profile, genuinely yes. Cloudways on Vultr or DigitalOcean starts at $14/month and gives you a managed layer over raw cloud infrastructure. The performance benchmarks within 10–15% of both Liquid Web and WP Engine for most WordPress workloads. The pricing is fully transparent — pay-as-you-go, no visit-based overages, no hidden fees. You get root server access through a managed interface, which means more control than either Liquid Web or WP Engine provide on their managed WordPress plans.
What you lose: WP Engine’s purpose-built WordPress developer tools (Local integration, Git push/pull, the Studio framework). Liquid Web’s WooCommerce-specific optimization and self-owned data center infrastructure. White-glove WordPress support from either provider. Cloudways support knows servers well but isn’t WordPress-specialized at the same depth.
If you’re an experienced WordPress user who can manage your own updates, configure your own caching, and troubleshoot plugin conflicts without calling support, Cloudways gives you 85–90% of the managed WordPress experience at 30–50% of the cost. If you need the support safety net or the WordPress-specific tooling, the premium is worth paying. I’ve been putting new client projects on Cloudways when neither Liquid Web nor WP Engine is a clear fit, and it’s worked well.
Jason’s Take
Remember the agency owner from the intro? Twelve client sites on shared hosting, ready to upgrade, narrowed it to Liquid Web and WP Engine? I was that agency owner. Not exactly — I had nine sites, not twelve. But close enough.
I’ve moved client sites between these two platforms three times in the past two years. Each time I thought I’d found the answer. Each time something changed — Nexcess got absorbed, WP Engine got sued, a support ticket went unanswered for 72 hours on a platform where I was paying $79/month.
Here’s what I’ve settled on, and I want to be specific because vague conclusions help nobody:
If the site makes money through WooCommerce transactions, I put it on Liquid Web. The infrastructure advantage is real for checkout-heavy workloads. When a client runs a flash sale and 800 people hit the cart simultaneously, the AMD EPYC processors and self-owned data centers earn their keep. The 215ms TTFB means the first click feels fast. The 0% error rate at 1,000 concurrent uncached users means the checkout doesn’t buckle. Yes, the support experience has deteriorated since the Nexcess absorption. Yes, I’ve had tickets sit for 18+ hours. But for WooCommerce sites, the performance floor is more important than the support ceiling, and Liquid Web’s floor is higher than anyone else’s in this price range.
If the site is a content or marketing WordPress site where developer workflow matters more than raw speed, I lean WP Engine. The staging environment alone saves me two hours per week across client projects. Push from Local to staging, test, push to production — the workflow is frictionless in a way that Liquid Web’s Nexcess portal can’t match. Git deployment means I can version-control themes and track changes across a team. For content sites where the traffic is mostly cached and the TTFB difference between 215ms and 367ms is masked by CDN delivery, WP Engine’s developer experience wins.
But I’ve also started putting new client projects on Cloudways with Vultr backends. $14/month. 95% of the performance. None of the brand-in-transition uncertainty. None of the ecosystem litigation risk. When a client has a moderate-traffic WordPress site and doesn’t need WooCommerce-level infrastructure or WP Engine’s developer toolchain, Cloudways is the honest recommendation. Telling someone to pay $79/month for Liquid Web or $109/month for WP Engine when $14/month Cloudways would serve them equally well is the kind of advice that earns affiliate commissions but doesn’t earn trust.
That’s where the industry is heading, whether Liquid Web and WP Engine want to admit it or not. The managed WordPress premium made sense when WordPress was hard to configure and server management was beyond most site owners. In 2026, tools like Cloudways, RunCloud, and GridPane have closed most of that gap. The premium managed hosts still win on polish, specialization, and support — but the delta is shrinking every year, and the prices aren’t shrinking with it.
Choose your risk. Liquid Web: great hardware, uncertain support, acquired WordPress layer. WP Engine: great tools, ecosystem litigation, opaque infrastructure. Cloudways: no specialization, no drama, most of the performance at a fraction of the price.
There isn’t a wrong answer. There’s only a wrong assumption — that these three paths are more similar than they are.
This review will be updated when the WP Engine vs. Automattic lawsuit reaches resolution. Last verified: April 2026.