Reign

From 100 to 100,000+ members

Hosting for Reign community sites.

5 tiers, real numbers, from your first 100 members to enterprise scale. What to pick, what to check, when to upgrade. From the Wbcom team that has shipped 2,000+ Reign community sites since 2013.

No affiliate links. We name the hosts and recommend tiers based on what we have actually deployed for paying customers.

5 hosting tiers

Match your member count. Read across.

Find your active member count in the badge. Read what hosting tier fits, what to check at signup, and when you will need to upgrade.

Starter

Under 500 active · Shared WordPress hosting

You are still validating your community. Speed matters less than cost. The bottleneck on shared hosts is not Reign - it is slow PHP, shared CPU contention, and missing object cache. Acceptable until you hit ~300 daily active members.

Recommended hosts

  • Hostinger Premium
  • Bluehost Choice Plus
  • SiteGround StartUp
  • A2 Hosting Drive

$5 - $15 / month

What to check at signup

  • PHP 8.2 or 8.3 available (PHP 7.x is end of life - avoid)
  • MySQL 8.x or MariaDB 10.6+ supported
  • At least 256 MB PHP memory limit (512 MB ideal)
  • cPanel / direct database access for backups
  • Free SSL via Let's Encrypt included

When to upgrade

You see consistent slow admin loads, BuddyPress activity feed takes 3+ seconds, or hosting CPU throttles you during member registration spikes.

Growing

500 - 5,000 active · Managed WordPress hosting

Most paid Reign community sites land here. Managed WordPress hosts handle PHP-FPM tuning, server-level caching, daily backups, and staging - so you spend zero time on infrastructure. Object cache (Redis or Memcached) is included on every major managed plan and pays for itself within a week of activation.

Recommended hosts

  • Cloudways DigitalOcean 2 GB
  • WP Engine Startup
  • Kinsta Starter
  • SiteGround GoGeek
  • Pressable Starter

$30 - $50 / month

What to check at signup

  • Redis object cache included or 1-click activatable
  • NGINX with FastCGI cache (default on managed WP)
  • PHP-FPM workers configurable (matters for BuddyPress concurrency)
  • Staging environment included
  • Daily backups + 1-click restore
  • Free SSL + free CDN front (Cloudflare or built-in)

When to upgrade

BuddyPress activity feed slows past 10,000 activity entries. Member directory queries crawl. You add LMS + marketplace + 1,000+ products and database pressure climbs.

Established

5,000 - 25,000 active · Larger managed WordPress or managed VPS

Community traffic patterns get spikier. You need 4 - 8 GB RAM, NVMe SSD, multiple PHP workers, and ideally MySQL on a separate node. ElasticPress or Algolia replaces MySQL search - this single move halves your member directory load. Cloudflare CDN in front becomes non-optional.

Recommended hosts

  • Cloudways Vultr HF 4 GB
  • WP Engine Growth
  • Kinsta Pro
  • Cloudways DigitalOcean Premium 4 GB
  • Pressable Personal

$80 - $200 / month

What to check at signup

  • NVMe SSD (not standard SSD)
  • Dedicated CPU cores - not burstable / shared
  • Object cache + page cache + edge cache all configured
  • ElasticPress or Algolia for member + content search
  • Cloudflare or BunnyCDN in front
  • Monitoring + alerting on PHP memory, MySQL slow query log

When to upgrade

BuddyPress activity table over 200,000 rows. Database connections cap during peak. Member directory pagination slows past page 50. You need to shard or archive.

Large

25,000 - 100,000 active · Enterprise WordPress or dedicated infrastructure

You are now running infrastructure, not just a website. MySQL needs read replicas for the activity feed. Image delivery moves to a dedicated CDN. BuddyPress cron jobs need queue workers (rather than wp-cron on page loads). Full-page cache at the Cloudflare edge becomes a hard requirement.

Recommended hosts

  • WP Engine Premium
  • Kinsta Business
  • Pressable Business
  • Cloudways Vultr HF 8 GB +
  • self-managed on AWS / GCP / DigitalOcean

$300 - $1,500 / month

What to check at signup

  • MySQL read replicas configurable
  • Queue worker (separate cron / job runner) - not wp-cron
  • Dedicated media CDN (Cloudflare or BunnyCDN at edge)
  • BuddyPress activity table archived or sharded
  • PHP memory 1 GB+ per worker
  • Direct SSH access + ability to install custom mu-plugins
  • SLA + 24/7 support included

When to upgrade

Sustained traffic above 500 requests / second. Cross-region members. Compliance requirements (HIPAA, SOC 2, FERPA) drive infrastructure choice.

