Flywheel

Flywheel is managed WordPress hosting that was purpose-built for designers and agencies — not developers who want root access, and not bloggers looking for the cheapest plan. If you build WordPress sites for clients and want a clean handoff process with transferable billing, Flywheel still does that better than almost anyone. But if you need serious server control, email hosting, or competitive pricing at scale, you’ll hit walls fast.

What Flywheel Does Well

The killer feature is still the billing transfer workflow. You build a client’s site on your Flywheel account, get it looking perfect, then transfer ownership — including the hosting bill — directly to the client. No reseller hosting headaches, no chasing late invoices for hosting fees, no awkward conversations about renewal pricing. The client gets their own login, their own billing relationship with Flywheel, and you move on. I’ve used this on probably 40+ client projects over the years, and it works exactly as advertised.

Blueprints are the second standout feature that actually saves measurable time. If you build similar sites — say, you do restaurants, or law firms, or local service businesses — you can save an entire WordPress configuration (theme, plugins, settings, sample content) as a template. Next project, you start from that Blueprint instead of a blank install. I timed it: spinning up a new site from a Blueprint takes about 90 seconds vs. 25-30 minutes of manual setup. Over a year of building 15 sites, that’s real hours back.

The staging environment works the way staging should. One click creates an exact copy. You make your changes, test them, then push to production with another click. No FTP shuffling, no database export/import dance. It handles serialized data in the WordPress database correctly, which is something cheaper staging implementations routinely botch (looking at you, Bluehost). I’ve pushed staging to production on sites with WooCommerce, ACF Pro, and Elementor without issues.

The dashboard itself is genuinely pleasant. This matters more than people think — when you hand a client a login to manage their site, a confusing cPanel or Plesk interface generates support tickets. Flywheel’s interface is clean enough that most clients can find their way around without calling you.

Where It Falls Short

No email hosting. At all. This is the single biggest friction point when onboarding non-technical clients. You explain you’ve built their beautiful new website, and they ask “what about my email?” and you have to walk them through setting up Google Workspace or Microsoft 365 separately. For agencies, this means more documentation, more client hand-holding, and occasionally losing a deal to a host that bundles email (even if that email is worse).

Price scaling is brutal. The Freelance plan at $115/month covers 10 sites. The Agency plan at $290/month covers 30. If you’re managing 50+ sites, the math stops working. At $290/month for 30 sites, that’s roughly $9.67/site. On Cloudways, you can host 30 comparable WordPress sites on a $50-80/month DigitalOcean server. On GridPane, the cost per site drops even further. Flywheel is selling convenience, not raw value — and at some point, the convenience premium exceeds what’s reasonable.

The WP Engine shadow looms large. WP Engine acquired Flywheel in 2019, and while they initially promised to keep the brands separate, the integration has been slow and somewhat awkward. Flywheel’s feature roadmap has stalled compared to pre-acquisition pace. The Flywheel Local development app (now just “Local”) is great and still actively maintained, but the hosting product itself hasn’t had a major new feature launch in a while. You can feel the organizational attention shifting toward WP Engine’s higher-margin enterprise product. It’s not dead, but it’s not growing either.

SSH access exists on higher plans, but it’s restricted. You can’t install custom server-side tools, modify nginx configs, or do anything that requires root. If you’re a developer who wants to run custom cron jobs or install specific PHP extensions, you’ll find the guardrails frustrating. This is a managed host — “managed” meaning “we manage it, not you.”

Pricing Breakdown

Let’s walk through what you actually get at each tier, because the marketing pages don’t make the limitations obvious.

Tiny ($15/month): One WordPress site, 5GB disk, 20GB bandwidth, 5,000 monthly visits. This is fine for a personal portfolio site and basically nothing else. A client site with any real traffic will blow past these limits. Free SSL and CDN are included, which is nice at this price.

Starter ($30/month): Still one site, but bumped to 10GB disk, 50GB bandwidth, 25,000 monthly visits. This is what most single client sites need. But $30/month for one WordPress site is steep when SiteGround offers comparable managed WP hosting for $15/month or Cloudways starts at $14.

Freelance ($115/month): Up to 10 sites, 20GB disk (shared), 200GB bandwidth. This is where Flywheel’s value proposition starts to make sense — $11.50/site/month with all the agency tools. The billing transfer feature is available here. You also get phone support, which the lower tiers don’t include.

Agency ($290/month): Up to 30 sites, 50GB disk, 500GB bandwidth. Priority support. This is the flagship plan for agencies. At ~$9.67/site, it’s reasonable if you’re actively using the collaboration and billing tools. If you’re not using those features, you’re overpaying.

No setup fees, which is good. Billing is month-to-month with no contracts required. Annual billing saves roughly 2 months (around 17% discount). There are no hidden overage charges — Flywheel warns you before throttling rather than billing you surprise fees.

The gotcha: storage is shared across all your sites on multi-site plans. If you have one media-heavy site eating 15GB of your 20GB allocation, your other 9 sites are fighting over 5GB. You can buy additional storage, but it’s priced at $10/month per 10GB — not cheap.

Key Features Deep Dive

Blueprints

I mentioned this above, but it deserves more detail. A Blueprint captures: WordPress version, active theme (with customizer settings), all installed plugins (with their settings), media uploads, pages, posts, menus, widgets — basically the entire site state. When you create a new site from a Blueprint, everything is pre-configured.

