MemberHost vs WP Engine for Membership, Course and Community Sites
Weighing a WP Engine alternative for a membership site? How WP Engine's Essential and Core plans compare with MemberHost on resources, logged-in caching, plugin support and uptime terms.
WP Engine is a managed WordPress host with published plans. Essential, listed with “Shared resources”, can be bought straight from its pricing page, while Core, listed with “Isolated resources”, and Enterprise go through its sales team (WP Engine plans). Its support team is available around the clock. MemberHost is a much smaller operation focused on WordPress membership, course and community sites, and it treats the plugin side of a problem as part of hosting rather than something to pass back.
This comparison was prepared by MemberHost from each company’s public documentation, checked on 15 September 2026. MemberHost is not affiliated with or endorsed by WP Engine, and WP Engine is a trademark of its owner. Contract-specific terms may differ from what is published. If something here has changed, tell us and we will correct it.
At a glance
| WP Engine | MemberHost | |
|---|---|---|
| Plans | Essential, Core and Enterprise. Essential carries first-year pricing for new customers; Core starts at “$400/month” (WP Engine plans, WP Engine FAQ) | No fixed tiers. Priced per site on traffic, plugin stack and support needs |
| Resources | Essential: “Shared resources”. Core: “Isolated resources” (WP Engine plans) | Each client gets its own node or cluster with dedicated resources, running as virtual machines on bare metal servers from data centre partners, on hardware we specify (performance) |
| PHP workers | We could not find a per-plan count publicly documented. Real visitors are queued ahead of AJAX and bot requests (WP Engine) | Configured per site (concurrent users) |
| Visits | “one unique IP address logged per day (UTC)”. Its overage rate of “$2 per 1,000 extra monthly visitors” is stated for the Startup, Professional, Growth and Scale plans (WP Engine) | No published visit tiers; any traffic or overage terms are set out in your plan (terms) |
| Logged-in pages | Membership and LMS plugins are among those that “will generally benefit the least” from its Edge Full Page Cache (WP Engine) | Caching configured per site, with Redis, Relay and OPcache where they suit the plugins (performance) |
| Plugin and theme problems | Server-side investigation; plugin functionality, bugs, and conflicts with WordPress core or your own code are out of scope (WP Engine) | Looked at on the server and in WordPress together (about us) |
| Support hours | “24 hours a day, 7 days a week”, with no phone support on Lite and Startup plans (WP Engine) | Not 24/7 |
| Uptime commitment | 99.95% on Essential, 99.99% on Core and Enterprise (WP Engine SLA, WP Engine) | 99.9% (our SLA) |
Essential and Core are different products
The two plans are built differently, so pin down which one you mean before comparing anything else. WP Engine’s caching docs explain what the shared model involves: on shared accounts, “resources are split between all sites on a server”, which is one reason caching can’t be switched off entirely (WP Engine cache docs). Its request queue limits the knock-on effect. When one account gets a flood of traffic, “PHP workers are still available for other accounts” on the same server (WP Engine).
Core adds isolated resources, managed migration services and a 99.99% uptime guarantee (WP Engine plans), with pricing that starts at $400 a month.
If your membership site is on Essential and it slows down during launches, ask WP Engine whether the plan’s capacity matches your logged-in traffic, or whether Core is the fairer comparison. Put the same question to us. Every MemberHost client gets its own node or cluster, with resources dedicated to that client rather than pooled with other customers, and we will walk you through how yours would be set up before you commit.
Logged-in members and caching
WP Engine spells out where its edge cache stops helping: “Plugins with extensive personalization will generally benefit the least from Edge Full Page Cache since their key dynamic pages cannot have their HTML cached. These types of plugins include Membership/Community plugins and Learning/LMS plugins.” Its server cache also skips any request carrying a wordpress_ login cookie by default (WP Engine cache docs).
So member dashboards, lessons and community pages are built fresh by PHP. WP Engine’s object cache, which you can toggle per environment, cuts down on repeated database queries (WP Engine). What we could not find is how many PHP workers each plan gets. WP Engine does describe what happens when every worker is busy: human visitors go to the front, the oldest waiting requests are rejected, and “A 504 error can occur when too many items are in the backlog”. Once a site can’t be optimised further, its advice is to upgrade “to a larger server with more PHP workers” (WP Engine).
MemberPress has specific advice here. It says “WP Engine has been a very good host for MemberPress, and we have no problem recommending them”, with conditions: ask WP Engine support to keep /register, /login, /mepr, /account, /thank-you and /unauthorized out of the cache, and “Disable their Object Caching as it can cause some unexpected issues”. It also points out that protecting static files such as PDFs needs its Downloads add-on, and that WP Engine “does not support true linux, or server side, crons”, offering Alternate Cron instead (MemberPress).
We decide caching one site at a time. On a MemberPress site, object caching gets tested before it goes live, and stays off if the plugins don’t agree with it. For why the page cache matters so little once members sign in, see our membership site speed guide.
Autoscale, if you are planning for launch spikes
WP Engine Autoscale adds application nodes automatically as traffic climbs, on Google Cloud, while the database scales up on a single instance (WP Engine). It also changes how you deploy: code goes through a GitHub repository and WP Engine’s CI/CD workflow, SFTP is not available, and “The only directory that is writable is the /wp-content/uploads/ folder”. WP Engine says “Most third-party plugins work without changes” and gives two checks for any plugin you are unsure about: does it write outside the uploads folder, and does it write files into uploads while serving a page (WP Engine compatibility). Run both against your membership, course and community plugins before relying on it. We could not find Autoscale pricing published.
Support: where the line sits
WP Engine covers the server side of plugin trouble: “We help identify issues that occur server side, analyze logs and other errors”, and in some cases it works with plugin developers on conflicts with its platform. Past that point, “Issues with plugin/theme functionality, bugs, and conflicts with WordPress core or your custom code are outside of our scope of support” (WP Engine). If a subscription renewal fails because two plugins disagree, the fix is your developer’s job.
We would treat that failed renewal as ours to investigate, on the server and in the plugins. The people doing it come from our sister agency, MemberFix, which has been building membership sites since 2011 (about us).
If round-the-clock access matters most, WP Engine takes that point: chat at any hour, plus phone on plans other than Lite and Startup. MemberHost does not offer 24/7 support.
Uptime terms
| WP Engine | MemberHost | |
|---|---|---|
| Commitment | 99.95% on Essential; 99.99% “Enhanced SLA” on Core and Enterprise | 99.9% of each monthly billing period |
| What it covers | “the Services” | “Necessary Services” needed for your site to be reachable |
| Main exclusions | Scheduled and emergency maintenance, beta services, force majeure, and the actions or omissions of you, your authorised users or anyone acting for you, including any use “that exceeds WP Engine’s recommendations or advertised limits” | Third-party services, maintenance in a daily 2am to 5am window (data centre local time), emergency maintenance, scheduled outages, force majeure including external service providers, traffic beyond the plan, client code and configuration, changes by other parties, and WordPress or plugin downtime while the server itself stays up |
| Remedy | Credits as a percentage of monthly fees for downtime beyond the target, capped at 100%, claimed within 30 days, and they “will not be paid or provided as a refund” | Credits applied to future invoices, capped at the month’s value, never paid in cash, requested within 30 days, and the SLA’s remedies are the sole remedy |
| Source | WP Engine SLA | Our SLA |
Note that our plugin troubleshooting is support work, not an uptime promise: if a plugin takes WordPress down while the server stays up, that is outside our SLA. An SLA credit won’t replace what a failed launch week costs you on either host. Our reliability guide is about avoiding that week in the first place.
WP Engine may fit better when
- You want help at 3am, over chat, or by phone on plans other than Lite and Startup.
- You look after many sites and want published plans and a self-serve portal to manage them from.
- Your developer already owns plugin bugs and custom code.
- You need a written 99.99% uptime commitment and Core fits the budget.
- Your team deploys from Git and wants Autoscale to add capacity on its own.
MemberHost may fit better when
- Plugin conflicts are your most common emergency, and you want the host to investigate them instead of routing them to a developer.
- Most of your traffic is logged in, and you want caching chosen for your plugins, including a MemberPress test before object caching is switched on.
- You would rather plan capacity around your launch calendar than around a monthly visit allowance.
- You want resources no other customer draws on, on a node or cluster of your own.
- Your launches justify a clustered setup, where failover sync keeps a synced clone ready (uptime).
Skip MemberHost if you need someone on the phone at 2am, want to compare prices on a public pricing page, run applications other than WordPress, or prefer to set up hosting without talking to anyone.
What switching looks like
WP Engine’s Essential plan includes a free automated migration plugin, and Core includes managed migration services (WP Engine plans). Whichever direction you move a membership site, choose a cutover window away from scheduled renewals, and afterwards confirm that payment webhooks and renewals ran on the new server.
If you switch to us, onboarding starts with a look through your plugin setup, and the migration costs nothing. To test before committing, we can put a staging copy of your site through a load test on the steps members take, like signing in, opening a course or renewing. On refunds, we grant all reasonable requests. And should you leave later, we will fully assist with the migration away from us.
Frequently Asked Questions
Is WP Engine a good host for membership sites?
It can be, particularly with a developer who handles plugin issues. MemberPress recommends it, with some configuration. Two things to plan around: WP Engine says membership and LMS plugins generally gain the least from its Edge Full Page Cache (WP Engine), and plugin functionality, bugs and conflicts with WordPress core or your own code fall outside its support scope (WP Engine).
Does WP Engine fix plugin problems?
It investigates the server side, analyses logs and sometimes works with plugin developers on conflicts with its platform. Fixing plugin functionality, bugs and conflicts with your own code is out of scope (WP Engine).
How many PHP workers does WP Engine include?
We could not find a per-plan number in WP Engine’s public documentation. It explains how requests are prioritised when workers are busy, and says Core and Enterprise plans with dedicated servers “can be upgraded to increase the number of PHP workers” (WP Engine).
Does MemberHost offer 24/7 support?
No. WP Engine does, so if round-the-clock access to support is a requirement, it is the better fit on that point.