Forem gives you DEV's publishing model, not a small forum kit
Forem is the application behind DEV, and its center of gravity is the article. Members publish posts, build profiles, join discussions, and receive material through feeds. That is a different product choice from installing a compact message board. Organizations that want a branded writing community get a working model to start from. Teams that only need topics and replies inherit far more code than the job calls for.
The size makes that distinction concrete. We checked out 6,687 files, roughly 358,599 lines of source, and 103.5 MB of repository data at commit 000c183. The backend is Rails, while the frontend is moving toward Preact. A team adopting Forem therefore owns an established application with a mixed stack, migrations, background work, and years of product assumptions. The payoff is that those assumptions already support a public community at DEV scale.
What happened when we ran it
Our sandbox installed the JavaScript side in 71 seconds. Yarn added 1,376 packages and occupied 974 MB on disk, then the build completed successfully in 5 seconds. For a codebase of this size, getting through installation and compilation without intervention is a useful result. It does not mean the checked commit was clean.
The Jest run exited with code 1 after 92 seconds. It passed 1,198 tests and failed 44 out of 1,242, spread across 7 failed suites. The log names tests for the article cover image, article display, onboarding, profile form, article options, title handling, and CSS utility documentation. One of 58 snapshots failed as well. The log tail does not identify a shared cause, so we would not write these failures off as one missing Debian package.
PostgreSQL with pgvector 0.8.0 is a hard requirement
The README says database migrations require pgvector version 0.8.0 or newer for HNSW indexing. That remains true if you skip semantic recommendations. A Gemini API key is optional, and the application can run without generating those embeddings, but the database extension itself is mandatory. That detail can rule out a managed PostgreSQL plan before you spend time on themes or imports.
Local setup also reaches beyond Node. Forem is a Rails application, and the linked installation guides cover native macOS and Linux environments. The README admits that parts of the documentation may fall behind the evolving code. Given the 44 test failures in our fresh run, follow the exact commit's prerequisites and keep a short record of any local fixes instead of treating the high-level quick start as a full deployment recipe.
Kamal 2 still leaves four services in your care
The beta Kamal 2 guide runs a web container, a Sidekiq worker, PostgreSQL with pgvector, and Redis. Initial deployment also needs SSH access, Docker on the relevant machines, a registry account, registry credentials, a Rails master key, a database URL, and PostgreSQL credentials. Kamal packages the procedure, but your team still owns those moving parts.
The guide is candid about production details. Database limits must cover both web and Sidekiq pools. Rolling deploys need shared fingerprinted assets so old pages do not request vanished files. Cloudflare must use Full or Full (strict) SSL mode to avoid redirect loops. On managed databases, an operator must confirm that pgvector exists and activate it before migrations. These are solvable jobs, though none belongs to a set-and-forget forum install.
September activity is healthy, while the test failure stays relevant
GitHub recorded a push on September 15, 2026, one day before our review, and listed 22,776 stars. The repository showed 134 combined issues and pull requests, while a separate issue search returned 38 open issues. Recent issue and pull request updates show an active project. The combined count is not a defect count, and the fresh push matters more than the absence of a latest GitHub release response.
Product work is still visible at the edges. Issue 23840 says spam comments that are deleted can still leave notifications in a user's inbox. That report concerns DEV and does not prove every private Forem has the same traffic or moderation burden. It does show why running community software involves policy and abuse handling alongside servers. Source access gives your team a place to fix the flow, not freedom from operating it.
Choose Forem only when the product shape earns the 974 MB install
Forem makes sense when articles, professional profiles, feeds, and discussion belong in one owned community. The 5-second build lowered the cost of evaluating it, and current repository activity is reassuring. The failed 44 tests, mandatory vector extension, four-service deployment, and AGPL obligations make the ownership decision much larger than that first successful build. If DEV's model is incidental to your goal, Discourse or NodeBB will usually ask less of the team that has to keep the lights on.