Reviewed by the SEOPointz team · Last reviewed June 2026. The platform requirements and Discourse sizing figures below are drawn from official docs and current self-hosting guidance, not vendor marketing. SEOPointz may earn a commission from some links; it never changes what we recommend.
A social or community site fails differently from a normal website. A blog can cache a page once and serve it to a thousand readers; a community can’t, because almost every view is personalised—your feed, your notifications, your unread count. That makes community platforms write-heavy, memory-hungry, and unforgiving of cheap hosting in a way that catches a lot of founders off guard. This guide is about matching the host to the kind of community you’re building, so the site stays fast as the membership—and the activity—grows.
Why community sites are harder to host than blogs
The economics of caching break down the moment content becomes personal. When every member sees a different activity stream, the server has to assemble pages on the fly and write to the database constantly: every post, like, comment, follow, and private message is a write. Add real-time features—live notifications, presence indicators, chat—and you’re holding open connections and burning memory. The practical upshot is that community platforms care far more about RAM, database performance, and the ability to scale than a brochure site ever will. Cheap shared hosting can run a small community, but it tends to wobble exactly when you succeed: when activity spikes.
Pick your platform first—it dictates the host
Hosting needs flow from the software you choose, so decide that first. Three routes dominate. BuddyPress (or BuddyBoss) on WordPress turns a familiar WordPress site into a social network with profiles, activity feeds, private messaging, and groups—great if you already live in the WordPress ecosystem. Discourse is the gold standard for long-form, threaded discussion: developer forums, support communities, and topic-driven groups. And hosted community SaaS (Circle, Mighty Networks, and similar) removes hosting from the equation entirely in exchange for a monthly fee and less control. Your choice here sets your whole infrastructure path.
What the leading platforms require
BuddyPress is a WordPress plugin, so its baseline is WordPress’s own—a modern PHP version and MySQL/MariaDB—but the real constraint is the same as any active WordPress site under load: enough memory and a database that isn’t fighting noisy neighbours on a shared box. Discourse is more demanding because it runs as its own Docker stack. The current self-hosting guidance is a minimum of 2 GB RAM, 2 CPU cores, and around 20 GB of disk plus a 2 GB swap file, with 4 GB RAM and 2–4 vCPUs being a comfortable production setup. One sharp edge worth knowing: a Discourse container rebuild needs roughly 1.5 GB of free RAM on top of what’s already running, so a 2 GB server can run out of memory mid-upgrade—which is a strong argument for not buying the bare minimum.
| Platform | Best for | Typical hosting | Watch out for |
|---|---|---|---|
| BuddyPress / BuddyBoss | WordPress-based social networks & membership sites | Managed WordPress or VPS with ample RAM | Plugin sprawl and database load as members grow |
| Discourse (self-hosted) | Forums and discussion-led communities | VPS/cloud: 2 GB RAM min, 4 GB comfortable | Rebuilds need ~1.5 GB free RAM; needs Docker comfort |
| Discourse (official hosting) | Teams wanting Discourse without server admin | Managed; plans roughly $20–$300/mo | Cost climbs with members and features |
| Hosted SaaS (Circle, Mighty, etc.) | Creators who want zero infrastructure | None—fully managed | Least control; you don’t own the stack |
Size for your peak, then leave headroom
Communities don’t grow in a straight line—they grow in bursts when a post goes viral or a launch lands. The mistake is provisioning for today’s quiet average and getting caught flat when activity triples overnight. Choose a host that makes scaling up genuinely easy: a VPS or cloud plan where you can add RAM and CPU without migrating servers beats a rigid shared plan you’ll have to abandon. And always buy a little headroom above the minimum—not just for traffic, but for the maintenance operations (backups, upgrades, rebuilds) that themselves consume resources.
Uptime, backups, and trust
A community runs on trust, and nothing erodes it faster than a site that’s down or that loses members’ posts. Insist on at least a 99.9% uptime guarantee, SSL by default, DDoS protection, and—above all—regular, restorable backups. Communities accumulate something irreplaceable: years of member-generated discussion. Losing it isn’t an inconvenience, it’s the end of the community. Test a restore before you need one. It’s also worth choosing a data-centre region close to where most of your members are, since latency on every interaction is felt more in a real-time community than on a static page.
Frequently asked questions
Can I run a community site on shared hosting?
For a small, low-traffic community, yes. But because community pages are personalised and write-heavy, shared hosting tends to slow down as activity grows—and a sluggish community quietly loses the members who make it worthwhile. Plan to move to a VPS or managed plan once engagement picks up.
Is BuddyPress or Discourse the better choice?
It comes down to format. BuddyPress (or BuddyBoss) suits social-network-style sites with profiles, feeds, and groups inside WordPress. Discourse is purpose-built for threaded, long-form discussion and is the stronger choice for forums and support communities. They’re different tools for different community shapes.
How much does it cost to host a community?
Self-hosting BuddyPress can start on modest managed WordPress or VPS plans, while a self-hosted Discourse server realistically wants a 2–4 GB VPS. If you’d rather skip server admin, Discourse’s official hosting runs roughly $20 to $300 a month depending on size, and hosted SaaS platforms price by members and features. Match the spend to the activity you actually have, not the activity you hope for.
Because a busy community puts real strain on the server, it’s worth understanding how to keep things responsive—see why speed in web hosting matters, and since you’ll be holding members’ personal data and discussions, read our guide to web hosting security before you launch.
