Explore what your community could build.
FeaturesBUILD Building blocks your community can combine. Comparison tableCOMPARE How Bonfire differs from other community platforms. Case studiesSTORIES How communities are shaping Bonfire for their needs. About BonfireABOUT The project, principles, and people behind it. Try Bonfire at the campground ↗ Launch your BonfireChoose how much you want to run yourself.
Self-hostDIY Your infrastructure and some sysadmin comfort. Cooperative hostingHOST Your own space without a sysadmin job. Co-design with usWITH For communities, organisations and funders with specific needs. Compare all three routes → EcosystemFind people, answers, and tools around Bonfire.
ParticipateJOIN Contribute, collaborate, or help sustain the commons. FAQsASK Licensing, federation, privacy, and governance. DocumentationDOCS Setup guides and technical reference for hosts and builders. Browse the source code ↗ Blog Get startedCommunity
Whoever you are, there's a way to take part. Come to listen, lend a hand, bring your community, or sustain the care work.
Where we gather
Day-to-day talk: questions, half-formed ideas, what people are working on. The easiest door: just say hello.
Join the chat →Our open test instance. Make an account, break things, tell us what felt wrong. Data may get reset now and then, don't move in.
Sign up on the campground →Where we post news, share what we're building, and converse in public. Follow, reply, boost.
Follow @Bonfire →Ways to help
We keep a list of small, well-described tasks specifically for newcomers to the codebase.
Browse good first issues →Bonfire so far speaks English, German, and a bit of other languages like Italian, French, Catalan, etc. If yours is missing, you can fix that.
Translate on Transifex →Something felt wrong, confusing, or inaccessible? That's may be a bug. Tell us, especially the small annoyances.
Open an issue →Elixir, Phoenix, LiveView. Set up a local environment from the docs and dig into an extension.
Read the docs → Get the code →If something confused you, it'll confuse the next person. Writing it down is a real contribution.
Suggest a doc fix →A feature, a better flow, a challenge to an assumption we've made. We'd rather be argued with early.
Open a proposal →Bring your community
Real communities with real needs are what move this project. Co-ops, collectives, unions, newsrooms, research groups, care and mutual aid networks... come tell us how you actually work, and we'll shape a space around it together. Everything we build with you goes back into the commons, for whoever needs it next.
Support the care work
Most funders want to pay for the new and shiny, rather than maintenance, like fixing bugs, answering questions, keeping things usable on old phones and slow connections, moderating, translating. That work is what makes software trustworthy.
A chunk of unglamorous work: a bug fixed, a question answered, docs unstuck.
Back it →Helps us slow a release when someone's ill or burnt out, instead of pushing through.
Back it →Or fund a specific feature, a circle, or a co-design sprint with your community.
Let's chat →The 33 who already do
Assemblée Virtuelle
BG
Benjamin Goering
Dragan Espenschied
ES
Eric Schultz
GL
Giacomo Leidi
G
Guest
IN
Incognito
IN
Incognito
JY
Jeffrey Yasskin
JK
John Kilcoyne
Marek Ľach
Mayel
MI
michcia
MD
mindaugasd
Nathan Schneider
pinage404
Fiscal host: Open Source Europe · every expense is public on Open Collective
Thank you
These contributors backed our crowdfunding campaign. We're grateful to every one of them.
Stay in touch
Something else in mind? There are humans at the other end.
team@bonfire.cafe →Everyone here must abide by the code of conduct. It's long, specific, and rooted in care, because a commons only works if people are safe in it.
Read the code of conduct