An open source community platform is software whose source code is public and free to run, modify and host, used to give a group a shared home for discussion, profiles, events or content. Discourse is a well-known example.
This guide sits inside the wider community platform coverage on this independent, non-commercial site, which has no affiliation with any project it describes.
What an open source community platform actually is
A community platform bundles the pieces a group needs to talk and organise: accounts, a place to post, ways to reply, moderation tools and some notion of membership. “Open source” adds a licensing promise. Anyone can read the code, run it on their own server, change it and, within the licence terms, share those changes.
The practical difference from a hosted social network is control. With a self-run platform, the community decides where data is stored, which rules apply, how the site looks and whether to move to another host later. The trade-off is responsibility: someone has to install updates, take backups and answer to members when things break.
Discourse illustrates the model. Its repository describes it as “a 100% open-source community platform for those who want complete control over how and where their site is run.” The same page lists the licence as GPL-2.0, a copyleft licence under which modified versions must remain open when distributed. The project also states that its back end is a Rails app, built on Ruby on Rails, which tells a prospective host what skills and runtime the software expects. The page notes that the maintainers sell official hosting for those who prefer to skip server management, a common arrangement where the software is free and convenience is paid for.
Main kinds of community software
Community platforms are not one product category. They group into a few families, and picking the wrong family is the most common reason a launch stalls.
Forums and discussion boards
Threaded forums suit long-lived, searchable conversation: support questions, hobby knowledge, project governance. Discourse and NodeBB are typical examples. Threads stay findable months later, which makes them good for building a knowledge base as a side effect of talking.
Federated social networks
Federated tools such as Mastodon, Lemmy, Pixelfed and PeerTube run as independent servers that can still exchange posts with one another. Each server sets its own rules, yet members can follow people elsewhere. This suits groups that want a public-facing voice and reach beyond their own members.
Groups, events and organising tools
Some projects focus on gathering people in person. Mobilizon, for example, is listed on Wikipedia’s ActivityPub page under event management and groups, and Gancio as a calendar and event planner. These replace the shared spreadsheet or the event page on a commercial site.
Personal-site and profile-centred tools
Older projects, Friendica and Hubzilla among them, combine blogging, profiles, file hosting and events in one installation. They appeal to communities that want each member to have a durable home page rather than a feed slot.
How federation connects separate communities
The feature that makes modern open platforms different from the self-hosted forums of the past is federation. Instead of each site being an island, many speak a shared protocol. The standard behind most of them is ActivityPub, which this site covers in its own guide.
According to Wikipedia, the standard was first published by the World Wide Web Consortium as a W3C Recommendation in January 2018 by the Social Web Working Group. The same article says it provides a client-to-server API for creating and modifying content, plus a federated server-to-server protocol for delivering notifications and content to other servers. It also calls ActivityPub the defining standard of the Fediverse, a decentralised social network made of independently managed instances.
In practice this means two layers. Clients, such as a phone app, talk to a member’s home server. Servers then talk to each other so that a reply written on one site shows up on another. A community can therefore stay small and self-governed while still taking part in a larger conversation.
Discovery is the other half. A server needs a way to turn a handle such as a name at a domain into the address of an account. That job is handled by webfinger, a lookup convention that most federated platforms implement alongside ActivityPub.
Choosing a platform for a specific community
A sensible choice starts with the group, not the software. A few questions narrow the field quickly.
- What is the main activity? Long discussions point to a forum; announcements and public reach point to a federated network; meetups point to an events tool.
- Who will run it? A volunteer with server experience can self-host. A group without that skill may prefer a managed host, or a project that offers a simple installer.
- How open should it be to outsiders? Federation widens reach but also brings moderation work from content arriving from other servers.
- What licence is acceptable? GPL-style licences keep derivatives open, which matters to groups that want a guarantee against the code being closed later.
- Can data leave? Export tools and open standards reduce lock-in if the community outgrows the first choice.
Trying a small pilot with a handful of members usually reveals more than reading feature lists. The pilot shows how moderation feels, how members react to the interface and how much maintenance the host really faces.
Running costs, moderation and sustainability
Free software is not free to operate. Servers cost money, and so do the volunteer hours spent on upgrades and security. Many projects, Discourse among them, fund development through paid hosting of the same code, so the community can choose between running it and paying the maintainers to do so.
Moderation is the larger long-term cost. Open platforms give administrators tools for roles, blocking and reporting, but they do not supply policy or people. A written code of conduct, a small team of trusted moderators and clear escalation rules matter more to a community’s health than any technical feature. Discourse’s repository itself links a code of conduct and a contributing guide, a pattern worth copying for community spaces.
Sustainability also depends on the project behind the code. Active repositories, regular releases, a public security policy and a documented way to contribute are signals that the software will still be maintained in a few years. A platform that is abandoned leaves a community running unpatched software, so these signals deserve as much weight as features.
Frequently asked questions
What is an open source community platform?
It is software with publicly available source code that lets a group run its own discussion, profiles or events on infrastructure it chooses, under a licence that permits modification and sharing.
Is Discourse really open source?
Its GitHub repository lists the GPL-2.0 licence and describes the project as a 100% open-source community platform.
Do open platforms need ActivityPub?
No. Many forums work as standalone sites. ActivityPub matters when a community wants members to interact with accounts and posts on other servers.
Can a non-technical group run one?
Yes, usually through a managed host or a volunteer with server skills. Self-hosting still brings duties such as updates, backups and moderation.
