Reviewed by the SEOPointz team · Last reviewed June 2026. We’ve set up and run forum and membership communities on both shared plans and VPS boxes, so the resource numbers below come from real deployments. SEOPointz may earn a commission from some links; it never changes what we recommend.
A static blog and a community site ask very different things of a host. The moment people start logging in, posting, replying, uploading avatars and refreshing notification feeds, every request hits your database instead of a cached HTML file. That’s the part most beginners underestimate when they try to build a social network: the hosting bill isn’t driven by how many pages you have, it’s driven by how many people are active at the same time. This guide walks through what a community actually demands from a host, which platform makes sense at your size, and where the cheap option quietly falls apart.
Why community sites are heavier than normal websites
On a regular brochure site, a visitor reads cached pages and leaves. On a community, almost every interaction is a write to the database — a new post, a like, a private message, a “mark as read.” Those queries can’t be served from a static cache, so they consume CPU and memory on every click. Entry-level shared hosting is built for the cached-page world: in practice a shared plan comfortably handles roughly 20–50 concurrent users before response times start to slide. A forum with 30 people online at 8pm can sit right at that ceiling, which is why so many new communities feel sluggish exactly when they finally get busy.
Choosing your platform first, then the host
The software you pick decides what hardware you need, so settle this before you buy a plan.
- BuddyPress + bbPress (on WordPress): free, familiar, and easy to bolt onto an existing WordPress site. It’s the lowest-friction way to add profiles, activity feeds and forums. The trade-off is architectural: performance gets visibly harder to manage as a forum grows past roughly 10,000 posts, and you’ll lean heavily on caching and a good host to keep it smooth.
- Discourse: purpose-built modern forum software. The application itself is free and open-source, but it expects a PostgreSQL database, Redis, and a working outbound email service — it is not a “drop it on shared hosting” product.
- Hosted/managed community platforms: you pay monthly and skip the server work entirely. Sensible if you’d rather moderate than maintain.
What Discourse really needs to run
Discourse is the one people most often get wrong, because the software being free makes it look cheaper than it is. The official minimum is 2 GB RAM, 2 CPU cores and around 20 GB of disk, plus a 2 GB swap file — and 4 GB RAM is the realistic recommendation for a comfortable production forum. The swap detail matters: rebuilding the Discourse container needs roughly 1.5 GB of free memory on top of what’s already running, so on a bare 2 GB box an upgrade can fail mid-rebuild with an out-of-memory error unless you’ve added swap. That rules out shared hosting completely; Discourse belongs on a VPS or cloud server where you control RAM, the database and email.
Self-host or pay for managed?
This is mostly a question of your size and whether you have anyone comfortable on a Linux command line. Hosted Discourse is the hands-off route, with an entry plan around $20/month and the widely-used standard tier around $100/month (always check current pricing on Discourse’s site before committing, as tiers change). Self-hosting is meaningfully cheaper for smaller communities — below roughly 1,000 daily active users, a modest VPS (around $6–$12/month), a transactional email service such as Mailgun (~$10/month) and offsite backups (a few dollars a month) can land near $27/month all-in. The catch is that those savings assume your time is free; once you’re past about 10,000 daily active users, the engineering hours usually cost more than just paying for managed hosting.
Matching the host to your stage
| Community size | Sensible setup | Rough monthly cost |
|---|---|---|
| Just starting / under ~50 members online | BuddyPress on quality shared or starter cloud hosting | $3–$15 |
| Growing forum, hundreds of members | Managed cloud VPS (e.g. Cloudways-style) with caching | $11–$30 |
| Active Discourse forum, self-hosted | VPS (2–4 GB RAM) + email service + backups | ~$27 |
| Large or non-technical team | Fully hosted Discourse plan | $20–$100+ |
The pricing above is indicative and moves over time — treat it as a sense of scale, not a quote.
Don’t forget email, backups and moderation load
Two costs sneak up on community owners. The first is transactional email: notifications, password resets and digests need a real sending service, because forum email volume will get a self-hosted mail server blacklisted fast. The second is backups — a community is its members’ content, and losing a week of discussion is far more damaging than losing a week of blog posts. Budget for automated, offsite backups from day one rather than treating them as an upsell.
Frequently asked questions
Can I run a community on cheap shared hosting?
For a small BuddyPress site with light activity, yes — but expect it to strain once you have more than about 20–50 people online at once. Discourse, on the other hand, won’t run properly on shared hosting at all because it needs PostgreSQL, Redis and at least 2 GB of dedicated RAM.
Is self-hosting Discourse actually cheaper than the paid plan?
For smaller communities, yes — a tuned VPS setup can cost roughly a quarter of the standard hosted plan. But that assumes you’re comfortable maintaining a Linux server and handling updates. Factor your own time in; above several thousand daily active users the managed plan often works out cheaper overall.
How do I know when to upgrade?
Watch for slow page loads during your busy hours, rising CPU usage in your hosting dashboard, and timeouts when several members post at once. Those are the classic signs your plan has hit its concurrency ceiling.
Once you’ve picked a platform, the host underneath it is what keeps the community fast as it grows — for the WordPress route start with our guide to the best web hosting for WordPress websites, and if you’re running a mission-driven group, see our notes on web hosting for nonprofits.
