MemberPress hosting where the paywall and the cache agree.
MemberPress decides who sees what on every single request. A cache that does not know about those rules will happily hand protected content to somebody who never paid for it.
Everything a paywall asks of a host.
The rules engine, the payment gateway and the renewal queue each fail in a different way. The stack is configured for all three.
Protected URLs never come from cache
Any URL a MemberPress rule covers is served dynamically, and the presence of a MemberPress login cookie bypasses the page cache outright. Marketing pages and the pricing table still serve from the edge.
Gateway webhooks that always arrive
Stripe and PayPal notify your site at a URL that must never be cached, never be challenged as a bot and never be rate-limited. Those endpoints are excluded from all three, so a renewal is recorded the first time it is sent.
Expiry that runs whether or not anyone visits
MemberPress schedules the jobs that expire subscriptions and send renewal reminders. Driven by wp-cron they run only when traffic arrives, which on a low-traffic membership site means days late.
Transaction tables that stay quick
Every payment, refund and status change is a row. The tables MemberPress reports read from are indexed for the queries the dashboard actually runs, so reporting does not slow down as the history grows.
Backups that include who paid for what
Members, subscriptions and transaction history in the same nightly snapshot as the content, replicated off the origin and restorable in one action from the dashboard.
See the paywall working.
The failures that matter on a membership site are quiet ones: a webhook that returned 500, a cron that stopped, a rule that started matching more than it should.
- One-click admin login, no shared passwords
- Webhook endpoint reachability checked
- Plugin and core updates with per-item status
- Restore any daily backup from the dashboard
Members-only pages, at public-page speed.
Protected pages cannot be cached, so their speed comes down to how fast the rules lookup and the member query answer. That is where the tuning goes.
What we change for MemberPress
These differ from a standard WordPress site on the same plan, and each one follows from the fact that MemberPress decides access per request.
| Setting | What we do | Why |
|---|---|---|
| Page cache | Bypassed on any URL a MemberPress rule covers, and whenever a MemberPress login cookie is present | The rules engine resolves access per visitor at request time, so a cached copy of a protected page is a copy that was authorised for somebody else and will be served to everybody. |
| Gateway webhook endpoints | Excluded from page cache, bot challenges and rate limiting; gateway ranges allowed | Stripe and PayPal retry a failed notification on a schedule of their own, so an endpoint that answers slowly or challenges the request turns a completed payment into a membership that silently never activates. |
| Scheduled jobs | MemberPress job queue driven by system cron at a fixed interval | Expiry and renewal reminders are scheduled events, and under wp-cron they fire only when a visitor happens to arrive — which on a paid site means lapsed members keep access and reminders go out days after the card was due. |
| Object cache | Redis, with membership and rule lookups held in memory | Resolving whether one member may see one page touches several tables on every request, and repeating that work per page view is what makes a members area feel slower than the public site in front of it. |
| Transaction table indexes | Added to match the columns MemberPress reports filter and sort on | Payment history only grows, and the dashboard queries that scan it are the first thing to time out once a site has a few years of subscriptions behind it. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Will caching leak my paid content to non-members?
Why do my Stripe renewals sometimes not register?
Do subscriptions expire on time on a quiet site?
Can I use MemberPress with WooCommerce on the same site?
Does the backup include member and payment records?
Run MemberPress where the cache respects your rules.
Free migration, webhooks that are never cached, and expiry that runs on time.