Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Hosting · Guide

How to Choose Hosting for a Membership Site

Short answer

Choose hosting for a membership site by starting with logged-in traffic, not page views. Pick a plan with PHP 8.3 or newer, a 256 MB WordPress memory limit, at least 6 PHP threads, cache exclusions for login and account pages, daily backups, staging, and a real cron for renewals. Then confirm the renewal price before you buy.

Key takeaways

  • Member pages are mostly uncached, so logged-in traffic needs PHP threads and database headroom, not just page cache.
  • WordPress.org recommends PHP 8.3 or newer, MariaDB 10.11 or newer or MySQL 8.4 or newer, and HTTPS support, as of November 2026.
  • MemberPress lists PHP 7.4 or newer, MySQL 8.0 or newer, and WordPress 6.5 or newer, but you should plan to the stricter WordPress.org numbers.
  • Kinsta says its Single Site membership plans include 6 or more PHP threads, as of November 2026.
  • Exclude /register, /login, /mepr, /account, /thank-you, and /unauthorized from server-side caching.
  • Budget $11 to $469 a month for hosting alone, as of November 2026, and always check the renewal price at checkout.

What makes hosting for a membership site different?

A membership site needs hosting built for logged-in traffic, because most member pages cannot use page cache.

A public blog can serve the same cached page to thousands of visitors. A membership site cannot do that for logged-in members, because each member sees different content, prices, and account details.

Each logged-in page load runs PHP and checks the database for that member's access level. That work uses server power on every visit, so a plan that looks fast for a blog can slow down once members sign in.

Kinsta puts this plainly on its membership hosting page: it recommends plenty of PHP threads for logged-in users, plus site-level caching with simple purge and exclusion controls.

What server specs does a membership site need?

Pick a host that runs PHP 8.3 or newer, a current database, HTTPS, and a WordPress memory limit of 256 MB or more.

ItemMinimum to accept, as of November 2026Source
PHP8.3 or newerWordPress.org
DatabaseMariaDB 10.11 or newer, or MySQL 8.4 or newerWordPress.org
WordPress memory limit256 MB or moreWooCommerce
Web serverApache or NginxWordPress.org
HTTPSActive on every pageWordPress.org

WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.4 or greater, and HTTPS support. It also notes that WordPress still runs on PHP 7.4 and MySQL 5.5.5, but those versions have reached end of life and may expose a site to security issues.

If you sell with WooCommerce, the bar is set in the same place. WooCommerce asks for WordPress 6.9 or greater, PHP 8.3 or greater tested up to PHP 8.4, MySQL 8.0 or greater or MariaDB 10.6 or greater, HTTPS, and a WordPress memory limit of 256 MB or greater, for WooCommerce 10.8 and later.

MemberPress sets a lower floor, so do not stop there. MemberPress lists PHP 7.4 or newer, MySQL 8.0 or newer with NO_ZERO_DATE and Strict Mode disabled, and WordPress 6.5 or newer. Plan to the stricter WordPress.org numbers, and treat the plugin floor as a last resort.

Check the numbers on a live site under Tools, then Site Health, then Info. If you use WooCommerce, open WooCommerce, then Status, and look for red flags on PHP, database, and memory.

How many PHP workers do you need?

Start with at least 6 PHP threads if you expect members online at the same time, and ask the host for the exact number on your plan.

A PHP worker, also called a PHP thread, handles one uncached request at a time. When all workers are busy, the next member waits in a queue, and logins and checkouts slow down first.

Kinsta gives a clear starting point. Its membership page says its special Single Site plans include 6 or more PHP threads, as of November 2026, and it recommends plenty of threads for logged-in users.

Ask each host these 3 questions in writing before you buy:

  • How many PHP workers or threads does this plan include?
  • Can I buy more workers without moving to a larger plan?
  • What happens when workers run out: do requests queue, or does the site show an error?

If a host will not give a number, treat that as a warning sign. A membership site with paying members needs a limit you can plan around, not a guess.

How should caching work on a membership site?

Cache public pages only, and keep login, account, checkout, and member pages out of page cache.

Page cache stores a finished page and serves it to the next visitor. That saves work on a sales page, but it can show one member's account page to another member, or show a paywall to a paying member.