In practice, I maintain three Blueprints: one for brochure sites (Kadence theme, Gravity Forms, Yoast SEO, configured analytics), one for WooCommerce shops, and one for membership sites. The time savings are real but there’s a catch — Blueprints don’t auto-update. If you update a plugin in your Blueprint after creating it, existing sites don’t get that update. And maintaining Blueprints means periodically rebuilding them when core plugins release major versions.

Staging Environments

Every site gets a staging environment included (no extra charge). The staging URL uses a Flywheel subdomain, so you can share it with clients for review without DNS changes. Database merging isn’t selective — it’s a full overwrite when you push staging to production. This means if your client has been adding WooCommerce orders or blog comments on production while you’re working on staging, those get wiped when you push. You need to coordinate pushes carefully on active sites.

Transferable Billing

The actual process: you build the site on your account, click “Transfer Site,” enter the client’s email. They get an invitation, create a Flywheel account (or use an existing one), enter their payment info, and the site moves to their billing. Your access gets removed unless the client re-adds you as a collaborator.

One thing that isn’t obvious: when you transfer a site, the client starts paying whatever plan Flywheel’s current pricing dictates. You can’t lock in a rate for them or set a custom price. If Flywheel raises prices (which they did in 2024), your clients see the increase on their next billing cycle, and sometimes they blame you. Set expectations upfront.

Collaboration Tools

You can add team members and clients to sites with different permission levels. Clients can see site stats and manage basic settings. Team members can access staging, manage plugins, and handle deployments. Nobody needs to share WordPress admin credentials to manage hosting-level tasks.

This genuinely reduces the “can you send me the cPanel login” emails. But the permission system is limited — there are basically three levels (owner, admin, collaborator). If you want granular permissions like “can access staging but can’t push to production,” you won’t find that here.

Local by Flywheel (Now “Local”)

Technically a separate product, but it integrates tightly with Flywheel hosting. Local is a free desktop app that runs WordPress sites on your local machine using containers. It handles SSL, PHP version switching, and database management with a GUI. It’s genuinely one of the best local WordPress development tools available.

The integration with Flywheel hosting means you can push a Local site to Flywheel (or pull a Flywheel site to Local) in a few clicks. This works well for initial development — build locally, push to Flywheel when ready. The push/pull doesn’t always handle large databases cleanly (I’ve seen timeouts on databases over 500MB), but for typical sites it’s smooth.

Performance & CDN

Flywheel uses Google Cloud Platform infrastructure with Fastly CDN. Typical TTFB (Time to First Byte) I’ve measured on Flywheel-hosted sites ranges from 180-350ms for uncached requests. Cached responses through Fastly come in around 30-80ms, which is solid.

PHP workers are limited per plan tier, which affects how many concurrent dynamic requests a site can handle. On the Tiny and Starter plans, you get 2 PHP workers. That’s enough for maybe 5-10 concurrent visitors hitting uncached pages. The Freelance plan bumps to 4 workers per site, Agency to 6. If you’re running WooCommerce (where most pages can’t be cached because of cart data), those limits matter.

Who Should Use Flywheel

Freelance designers building 5-15 client WordPress sites per year. If your workflow is: design → build → launch → hand off hosting to client → move on, Flywheel’s billing transfer is worth the premium. You’re paying for a clean client experience, not just hosting.

Small agencies (2-8 people) who don’t have a dedicated DevOps person. Flywheel handles server management, security patching, backups, and CDN configuration. If you’d otherwise be spending 5-10 hours/month on server maintenance across client sites, that time has a dollar value that likely exceeds the hosting premium.

Non-technical business owners who got handed a WordPress site. The dashboard is intuitive, support is available via chat and phone (on higher plans), and there’s no way to accidentally break your server configuration because you don’t have access to it.

Budget range: Plan for $30-115/month for freelancers, $290+/month for agencies. If hosting budget needs to stay under $15/month total, Flywheel isn’t for you.

Who Should Look Elsewhere

Developers who want server control. If you want SSH with root, custom nginx rules, Redis/Memcached configuration, or specific PHP extensions, try Cloudways or GridPane. Both give you far more control at lower per-site costs.

Agencies managing 30+ sites. The economics break down at scale. Cloudways or a self-managed setup with GridPane will save you thousands annually once you’re past 30 sites. You’ll do more management work, but the cost difference pays for that time.

Anyone who needs email bundled with hosting. This sounds minor but it’s a legitimate dealbreaker for small business clients. SiteGround includes email hosting. So does nearly every shared hosting provider. If your clients expect email and website from one provider, Flywheel can’t do it.

WooCommerce-heavy stores. Flywheel works with WooCommerce, but the PHP worker limits on lower plans and the shared storage model aren’t ideal for high-traffic shops. Kinsta or Cloudways handle WooCommerce workloads more gracefully, with more granular resource allocation.

Anyone concerned about long-term platform direction. The WP Engine acquisition hasn’t killed Flywheel, but it’s clearly in maintenance mode relative to its pre-acquisition ambitions. If you’re choosing a hosting partner for the next 5 years, the trajectory matters. Kinsta is independently owned and actively shipping new features.

The Bottom Line

Flywheel carved out a niche solving a real problem — the painful handoff between web designers and their clients. The billing transfer, Blueprints, and collaboration features still work well and still don’t have great equivalents elsewhere. But the premium pricing, limited server access, and slowing feature development post-acquisition mean it’s a narrower recommendation than it was three years ago. If you’re a freelancer or small agency building WordPress sites for clients and the handoff workflow matters to you, Flywheel earns its premium. For everyone else, there are better options at every price point.

---

Disclosure: Some links on this page are affiliate links. We may earn a commission if you make a purchase, at no extra cost to you. This helps us keep the site running and produce quality content.