Campfire is 37signals' self-hosted group-chat system, sold under its ONCE line: rooms, direct messages, @mentions, search, and file attachments that a team runs on its own server instead of renting per seat. The code is MIT-licensed, the 2026 edition is rebuilt on Rails 8 with SQLite, and one person installs it with a single command then invites the team through web or mobile browsers.[1][2]
Quick verdict
Small teams, non-profits, and communities that want to own their chat data will get the most from Campfire. Its self-hosted rooms, direct messages, full-text search, attachments, and installable mobile app cover everyday team chat, and the MIT code now costs nothing to licence. Teams with nobody to run a server, and organizations needing documented SSO or compliance exports, should stay on managed chat instead. If you can operate one Linux server, self-host Campfire; if not, keep paying Slack or Teams for that convenience.[1][2]
Key features
Public and private rooms Run open rooms for the whole team alongside private rooms for sensitive threads, with unread indicators showing what is new since each person last looked.[1]
Direct messages and @mentions Take side conversations into direct messages and pull people into a thread with @mentions, the same two primitives teams expect from managed chat.[1]
Full-text search with saved searches Search the whole archive by keyword and keep repeat queries in a saved-searches sidebar, so standing topics stay one click away.[1]
File attachments with previews Drop files into any room or message with inline previews, keeping shared documents next to the discussion that produced them.[1]
Web Push and installable PWA Get notified through Web Push and install the mobile web app on phones, covering on-the-go use without native store apps.[1]
Chatbot integrations over HTTP Wire custom bots and notifications into rooms through a chatbot HTTP API instead of waiting on a vendor app directory.[1]
Single-command install, automatic updates Install with one command on your own domain and leave automatic updates on, or switch them off to upgrade on your own schedule.[1][2]
Dark mode, audit log, spam controls Work after hours in dark mode while administrators keep an audit log of activity and block spammers from open rooms.[1]
Who will love it
Small teams that want to own their chat data: MIT code plus SQLite on your own server means the archive lives with you, not with a vendor.[1][2]
Non-profits and communities escaping per-seat fees: no subscription and no per-user charge fit groups whose headcount outgrows their budget.[1]
Rails-friendly operators: a standard Rails 8, SQLite, Redis, and Kamal stack is easy to inspect, adapt, and debug for teams already in that world.[1]
Who should avoid it
Teams with nobody to run a server: someone must provision the machine, hold the domain, and handle updates and backups, since no vendor-managed hosting exists.[1][2]
Organizations requiring documented SSO or compliance exports: neither appears on the official pages checked, so regulated procurement cannot finish from public evidence.[1][2]
Mobile-first workforces and very large rooms: phones are served by a PWA rather than native apps, and public evidence positions Campfire at small-team scale.[1]
Reported experience
Repository-published signal plus one directory listing: the README's printed 4,600+ stars and 775 forks with an open invitation to issues and discussions, and an Alternativeto listing with platform tags only.
1 cited community source. No original Reddit or G2 user reports were accessible in this pass (direct Reddit reads failed; the G2 page showed no Campfire-specific reviews), so no sentiment or prevalence inference is possible and no user experience is quoted.
The visible community signal in this pass is the repository itself, credited in its README with 4,600+ stars and 775 forks and an open invitation to file issues and join discussions, plus a third-party directory listing. No original Reddit or G2 user reports were accessible, so this assessment carries no quoted user experience and no sentiment claim.[1][2]
Alternatives and compatibility
Slack is the incumbent this decision is read against, with Microsoft Teams as the second catalogue edge. Choose Slack or Teams for zero operations, native mobile apps, and managed reliability; choose Campfire when data ownership, MIT code, and freedom from per-seat pricing outweigh managed convenience.[1][2]
Because Campfire is free software with no subscription, a mixed posture is practical: keep the regulated or non-technical majority on managed chat while a technical group runs Campfire where ownership matters most.[1][2]
Questions worth asking
What is the best Campfire alternative for non-technical users?
Slack or Microsoft Teams remain the safer pick for non-technical users: managed hosting, native apps, and support with no server to operate. Choose Campfire when owning the chat data and avoiding per-seat fees outweigh that convenience. This stays conditional because no head-to-head testing was done in this pass.[1][2]
Is Campfire really no-code?
Using it is no-code: rooms, direct messages, search, and file sharing work in the browser with no scripting. Running it is not: someone must provision a server and domain, deploy with Kamal or Docker, and keep updates and backups going. Plan for operator time even though the chat UI itself needs none.[1][2]
How much does Campfire cost per month?
The software licence costs nothing: the ONCE page lists Campfire at $0, down from a $299 one-time price, with a 30-day free trial and no per-user fees stated. The monthly cost is whatever the operator pays for the server, storage, and domain, plus their time. The same page still mentions $150 packs of 10 extra users from the paid era, so confirm current pack terms before budgeting.[1]
Can you self-host Campfire?
Yes, self-hosting is the whole point: install it on Ubuntu with Nginx under your own domain, deploy with Kamal or Docker, and switch automatic updates off if you prefer manual control. There is no vendor-managed hosting option, and a bare repository checkout alone is not a running instance. SSO availability is not documented on the pages checked.[1][2]
Sources and editorial review
Source research. Reviewed on October 9, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
Repository-published signal plus one directory listing: the README's printed 4,600+ stars and 775 forks with an open invitation to issues and discussions, and an Alternativeto listing with platform tags only. No original Reddit or G2 user reports were accessible in this pass (direct Reddit reads failed; the G2 page showed no Campfire-specific reviews), so no sentiment or prevalence inference is possible and no user experience is quoted.
- ONCE Campfire: pay once, use it forever
official · Observed October 9, 2026
ONCE Campfire product page: one-time pricing history ($299 struck through to $0 since September 2025), 8 users included, $150 10-user packs text, 30-day trial, self-hosting on own domain with Ubuntu and Nginx, Rails 8 plus SQLite 2026 rebuild, forums and email support, affiliate and student terms.
- basecamp/once-campfire repository
official · Observed October 9, 2026
Official repository README: MIT licence, Ruby 3.4.5 and Rails 8.0.2 stack, Kamal deployment, full feature list (rooms, DMs, mentions, search, saved searches, attachments, dark mode, audit log, spam blocking, PWA, push, bots), v1.5.1 release line, printed 4,600+ stars and 775 forks, open invitation to issues and discussions.
- ONCE Campfire directory listing
community · Observed October 9, 2026
Third-party directory listing for ONCE Campfire: short product description and platform tags (Mac, Windows, Linux, Android, iPhone, iPad, self-hosted). Used only as a listing-existence signal; directory copy is not product evidence and carries no user review.