MemberPress is direct about this risk. Its technical requirements page says the paywall and SEO features will not work with any kind of page caching enabled.

Its hosting guide adds that object caching and Varnish are the most common problem sources, and that MemberPress-related URIs should be excluded from server-side caching. MemberPress lists the pages to exclude, and the same list works as a starting point for other membership plugins.

Exclude these paths from page cache:

  • /register
  • /login
  • /mepr
  • /account
  • /thank-you
  • /unauthorized

Note the split on object cache. Kinsta offers an optional Redis object cache add-on, while MemberPress says it does not recommend that add-on for its plugin. Follow your membership plugin's own guide first, and test any object cache change on staging.

What about cron, renewals, and payment webhooks?

Choose a host with a real server cron or a documented alternate cron, so renewals and emails run on time even when traffic is low.

WordPress runs scheduled jobs with WP-Cron, which only runs when someone loads a page. On a quiet site, a renewal, an expiry, or a reminder email can run late because no visit triggered it.

A server cron fixes that by running on a clock, not on visits. Ask the host if you can set a server cron job, how often it can run, and whether the host offers one by default.

MemberPress gives one worked example. On WP Engine, it says to enable Alternate Cron through support, and that this service checks for due crons every minute. That is the kind of concrete answer you want from any host.

Payment webhooks need the same care. The /mepr path must stay uncached and reachable, so Stripe or PayPal can tell your site that a payment went through. If webhooks fail, payments can sit in a pending state while the member waits for access.

How much does hosting cost for a membership site?

Budget $11 to $469 a month for hosting alone, as of November 2026, with most small membership sites near $28 to $65 a month.

Host and planStarting price, as of November 2026Renewal note
Kinsta membership plansFrom $27 a month for Single and Dual-Site plansMultiple-site plans from $68 a month; Enterprise from $469 a month
SiteGround StartUp$2.99 a month for the first 12 monthsRenews at $17.99 a month
SiteGround GrowBig$4.99 a month for the first 12 monthsRenews at $29.99 a month
Cloudways Flexible, DigitalOcean 1 GBFrom $11 a monthSame price at renewal; billed by the hour
WP Engine Essential, 1 site$35 a month, or $28 a month in year 1 on annual billingRenews at $35 a month

Kinsta lists its membership prices on its own membership page, with 2 months free on annual billing and a 30-day money-back guarantee. Cloudways charges by the hour with no visit caps, so the price follows server size, not traffic.

SiteGround shows the largest gap between intro and renewal prices in this table. GrowBig costs $59.88 for the first 12 months at $4.99 a month, then $359.88 a year at $29.99 a month, so write the renewal figure in your budget.

For the full yearly picture, including the plugin and payment fees, see how much a membership site costs to run.

Which hosting type fits which size of site?

Use shared hosting only to start small, managed WordPress hosting for a growing paid site, and cloud hosting when you need control over workers and cron.

Hosting typeBest forWatch out for
Shared hostingA new site with few members and no paid launch yetHidden worker limits and shared resources
Managed WordPress hostingA paid site that needs staging, backups, and supportVisit caps and overage fees on some plans
Cloud hostingA growing site that needs a set server size and cron controlMore setup work and no single site price
Dedicated or enterprise hostingA large site with steady peaks and strict uptime needsA much higher monthly price

Shared hosting is the cheapest start, but it shares server power with other sites. That matters more for members, because their pages cannot use page cache to hide a slow server.

Managed WordPress hosting fits most paid membership sites. Look for one-click staging, daily backups, free SSL, and support that will set cache exclusions for you.

Cloud hosting fits when you want to pick the server size yourself. Cloudways starts at $11 a month for a 1 GB DigitalOcean server, and its 4 GB Premium server costs $54 a month, as of November 2026.

How do you choose and move in 7 steps?

You can pick a plan and move a membership site in about 1 to 3 hours of active work, plus time for DNS changes to spread.

  1. Write down your plugin and its needs: MemberPress, WooCommerce Memberships, or another plugin, plus PHP, database, and memory numbers.
  2. Shortlist 2 hosts that meet those numbers and publish cache exclusion controls, staging, and daily backups.
  3. Ask each host in writing about PHP workers, cache exclusions, server cron, backup frequency, and staging.
  4. Buy the plan that answers all 5 questions, and note the renewal price and any visit cap.
  5. Install WordPress and your membership plugin on staging, then set the cache exclusions from the earlier section.
  6. Move the live site with the host's free migration service, or with a backup plugin, and check DNS after the move.
  7. Test as a member before you tell members about the move.