Massive

100,000+ active · Custom infrastructure

At this scale Reign code is not the bottleneck. You are solving infrastructure: multi-region database, edge caching, queue workers, separate media + member-asset domains, often a custom Worker layer in front. The Wbcom team has built and shipped a handful at this scale - typically enterprise alumni networks, large associations, crypto and dating communities.

Recommended hosts

  • Self-managed on AWS
  • Self-managed on GCP
  • Self-managed on Azure
  • Pantheon Elite
  • WP Engine Enterprise

$2,000+ / month

What to check at signup

  • Multi-region deployment (read replicas in 2+ regions)
  • Custom Worker / Lambda layer for hot paths
  • BuddyPress activity sharded by member ID or time bucket
  • Separate domains for media + member assets
  • Observability stack (Datadog, New Relic, or open-source)
  • Dedicated infrastructure team or trusted partner

When to upgrade

You need IPO-ready or M&A-ready infrastructure. Compliance requires custom architecture. Talk to the Wbcom team early.

Universal recommendations

Six things every Reign site needs. Tier-independent.

Whether you are on shared hosting or running multi-region AWS, these six choices matter at every scale.

PHP version

PHP 8.2 or 8.3 across every tier. PHP 7.4 is end of life and increasingly unsupported by major plugins. PHP 8.1 still works but expect 5-10% slower BuddyPress activity rendering vs 8.2.

MySQL version

MySQL 8.0+ or MariaDB 10.6+ minimum. The BuddyPress activity table query patterns benefit from newer indexing. If your host is on MySQL 5.7 or older, the BuddyPress activity feed slows down 2-3x at scale.

Object cache

Redis or Memcached on every Reign site past 500 members. Pays for itself within a week of activation - turns most BuddyPress + Reign page loads from 10+ database queries into 1 cached lookup.

CDN

Cloudflare in front of every production Reign site. Free tier is enough for most starter + growing communities. Move to Pro ($25/month) once you have member-only images that need polish-on-delivery.

Backups

Daily off-server backups minimum. Test the restore once before you launch - many backup plugins fail silently on large databases (BuddyPress activity tables get big fast). UpdraftPlus, BackWPup, or your host's native backup all work if tested.

Email delivery

Never send transactional emails through your hosting provider's default mailer. Use Mailgun, Postmark, Amazon SES, or SendGrid for member registration, password resets, BuddyPress notifications. Hosting-provider email gets flagged as spam past a few hundred members per day.

Hosting questions

FAQ.

Does Reign run on shared hosting?

Yes for communities under 500 active members. Past that, shared hosting becomes the bottleneck - not Reign. Move to a managed WordPress plan ($30-50/month) as soon as BuddyPress activity feed loads take more than 2 seconds.

Do I need Redis for a Reign community site?

Strongly recommended past 1,000 active members. Most managed WordPress hosts include it. Object cache turns most BuddyPress + Reign page loads from 10+ database queries into 1 cached lookup. The single biggest performance win on any growing Reign community.

How big can a Reign community get on $30/month managed WordPress?

Comfortably to 5,000 active members on a Cloudways DigitalOcean 2GB, WP Engine Startup, or Kinsta Starter plan. The bottlenecks at that size are usually BuddyPress activity tuning + ElasticPress search, not the hosting tier itself.

Cloudflare in front of WordPress + BuddyPress - any gotchas?

Two main ones. (1) Logged-in member sessions need to bypass cache - the BuddyPress Activity Cache plugin handles cookie-aware rules. (2) Real-time BuddyPress notifications need polling, which the CDN should NOT cache. Set a cache-bypass rule for /wp-json/buddypress/ endpoints. The Wbcom setup package configures both for you.

Should I self-host on AWS / GCP for a Reign community?

Only if you have a dedicated DevOps person and 25,000+ active members. Below that scale, managed WordPress hosts (Cloudways, WP Engine, Kinsta) deliver the same performance with zero infrastructure work. Self-hosting becomes worthwhile at the scale where multi-region database + custom CDN layer matter - typically 50,000+ members or strict compliance requirements.

Does Reign theme add a hosting overhead vs other community themes?

No. The Reign theme adds minimal PHP overhead - it is mostly templates + CSS. At any scale the bottleneck is BuddyPress activity table queries + MySQL search + image delivery. Same bottlenecks any WordPress community theme would hit. Reign code is competitive with BuddyBoss, Kleo, and BuddyX at every scale.

Planning a 10,000+ member launch?

The Wbcom team does hosting + caching + database scale audits as part of the standard support queue. Email support@wbcomdesigns.com with your projected member count + community shape and we will recommend a stack.