Forem

Last reviewed Aug 26, 2026 · 650 words

Forem is the only self-hostable community platform that ships the DEV experience: long-form articles in a proper editor, comments, tags, reactions, a feed, podcasts and listings, all under one login. It is also a full Rails monolith with Postgres, Redis and Sidekiq workers, and the 2 GB RAM floor is a floor, not a comfortable number. If your community is discussion-first, Discourse is easier to run and easier to moderate. If it is publishing-first, where members write posts and others respond, Forem is the tool, and this guide is about surviving the Hard rating.

The install path is not the one you expect

There is no docker run that gives you a working site. The supported self-hosting route is the forem/selfhost repository, which uses Ansible to provision a Fedora CoreOS host running the containers under Podman, with playbooks for DigitalOcean, AWS and Google Cloud plus a generic option for any VM. The compose file in the main repo exists for hacking on Forem, not for serving it. Budget a day for the first deploy, and expect to learn a little Ansible and a little CoreOS even if you never wanted to.

What you end up running: the Rails web app, Sidekiq workers for background jobs (emails, feed generation, image processing), Postgres, Redis and an image proxy. Email delivery needs a real SMTP provider from day one, because sign-up, notifications and digests all depend on it.

Sizing: 2 GB is survival, 4 GB is comfortable

A Rails app plus Sidekiq idles at well over 1 GB before Postgres and Redis take their share. On a 2 GB VPS, the first traffic spike or a large image import triggers swapping. A 4 GB VPS at about $20 to $25 a month at last check is the realistic starting point for a small community, and Postgres wants its own tuning once you pass a few thousand posts. Image storage is the other budget line: uploads want S3-compatible object storage rather than local disk, both for the CDN path and so the host stays disposable.

The feature list is both the draw and the burden

Everything DEV has, you have: article drafts with a Markdown editor and front matter, series, canonical URLs for cross-posting, reactions, reading lists, badges, moderation queues, an admin panel and a REST API. The catch is that all of it was built for one very large site, so a 200-member community inherits configuration surface designed for one 10,000 times bigger. The admin area has dozens of feature flags, and most of your first week is spent turning things off. Podcasts and listings in particular look nice until you notice nobody in a small group uses them.

Where Forem loses

The Reddit alternatives page covers the aggregation side properly. Forem's federation story is thin, its mobile experience is the web app, and the AGPL-3.0 licence means modifications to a public instance must be published. Development has also slowed from its 2020 to 2022 pace, so read the recent commit history before committing a community to it.

What I'd do

Only self-host Forem if the community is explicitly a publishing community: members write, others read and comment, and the DEV-style feed is the point. Then run it on a 4 GB VPS via the official selfhost playbooks, S3-compatible storage for images, a transactional email provider, nightly Postgres dumps off-box, and a monthly reminder to pull upstream. For anything that is mostly threads and replies, I would choose Discourse and never look back; the forums category lays out the rest of the field.