For general hosting checks that apply to any WordPress site, see how to choose WordPress hosting.

Allow 30 to 60 minutes to test on staging. That test is where most cache and cron problems show up, while they are still easy to fix.

How do you check that the hosting works after launch?

Log in as a test member, buy or renew a test membership, and watch for slow pages, cached member pages, and missed emails.

Run these 6 checks in order:

  • A logged-out visitor sees the paywall on protected content.
  • A logged-in test member sees only their own account details.
  • The /account and /login pages load fresh each time, with no other member's data.
  • A test payment or renewal reaches your site, and the member gains access.
  • Renewal and welcome emails arrive within a few minutes.
  • A backup from after the move exists, and you know how to restore it.

If a member page shows the wrong content, turn off page cache for that path first, then clear the cache and test again. If renewals run late, check the cron setup next.

Speed still matters after the move. See how to speed up WordPress before you pay for a larger plan, since image size and plugin load can cut the hosting you need.

Backups are part of the check, not an extra. See how to back up WordPress and confirm that daily backups run and that you can restore one.

What mistakes should you avoid?

Do not pick hosting on the first-year price alone, and do not leave member pages in page cache.

  • Budgeting from an intro price, then facing a renewal at 3 to 6 times that price.
  • Leaving /account, /login, and /mepr in page cache, so members see the wrong pages.
  • Turning on object cache or Varnish without checking your membership plugin's guide first.
  • Relying on WP-Cron alone for renewals on a quiet site, with no server cron.
  • Skipping a staging test, then finding a cache problem on the live site.
  • Picking a plan by visit count alone, when logged-in members use far more PHP time per visit than blog readers.

Ask the host for the worker count, the cache exclusions, the cron setup, and the renewal price in writing. If any answer is missing, keep looking before you move paying members.

Frequently asked questions

Can I run a membership site on cheap shared hosting?

Yes, for a small new site with few members, but check the limits first. Shared hosting shares server power, and member pages cannot use page cache, so logins can slow down sooner than on a blog. Ask for the PHP worker count, the cache exclusion controls, and the renewal price. Move to managed or cloud hosting once you have paying members or regular peaks.

Do I need Redis or object caching for a membership site?

Not always, and it can cause problems if it is set up wrong. Object caching can cut database work, but MemberPress says object caching and Varnish are the most common problem sources for its plugin and should be disabled. Follow your membership plugin's own guide, test any change on staging, and keep member pages out of page cache either way.

How do I stop members seeing each other's account pages?

Exclude the member paths from page cache: /register, /login, /mepr, /account, /thank-you, and /unauthorized. Then clear the cache and test with two test accounts. If a page still shows the wrong member's details, turn off page cache for that path at the server level and ask host support to confirm the exclusion is active.

What is a PHP worker, and why does it matter for members?

A PHP worker, also called a PHP thread, handles one uncached request at a time. Logged-in members bypass page cache, so each of their page loads uses a worker. When all workers are busy, the next member waits in a queue. Kinsta says its Single Site membership plans include 6 or more PHP threads, as of November 2026, which is a useful starting point.

Should I host membership videos on the same hosting plan?

No, in most cases. Video files use a lot of storage and bandwidth, and they can push a small plan over its limits during a launch. Host videos with a video service or a media host, and keep the WordPress plan for pages, logins, and checkouts. Check the host's storage and bandwidth limits before you upload large files.

When should I move from shared hosting to managed hosting?

Move when you have paying members, regular logins at the same time, or renewals that must run on time. Managed hosting adds staging, daily backups, and support that can set cache exclusions for you. Move sooner if logins slow down at peak times, if cache problems keep coming back, or if the renewal price is close to a managed plan.

Sources

  1. Requirements WordPress.org
  2. WooCommerce Server Recommendations WooCommerce
  3. What are the technical requirements to run MemberPress? MemberPress
  4. What Web Hosting Works Best with MemberPress? MemberPress
  5. WordPress Membership Website Hosting Kinsta
  6. Cloudways Pricing and Plans Cloudways

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test