Free online community platform: what the free plans give you, and how to test one
A free online community platform is a sensible way to start. If you are gathering customers, students, members of a club or the readers of a newsletter, a free plan gets you spaces, posts and events without a monthly bill, and several options do that well.
What free plans are careful about is scale and control: how many members, whose name is on the door, and who can moderate. Those are exactly the things that start to matter once the community works.
This page covers the four kinds of free, the decision to make first, what free plans usually hold back, and six tests to run before you invite anyone.
The four kinds of free
1. The free plan of a hosted community platform
Spaces, posts, events and member profiles, free up to a limit — often a member cap, the platform's branding, or its address instead of yours.
What it costs you: the cap, and the move. Communities are hard to move once they work, because members follow habits, not links. Check the price at the size you hope to reach, not the size you are.
2. A group on a social network or chat app
The most common free community of all: a group on a social network, or a server in a chat app.
What it costs you: ownership. The platform owns the members, its feed decides what they see, and search, structure and export are whatever it allows. It is a good place to start a conversation and a hard place to keep one.
3. Open source, self-hosted
Forum or community software you install and run yourself.
What it costs you: operations and moderation. Hosting, updates, spam and backups are yours, and a community holds members' personal details, so security updates are not optional.
4. Free because they earn on your members
Platforms that cost nothing if you charge members for access, and take a percentage of what members pay.
What it costs you: the share, on every payment, for as long as members pay. Free membership software shows how to work out whether that is worth it.
Decide what the community is for first
Community products lean in different directions, and free plans lean harder.
Discussion. Questions and answers that stay useful for months and are found through search. Structure matters more than speed.
Conversation. Real-time chat. Fast and lively, and hard to search later.
Events and learning. Calendars, RSVPs and sessions, sometimes with courses alongside.
Customers of a product. Support, ideas and feedback, often beside the product itself.
Then decide who can join: anyone, invited people only, or paying members. That one choice changes which free option fits.
Which kind of free fits your community
| Your community | Best kind of free | Watch for |
|---|---|---|
| A conversation starting around a newsletter or channel | A social or chat group | Moving members later |
| A club, alumni or interest group meant to last | A hosted free plan | The member cap, and the platform's address |
| Customers of your product | A hosted plan, or open source if you have a technical team | Single sign-on, and who owns the data |
| A paid community | A platform with paid access built in | The share of every payment |
What free plans usually hold back
We keep a hand-counted inventory of what community software actually documents, built from 60 products. Here is a selection, with how many of the 60 document each:
| Capability | Products (of 60) |
|---|---|
| Spaces, groups and channels | 50 |
| Articles, resources and files | 48 |
| Data export, deletion and retention | 48 |
| Community guidelines, terms and consent | 45 |
| Posts, discussions and replies | 41 |
| Events, RSVP and reminders | 41 |
| Single sign-on, API and integrations | 41 |
| Direct messages and chat | 39 |
| Notifications with member preferences | 30 |
| Member directory and connections | 24 |
| Roles and scoped access | 20 |
| Reports and a moderation queue | 9 |
| Privacy, blocking and messaging controls | 4 |
Free plans usually include the top of that list: spaces, posts, events. What they tend to hold back:
Your own address and brand. Often a paid feature, and it matters more than it seems: a community on someone else's address is a community you are building for them.
Roles and moderation tools. Only 20 of the 60 document roles and scoped access at all, and 9 a moderation queue. On a free plan, moderation is often the owner deleting posts by hand.
Single sign-on and integrations. 41 of the 60 document them, frequently on paid plans. That matters most for a customer community, where members already have an account with you.
Member caps. Covered above. They arrive when the community starts working.
Set these rules before you invite anyone
Most community problems are rules nobody decided. Write these down, then check the platform can carry out each one:
| Rule | What to decide |
|---|---|
| Joining | Open, request to join, invitation only, or paid |
| Posting | Who can post where, and who can start a new space |
| Profiles | What members see about each other — and what they never see |
| Messages | Who can message whom by default, and whether members can change it |
| Reports | What can be reported, who reviews reports, and how fast |
| Removal | What gets a post removed or a member suspended, in plain words |
| Leaving | What happens to a member's posts and profile when they leave |
The profile and message rows are the ones free plans are least flexible about, and the ones members notice first.
Test a free community platform in an afternoon
Run these six with a few test accounts before you invite a single real member.
- Join as a stranger. Invite a test address and walk through joining. Count the steps; every step loses people.
- Make a private space. Post in it, then sign in as a non-member and search for a word from the post. Nothing should come back.
- Open the directory as an ordinary member. You should see names and what members chose to show, not their email addresses.
- Report a post. Then sign in as the member who wrote it: nothing should tell them who reported it. An ordinary member should not be able to open the moderation queue at all.
- Turn notifications down. Set a space to digest or off for a test member, post in it from another account, and check the setting is respected.
- Export everything. Members, spaces and posts. If you cannot take the community with you, you are renting it.
Five mistakes that stall a new community
Too many spaces on day one. Ten empty rooms feel like a closed shop. Start with two or three, and add spaces when conversations ask for them.
No guidelines until the first argument. 45 of the 60 products support guidelines or terms that members accept when they join. Write yours before the first post, not after the first dispute.
One moderator. A founder moderating alone burns out and becomes the bottleneck. Give a second person a role before you need one.
Launching empty. Seed a handful of real posts and questions before you invite anyone, so the first visit has something to answer.
Choosing a platform you cannot export from. Test the export before the first invitation, not when you want to leave.
Moving from a social group without losing people
Move with a date. Announce the new home, run both for a short overlap, then make the old group read-only with a pinned link. A group that stays open never empties.
Move the conversations, not just the people. Open the new space with the questions members are already asking, so they have a reason to reply there.
Invite in waves. Bring the most active members first, so the new space is lively when everyone else arrives.
What the first month should tell you
After four weeks, you should be able to answer five questions from the platform's own numbers:
- Of the people you invited, how many joined?
- Of those who joined, how many posted or replied at least once?
- How many came back in their second week?
- Which spaces have conversations, and which are silent?
- How many questions are still unanswered?
If the platform cannot tell you these, you are running the community blind. If it can and the answers are poor, the fix is almost never a new feature. It is fewer spaces, more seeded questions and a faster first reply.
When free stops being free
The member cap arrives first, usually just as the community starts working.
Then your own address and brand, when the community becomes part of how customers see you.
Then moderation roles and single sign-on, when one person can no longer read everything and members want one login.
The option worth considering at that point
For most communities, the next step is a paid plan of a hosted platform. Building your own starts to make sense when the community is part of a product you already run — a customer community inside your app, members who already have accounts with you — or when the rules are unusual: verified members only, several organisations sharing one space, or strict requirements on where data is kept.
A coding agent can build a working community in days, and it will look finished: spaces, posts, a member list, events. What it has to be told is who may read what about whom. Online community software features lists what has to be real, with a test for each, and the online community build-off shows three AI models working from the same specification.
If you do build with a coding agent, the Online Community planner is the specification we hand ours. You can sign into three community platforms built from it before deciding anything.