WP Engine Bought Flywheel — Is It Still Worth Using?

Flywheel was acquired by WP Engine in 2019. Since then, long-term Flywheel users have documented a consistent pattern: slower page loads, a dashboard that hasn't meaningfully evolved, and support response times that no longer match the brand's original reputation. If you're still on Flywheel today, the question isn't sentimental — it's whether you're still getting what you're paying for.

What Actually Happened When WP Engine Bought Flywheel?

Flywheel launched in 2012 with a clear value proposition: beautifully simple managed WordPress hosting designed specifically for creative agencies and freelancers. The dashboard was clean, onboarding was smooth, and the support team understood WordPress workflows in a way that generic hosts didn't. Agencies loved it. Freelancers swore by it.

WP Engine acquired Flywheel in 2019 for a reported $50 million. At the time, the messaging was reassuring — both products would continue operating independently, Flywheel's culture would be preserved, nothing would change for existing customers.

That's not quite how it played out.

What typically happens in tech acquisitions — and this is well-documented in SaaS and hosting specifically — is that the acquiring company achieves consolidation efficiencies by merging infrastructure teams, deprioritizing the smaller product's roadmap, and redirecting talent toward the parent platform. Customers on the acquired product become a retention problem, not a growth investment.

By 2021 and into 2022–2023, Flywheel's community forums, Reddit threads (r/webdev, r/wordpress), and Trustpilot reviews began accumulating a consistent complaint pattern: slower sites, a dashboard with fewer updates, and support that had lost the responsive, knowledgeable feel that made Flywheel worth paying a premium for in the first place.

How Much Has Flywheel Performance Actually Degraded?

This is where we move from anecdote to data. Independent benchmark testing by hosting review sites including Review Signal and HostingFacts has placed Flywheel's average Time to First Byte (TTFB) in the 380–520ms range for mid-tier plans — a metric that was considerably better in pre-acquisition reviews from 2017–2019.

For context:

TTFB ranges sourced from Review Signal WordPress Hosting Benchmarks 2024–2025 and independent GTmetrix test compilations.

A 400ms TTFB isn't catastrophic in isolation. But context matters. Google's Core Web Vitals directly factor server response time into rankings. According to Google's own research, sites that load in 1–3 seconds have a 32% higher bounce rate than sites loading under 1 second (Google/SOASTA, 2017 — still cited in Core Web Vitals documentation). If your hosting is contributing 400–500ms before a single asset loads, you're starting in a hole.

For agencies managing client sites, this isn't abstract. It's a client retention risk. We've written in detail about how site speed directly impacts revenue — the numbers are hard to argue with when you put them in front of a client.

What Do Long-Term Flywheel Users Actually Report?

The degradation pattern isn't one dramatic failure — it's a slow erosion that's easy to rationalize quarter by quarter until you realize how far things have slipped.

Common themes from Flywheel users on Reddit, G2, and Trustpilot (compiled 2023–2025):

Dashboard stagnation. The Flywheel interface, once praised for being the best-designed in the industry, hasn't received major feature updates in years. Competitors have added staging workflows, Git integration, real-time monitoring, and AI-assisted diagnostics. Flywheel's roadmap, to the extent it's communicated publicly at all, has been quiet.

Support quality shift. The original Flywheel support team was known for WordPress expertise — people who understood plugin conflicts, theme issues, and database optimization. Post-acquisition, users report longer resolution times and more generic, tiered responses. One user on r/webdev wrote in 2024: "It feels like they moved Flywheel support onto the same queue as WP Engine, which sounds fine until you realize WP Engine support isn't that special either."

Pricing versus value drift. Flywheel's Growth plan (the most common tier for small agencies) now runs $115/mo for 10 sites. For that price point, comparable options deliver meaningfully better performance metrics and more actively developed feature sets.

No migration incentive to stay. Several users noted that when they asked about switching to WP Engine's own plans, there was no compelling reason to do so — WP Engine's entry plans have their own limitations and the migration process wasn't as smooth as promised.

Is This Just Nostalgia, or a Real Business Problem?

It's a real business problem, and it's worth being direct about why.

If you're an agency or freelancer managing client sites on Flywheel, every client site is a reflection of your recommendation. When a client's site runs slowly, they don't think "my hosting provider is underperforming" — they think "my agency isn't on top of things." That's a client relationship risk you're absorbing on behalf of a hosting company that, frankly, isn't your partner in that relationship anymore.

The broader pattern here — a beloved indie product getting absorbed and hollowed out by a larger acquirer — isn't unique to Flywheel. It's happened with EIG acquiring Bluehost, HostGator, and others. It happened when Liquid Web acquired Nexcess. The real cost of cheap or degraded WordPress hosting isn't the monthly bill — it's the compounding cost of slower sites, higher churn, and lost client trust.

What Should You Actually Look for in a Managed WordPress Host?

If the Flywheel story is a case study in what to avoid, here's what to look for in a host that's worth trusting:

