VPS vs Managed Hosting for a Membership Site: Who Runs the Server?
Shared, managed WordPress, VPS or managed VPS for a membership site? A responsibility matrix shows who patches, backs up, monitors and tunes each one.
Shared hosting suits small, quiet sites. A VPS can be managed or unmanaged: “VPS” describes the server, while “managed” describes who operates it. Choose an unmanaged VPS only if you or your developer can handle patching, backups, monitoring and tuning. For a membership site, either approach needs resources sized for logged-in traffic and caching configured for member pages.
So list the jobs before you pick a type. The matrix below shows who does each job on each kind of hosting.
Sources below are the vendors’ and hosts’ own documentation and articles, checked on 19 October 2026. Citing a company’s material doesn’t mean it endorses this article, and product names are trademarks of their owners.
What do shared, managed WordPress, VPS and dedicated hosting mean?
Shared hosting pools server resources among customers. Managed WordPress hosting means the host runs WordPress-specific infrastructure. A VPS is a virtual server that may be managed or unmanaged. A dedicated server assigns one physical machine to one customer. A cluster is a group of servers configured to work together; whether it provides failover depends on its design.
- Shared hosting. LifterLMS’s hosting guide describes the pooling: on shared hosts, “a common pool of resources (RAM/ CPU, etc) is shared between a number of sites” (LifterLMS). Exact Hosting’s help center says each account on shared hosting has limits “that keep one busy site from slowing down the others”, typically on CPU, memory and the number of processes (Exact Hosting).
- Managed WordPress hosting. WP Engine defines it as “a service model in which a web host handles the technical operation of your website”, overseeing “server-level performance, security updates, daily backups, and specialized technical support” (WP Engine). On resources, sources disagree. WP Engine describes managed hosting as providing “isolated server resources”, while LifterLMS says that although optimized WordPress hosting costs more, “technically they still are a type of shared hosting (because your site will still be sharing resources with other sites)” (LifterLMS). Both describe real products, and plans differ, so read what your plan says about resources.
- VPS. LifterLMS: “On a VPS, however, you get full control of your resources and you can tune every aspect of your server. That’s also the drawback. You need the technical know-how and skills to be able to fine-tune a VPS” (LifterLMS). Whether the host helps with that is the managed or unmanaged question, covered below.
- Dedicated server. A whole physical machine assigned to one customer (WP Engine). WP Engine adds: “Managed refers to the operational service model, while dedicated refers to how physical server resources are allocated.” Managed or unmanaged and shared or dedicated are two separate questions.
- Cluster. A group of servers configured to work together. Ask whether the proposed setup includes failover, which failures it handles, and how recovery is tested. MemberHost offers failover only on clustered setups (see uptime).
Who does what on each type of hosting?
On shared and managed WordPress hosting, the host runs the server and you run the site. On an unmanaged VPS you run both. On a managed VPS the split depends on the plan’s written scope. Liquid Web adds a caveat: “Management scope varies by provider and plan. Review the support terms to confirm exactly what the provider handles” (Liquid Web).
| Job | Shared | Managed WordPress | Unmanaged VPS | Managed VPS |
|---|---|---|---|---|
| OS and server security patches | Depends on plan | Host | You | Often the host, within plan scope |
| PHP and MySQL upgrades | Depends on plan | Depends on plan | You | Depends on plan |
| Firewall and WAF | Depends on plan | Depends on plan | You | Depends on plan |
| Backups | Depends on plan | Host | You | Depends on plan |
| Restore tests | Depends on plan | Depends on plan | You | Depends on plan |
| Monitoring and alerts | Depends on plan | Host | You | Often included in the plan |
| PHP-FPM and caching tuning | Depends on plan | Depends on plan | You | Depends on plan |
| Incident response | Depends on plan | Depends on plan | You | Host, within plan scope |
| Scaling | Depends on plan | Depends on plan | You | Depends on plan |
| Application security (your WordPress site, plugins, themes) | Depends on plan | Depends on plan | You | You |
“You” means you must assign someone to the job. “Depends on plan” means you need written confirmation of who performs it. The VPS entries follow Liquid Web’s comparison; the managed WordPress “Host” entries reflect WP Engine’s description, not a universal service standard. Before buying, ask the provider to confirm each responsibility, including exclusions and extra charges.
The PHP and MySQL row is the one people overlook. Each PHP branch gets two years of active support and two more of security fixes only, then “reaches its end of life” (PHP). Someone has to schedule and test those moves.
How to check what a plan covers
Liquid Web suggests asking “What server tasks does management include?”, “Does the plan include monitoring and backups?” and “Does support cover applications or only the server?” (Liquid Web). For a membership site, five questions get you most of the way:
- Who applies operating system security patches, and is that written in the plan?
- Where do backups live, how long are they kept, and who tests a restore?
- Who gets the alert when the site goes down, and who acts on it?
- Is the PHP worker or process limit written down, and can it be raised?
- Does support cover a misbehaving plugin, or only the server?
How do the hosting types compare for a membership site?
For a membership site, three differences matter most: how resources are allocated, who runs the server, and whether PHP worker limits are published. Shared hosting pools resources, managed plans vary, and an unmanaged VPS gives you more server work. Member pages are personalized, so page caching often helps less than it does on a blog. BuddyBoss puts it this way: “you can’t simply cache all the pages because each user has a personalized experience” (BuddyBoss).
| Type | Resources | Who runs the server | PHP worker limits | Good fit | Watch out for |
|---|---|---|---|---|---|
| Shared | Pooled; limits on CPU, memory and processes | Host | Often set as process, CPU and memory limits; ask whether PHP workers are limited | Small, quiet sites; a site just starting | Resource-limit errors; catch-all page caching |
| Managed WordPress | Depends on plan | Host | Ask for the number in writing | Teams with no sysadmin who want WordPress-aware support | Cache rules for member pages; plugin problems may fall outside support |
| Unmanaged VPS | Plan allocation; ask whether CPU is shared or dedicated | You | You set them, within CPU and RAM | Teams with real server skills | Every job in the matrix is yours |
| Managed VPS | Depends on plan | Split per written scope | Ask, or have the host set them | Revenue-sensitive sites without in-house server staff | ”Managed” does not mean application problems are covered |
| Managed cluster | Depends on design and plan | Split per written scope | Ask | Sites where an hour of downtime costs real money | Added cost and complexity |
The catch-all caching point comes from LifterLMS: “Many shared hosts employ some sort of catch-all page-caching mechanism because you share resources with other websites on the same server (That’s why it is called shared hosting). This can interfere with some LifterLMS functionality.” (LifterLMS) On workers, see PHP workers for membership sites for what they are and how to estimate your own number.
What are the signs you’ve outgrown shared hosting?
Frequent 508 errors can show that a shared-hosting account is repeatedly reaching its allowance, though a single 508 doesn’t mean you need a larger plan, since inefficient plugins, missing caching, bot traffic and traffic spikes can trigger the same limit (Exact Hosting).
Exact Hosting defines the 508: “A 508 Resource Limit Reached message means your account momentarily needed more than its allowance. It is usually temporary”, and “frequent 508s mean your site is regularly bumping the ceiling and needs attention” (Exact Hosting). Its resource table lists “Entry processes” as controlling “Simultaneous active requests”. Ask the host separately whether the plan also has a PHP-worker or PHP-process limit.
The same page lists common causes of high usage, including “Too many plugins or a poorly coded one”, “No caching”, “Bot or crawler traffic hitting the site aggressively” and “A traffic spike that genuinely exceeds the plan”. Its advice on telling them apart: “Spikes that line up with traffic are normal; constant high usage points to something inefficient on the site.” And on upgrading: “If your usage is legitimate and consistently exceeds your plan even after optimizing, the right move is a plan with more resources.”
LifterLMS notes that on shared hosting, support “can often dismiss as WordPress related which they can’t/won’t help you with” (LifterLMS). A short checklist keeps the conversation useful:
- Open your host’s resource-usage graphs and note when the spikes happen.
- Compare those times with logins, launches, email sends and scheduled jobs.
- Check that account, login and checkout pages are excluded from page caching. Why WordPress gets slow when members log in covers the usual causes.
- Test the site the way members use it. Our load testing guide shows how to do it without fooling yourself.
What do the plugin vendors say about shared hosting?
The vendors do not agree.
- BuddyBoss is the firmest. Its server recommendations say: “Shared hosting is not recommended as it can lead to extremely slow performance and functionality issues. VPS, Dedicated Servers, or Managed WordPress Hosting are ideal for maintaining speed, performance, and security” (BuddyBoss, updated 13 August 2025). Note what the page lists: a VPS is one of three options. For more on that platform, see why BuddyBoss is slow.
- LifterLMS is conditional. “A large number of existing LifterLMS users host their sites on such hosts without any trouble whatsoever”, but once courses and audience grow, “you may start running into issues”, and the heavy processing “is definitely not something a shared host built for simple micro-sites will be able to handle well” (LifterLMS, modified 8 September 2026).
- MemberPress lists shared plans among hosts that work with it, with caveats. It tells owners: “MemberPress, like every plugin on your site, requires a portion of your server resources (CPU, memory, etc.). Thus, please make sure that your hosting plan comes with enough resources.” For one host’s shared plans it adds: “if your site is growing and traffic is picking up, we recommend moving off of shared hosting” (MemberPress, modified 17 October 2025).
- LearnDash: its technical requirements page, now served from Nexcess documentation, lists software minimums, including a “PHP memory limit of 128 MB or greater”, and says nothing about shared hosting either way (LearnDash requirements).
- MemberMouse is the most specific. Its hosting requirements page names a VPS as the minimum recommended plan, says “Avoid ‘managed WordPress’ plans”, and requires “the ability to control caching to omit pages and functions” (MemberMouse, modified 23 February 2024). That is one more reason to read the plan’s written terms rather than the plan’s label.
Some vendor pages also point to a hosting partner. BuddyBoss’s page goes on to recommend Rapyd (BuddyBoss), and MemberPress’s list names Rapyd Cloud first among its recommended hosts (MemberPress).
What does running a VPS yourself involve?
On an unmanaged VPS, you or someone you hire handles setup, security updates, the firewall, backups, monitoring and tuning. Liquid Web defines it this way: “Unmanaged, or self-managed, VPS is a hosting option where you handle server management tasks, including setup, software installation, security, updates, backups, and ongoing maintenance.”
Liquid Web draws the line at the virtual machine: “The provider manages the physical hardware, core network, power, and virtualization platform. Your team manages what runs inside the virtual server.” (Liquid Web) The recurring jobs inside that line:
- Patching the operating system and web stack. Patching continues after setup.
- Moving PHP versions on schedule. PHP’s support policy gives each branch “two years from its initial stable release” of full support, then “two additional years for critical security issues only”. On the PHP project’s supported-versions table, security support for PHP 8.2 ends on 31 December 2026 and for 8.3 on 31 December 2027 (PHP). Test each move before you make it.
- Backups, and proof that a restore works. Liquid Web: “Snapshots can support a short-term rollback, but they should not replace an independent backup and tested recovery process.” (Liquid Web)
- Monitoring that reaches a person. Liquid Web again: “Monitoring software alone doesn’t resolve an incident. Your plan should identify who receives alerts, what they check, and how quickly they respond.” (Liquid Web)
- Worker and cache tuning. On self-managed stacks, the cache rules for member pages are yours to write. MemberPress’s hosting page tells GridPane users they “need to add this piece of code to either a website-specific config or a server-level config to exclude default MemberPress-generated pages”, and RunCloud users to add the MemberPress URL paths to an exclude list in the RunCache settings (MemberPress).
What does it cost in time and tools?
Liquid Web notes that an unmanaged VPS “may require additional spending on control panel licenses, security tools, backup storage, monitoring software, outside technical help, or internal system administration.” (Liquid Web) The monthly server price can be only one part of the total cost. For a plan-by-plan view of what managed platforms charge, see our pricing comparison for membership sites.
Is a VPS with a control panel a fair middle?
It can be. A panel or provisioning tool automates part of the work. MemberPress’s page describes RunCloud as “not an actual hosting company but more of an interface that can be used by several cloud hosting providers”, and its list also includes GridPane (MemberPress). A panel can automate some tasks, but verify who receives alerts, responds to incidents and tests restores. LifterLMS’s advice for the self-managed route: “If you’re technically inclined or have a developer in your team, you could opt for a VPS.” (LifterLMS)
When does managed hosting or a cluster make sense?
When the people who would run the server are busy running the business, or when an hour of downtime costs real money, hand the matrix to someone whose job it is. Liquid Web lists the same triggers for choosing a managed VPS, and a cluster can add a second server ready to take over, at higher cost and complexity.
Liquid Web’s list includes: “The server supports a business-critical website or application”, “Downtime could affect customers or revenue” and “You do not have an internal system administrator”. It also notes: “Even technically experienced teams may choose managed hosting for production workloads when server administration is not the best use of their time” (Liquid Web). The same page adds a warning: “Managed doesn’t mean the provider handles every application, plugin, script, or code problem.” Read the support scope before you rely on it.
This article gives no member counts or traffic cutoffs. The right size comes from measuring your own site. Estimate workers with the PHP workers guide and calculator, test with the load testing guide, and see how we think about concurrent users for what the numbers mean.
Where does MemberHost fit?
MemberHost is managed hosting for membership, LMS and community sites. Each client gets their own node or cluster with dedicated resources, as virtual machines on bare metal hardware we specify. We manage the environment and configure caching per site. Failover is available only on clustered setups.
We’re not the right pick for everyone. If your site is small and quiet, or the budget is tight, a good shared or managed WordPress plan is a fair choice, and LifterLMS’s own guide says as much for small sites. We make the most sense when downtime or slowness costs you members and you’d rather not staff the server work yourself.
If you’re weighing a VPS against handing the work off, get a free site speed audit. We run synthetic load tests on concurrency and PHP worker usage and tell you what we find.
Frequently Asked Questions
Is a VPS faster than shared hosting?
It can be, because a VPS may give you more control over resource allocation and server configuration. Speed still depends on how the server is set up. Liquid Web warns that “an unmanaged VPS may perform worse than a well-maintained managed server” when it isn’t configured and maintained properly (Liquid Web).
Do I need a VPS for LearnDash or BuddyBoss?
BuddyBoss says shared hosting “is not recommended” and lists “VPS, Dedicated Servers, or Managed WordPress Hosting” as ideal (BuddyBoss), so a VPS is one of three options. LearnDash’s requirements page lists software minimums and doesn’t name a hosting type (LearnDash).
What’s the difference between a VPS and a dedicated server?
A VPS is a virtual server that runs on a physical machine; its resource allocation depends on the plan. A dedicated server is the whole physical machine for one customer. Neither label says who manages it. WP Engine notes that “Managed refers to the operational service model, while dedicated refers to how physical server resources are allocated” (WP Engine).
Is managed WordPress hosting a VPS?
Not necessarily. Managed WordPress hosting describes a service: the host runs WordPress-specific infrastructure for you. Some plans isolate resources, and LifterLMS says optimized WordPress hosting is still technically shared (LifterLMS). Check what the plan says about resources and PHP workers.
How many PHP workers does a VPS have?
You configure the worker limit on an unmanaged VPS, subject to the server’s CPU and memory. The PHP workers guide explains how to estimate a limit from your own request rate and PHP time.