Open Source XenForo Alternatives

Discourse is a community platform for organizations that want complete control over how and where their site runs. It has been in production for over a decade, and self-hosting removes the dependence on a forum vendor deciding pricing, data location and feature direction.

The backend is a Ruby on Rails application answering RESTfully in JSON, and the frontend is an Ember.js app talking to that API. PostgreSQL holds the main data store while Redis serves as cache and transient storage.

The platform gives community managers several distinct surfaces to work with.

• Discussion topics: the core format, built for conversations that stay readable over time.
• Real-time chat: a built in channel alongside threaded discussion.
• Themes: an ever growing set of official and community themes for changing how a site looks.
• Plugins: extend the site with tools such as Discourse AI chatbots and SQL analysis through Data Explorer.

Running it in production needs Ruby 3.4 or later, PostgreSQL 15 and Redis 7, with an install guide in the repository and development setups documented for Docker, macOS, Ubuntu, Debian and Windows. The latest stable releases of Safari, Chrome, Edge and Firefox are supported, along with iOS and Android. Official hosting exists for teams that prefer to skip server maintenance entirely.

Flarum is a discussion platform for your website, built on the idea that forum software should be quick to deploy and pleasant to read. There is no clutter, no bloat and no complex dependency chain, which suits communities that want conversation rather than a heavyweight administration surface.

The back end is PHP, so it deploys the way most shared hosting and small servers already expect. The interface is powered by Mithril, a performant JavaScript framework with a tiny footprint, which keeps the client quick across desktop and mobile without a separate app.

Three ideas shape how the project describes itself.

• Fast and simple: no clutter and no heavy dependencies, so installation and daily use stay quick.
• Beautiful and responsive: the interface is designed to be consistent and intuitive across platforms out of the box.
• Extensible: the architecture is flexible, with an extension API for customizing and integrating Flarum with the rest of a site.

Getting started means following the installation guide, and help comes from the documentation, the community forum and the Discord chat. Security issues have their own disclosure policy rather than the public issue tracker, and the software is MIT licensed.

Before cloning, note one thing about the layout. This repository holds only the Flarum skeleton application, and most development happens in the separate core repository, which is where code contributions belong.

Storyden takes the bulletin board forum and rebuilds it for the present. A single instance can run a forum, a blog, a news feed, a curated set of links, a directory or a knowledge base, so a community does not have to scatter itself across a chat server, a wiki and a link aggregator.

Trying it takes one command. A container image published to the GitHub registry runs the whole application and opens on port 8000, and the project documents self-hosting on a plain VPS.

A few conventions are worth knowing before running it in earnest.

• Version numbers: releases combine a fixed major, a year marker and a counter, which reads more like a build number than a semantic version.
• API stability: semantic versioning is not used, so breaking changes are avoided and, when unavoidable, called out in release notes and a separate list.
• Development builds: versions outside a release commit carry a post suffix to show you are off a stable release.
• Content types: discussion threads, wiki style pages, structured data and shared links all live in the same instance.
• Deployment: the container is the supported path, with local development instructions kept in the repository.

The stated motivation is that most forum software is decades old, insecure, abandoned or simply unattractive, and Storyden answers that with a modern language, simple deployment and a design meant to be looked at. It suits someone who remembers 2000s internet forums and wants one without the maintenance that came with them.