1. Infrastructure transparency. Can they tell you exactly what server stack they're running, what PHP versions are supported, and how they handle updates? A host that's serious about performance publishes this. You can review TopSyde's full stack as an example of what that transparency looks like.

2. Active product development. Is the dashboard getting meaningfully better? Are new features shipping? A stagnant product is a red flag, especially in a category where AI-assisted monitoring, automated backups, and staging workflows are now table stakes.

3. Support that's actually staffed. "24/7 support" often means a chatbot or outsourced tier-1 that escalates slowly. What you want is documented response SLAs — something you can actually hold them to. Our SLA page publishes the commitment: under 2 hours during business hours for support responses.

4. AI-powered monitoring, not just uptime pings. Basic uptime monitoring tells you when a site is completely down. That's a low bar. AI-powered WordPress monitoring catches performance degradation, security anomalies, and silent failures before clients notice. That's the standard worth expecting.

5. Independent ownership. This one is harder to verify, but it's worth asking: who owns this company, and what's their incentive structure? A VC-backed platform with an exit in sight has different priorities than a team that's building for the long term. It's a legitimate question to ask before you migrate client sites.

What Does Migration Actually Look Like?

The most common reason agencies stay on underperforming hosting is inertia and migration anxiety. The fear of breaking something, the time cost, the client conversations — it all feels like more pain than just accepting slower performance.

That's usually the wrong calculation.

For a typical WordPress site, a managed migration to a better host takes 2–4 hours of actual work, most of which the receiving host handles. DNS propagation adds 24–48 hours of lead time, but there's no actual downtime when migration is done correctly. We wrote a detailed walkthrough of what to expect when migrating from GoDaddy to managed WordPress hosting — the process is essentially identical for Flywheel.

The real cost of staying isn't the $15–$115/mo you're paying Flywheel. It's the slower performance compounding against your SEO, the client conversations about why their site isn't as fast as a competitor's, and the support resolution times when something goes wrong at a bad moment.

For agencies specifically, the calculus is even clearer. Managed WordPress hosting built for marketing agencies isn't just infrastructure — it's part of your value proposition to clients. When your hosting is rock-solid, you're selling confidence. When it's degrading quietly, you're absorbing risk for a brand that's no longer investing in you.

Should You Stay on Flywheel or Move On?

Here's the honest answer: if you're on Flywheel's lower tiers for personal projects and performance hasn't been an issue, there's no emergency. But if you're managing client sites, running WooCommerce, or depending on your hosting for business-critical applications, the data doesn't support staying on a platform that's been deprioritized by its parent company.

The full 2026 managed WordPress hosting comparison walks through WP Engine, Kinsta, Flywheel, and TopSyde side by side with real pricing and performance data. Use it to do the math for your specific situation.

If you want to see what modern managed WordPress hosting looks like — with AI monitoring through TopSyde Sentinel, proactive security scanning, and a team that actually picks up the phone — TopSyde starts at $89/mo per site with a 30-day money-back guarantee. Migration is handled for you. There's no reason the switch has to be complicated.

Frequently Asked Questions

Is Flywheel still a good host in 2026?

Flywheel remains functional, but independent benchmarks and user reports consistently show performance and support quality that lags behind what it offered pre-acquisition. For personal sites or low-traffic projects, it may still be adequate. For agency client sites or business-critical WordPress installations, the risk-adjusted value has declined significantly since the WP Engine acquisition.

Will WP Engine eventually shut down the Flywheel brand?

WP Engine hasn't announced plans to retire Flywheel as of 2026, but the acquisition playbook is well-established: consolidate infrastructure, slow down the acquired product's roadmap, and gradually migrate customers to the parent platform. Whether Flywheel stays branded or gets absorbed, the trajectory for existing customers on the platform isn't improving.

How hard is it to migrate away from Flywheel?

For a standard WordPress site, migration takes 2–4 hours of actual work when handled by a managed host that includes migration services. DNS propagation adds 24–48 hours, but there's no production downtime when migration is executed correctly. The process is straightforward, and most managed hosts — including TopSyde — handle the migration as part of onboarding.

What should I look for to avoid another Flywheel situation?

Look for hosts with transparent infrastructure documentation, actively updated dashboards, published SLAs for support response times, and independent ownership structures that aren't optimizing for an exit. Asking directly about roadmap and company ownership is a legitimate part of the vendor evaluation process.

How does TopSyde compare to Flywheel on pricing?

Flywheel's Growth plan runs approximately $115/mo for 10 sites. TopSyde starts at $89/mo per site, which reflects a different model — fewer sites per account, but with significantly more included per site: AI monitoring via TopSyde Sentinel, malware scanning, proactive support under 2 hours during business hours, and an actively developed platform. For agencies managing high-value client sites, per-site pricing with full-service support typically delivers better ROI than volume-discounted plans with degraded infrastructure.

Rachel Nguyen

Senior WordPress Engineer

8+ years WordPress & WooCommerce development

Rachel is a senior WordPress engineer at TopSyde specializing in WooCommerce performance and plugin architecture. She has built and maintained high-traffic e-commerce sites processing millions in annual revenue.

XLinkedIn