Flywheel

Designer-friendly managed WP

The entry plan is Starter: one WordPress site metered at 25,000 visits a month for $25/mo, as published September 2026. Flywheel is owned by WP Engine, and that one fact explains most of the lineup — the two brands sell overlapping managed WordPress products at different price points and to different sensibilities, with WP Engine's Essential tier covering the same 1 site and 25,000 visits at $28/mo for the first year against a $35/mo standard rate. Email and domains are not included.

What Flywheel sells that its parent brand does not is workflow for people who build sites for other people: a dashboard that is the most approachable in the niche, Local — the free desktop WordPress development app, originally Local by Flywheel — and billing transfer, which hands a finished site's invoice to the client without rebuilding anything. Our standing objection to the lower tiers is storage caps; we have not verified the per-tier storage figures, so we do not quote them.

There is no renewal step in our record: $25/mo is both the entry and the ongoing rate as verified September 7, 2026. On the three-year arithmetic our managed-WordPress table uses — twelve months at the advertised rate, then twenty-four at the rate it renews to — that is $900. Pressable is about $750, Rocket.net $900, Kinsta $1,080, and WP Engine $1,176, because its $28 first year steps to $35.

The useful way to read that: Flywheel and WP Engine are $276 apart over three years, and the cheaper of the two is the one with the designer-friendly tooling. If you are choosing between the sibling brands on price alone, Flywheel wins. The measurement in the limitations section below is the reason we do not leave the recommendation there.

Both brands are visit-metered and we have not verified either vendor's overage schedule. Model a bad month before you commit — at this tier overages, not list price, are what surprise people when a post travels.

Renewal figures come from our Hosting Renewal Price Index — intro vs renewal pricing for every provider we cover, verified on vendor sites and dated.

Choose Flywheel if

• +Designers and freelancers who hand finished sites to clients — billing transfer is the feature nobody else does as cleanly
• +Teams already building in Local who want the hosting to match the development tool
• +Anyone who wants WP Engine's platform lineage at a lower sticker price and a friendlier dashboard
• +Buyers who want the entry price to be the ongoing price: our record shows no renewal step

Look elsewhere if

• −Response-time consistency is what you are paying for — Flywheel is the worst entry in our study's degraded-time table by a wide margin; read the limitations below before buying
• −Your traffic is spiky — 25,000 visits is the entry allowance and we have not verified the overage rate
• −You need email or a domain bundled; neither is included
• −You keep a lot of media on a lower tier — storage caps are our standing objection, though we have not verified the figures
• −You want server-level control, or your site is not WordPress

Inbound: Flywheel lists free migration, standard at this tier, and the move is the ordinary managed-WordPress one — database plus wp-content, then a DNS cutover. Local, Flywheel's free development app, also pushes a local site up to Flywheel hosting, which is the smoothest inbound path if you are building rather than moving. Outbound is unremarkable in the good sense: WordPress exports and database dumps restore anywhere. What does not travel is the workflow layer — billing transfer, the dashboard and the Local integration are Flywheel's. One note about ownership rather than technology: Flywheel and WP Engine are the same company, so moving between them is a move within one vendor, not a diversification. We have not verified a money-back window or a published SLA, so budget as though there is neither until you have it in writing.

The most important fact on this profile is a measurement, and it is not flattering. Across the 45-day interim window of our uptime study (Aug 8 – Sep 22, 2026), getflywheel.com recorded 5,191 minutes of degraded time across 209 separate episodes, the longest 161 minutes on August 10. That is roughly 87 hours — more than three and a half days' worth of slow-but-successful responses inside 45 days, averaging better than four episodes a day. It is the largest degraded figure in the study by a factor of about four and a half: WP Engine, Flywheel's own parent brand, is second at 1,145 minutes across 46 episodes. Nothing else in the field looks like it, and for two brands positioned and priced on performance the pairing is the finding, not a footnote.

Four boundaries on that number, and all four matter. First, it is not downtime and we will not call it downtime: every one of those checks returned a successful HTTP response, only slowly, and degraded time is never counted as downtime anywhere in the study. Flywheel recorded no hard downtime at all in the window — it is absent from the hard-downtime table entirely, meaning zero episodes of requests failing outright. Second, slow is a threshold rather than a judgement: a response is marked degraded when it crosses our three-second threshold, and the published methodology already records one case (Microsoft 365) where time logged near that line was largely a threshold artifact. Flywheel's volume is far beyond artifact territory, but the threshold is what defines the number. Third, the pattern is regional — the interim report notes it was worst from our Asia-Pacific probes. Fourth and most important: the study measures each provider's own primary website, not the availability or speed of customer sites hosted on the platform. Those are different infrastructures, and a host's own site can be slow while customer workloads are fine. We think a company's front door is worth measuring, and worth measuring publicly when the company sells speed; we will never present it as your site's response time.

What we have not verified, and therefore do not state: per-tier storage allowances, the visit-overage rate, a money-back guarantee, an uptime SLA, data-centre locations, or support channels and hours. We have run no performance or load testing on Flywheel, as on every provider on this site — see how we test; the degraded-time figures above come from availability monitoring of the vendor's own website, which is a different thing from a benchmark of hosted workloads. The full 90-day report, due early November 2026, is where these numbers get their final window.

Alternatives to consider

• Hostinger — budget-friendly first sites
• Cloudways — managed cloud for growing sites