Community & Support

ChurchCRM isn’t made by a company. It’s made by volunteers around the world — developers, translators, testers, writers, designers, and church staff — who share one conviction: every church deserves access to high-quality management tools, free.

Ready to get involved yourself? The Contributing Guide has exact next steps for every skill. This page is about everything around that: where the community actually talks, how support works, and how the project is run.

Where Community Happens

Discord is the real-time home — questions, feature discussion, translator coordination, and introductions all happen there. It’s free, it’s where open-source communities already gather, and conversation there feels like being part of something rather than filing a ticket.

GitHub holds everything durable: issues, discussions, and pull requests. docs.churchcrm.io is where churches learn to use the software day to day. The blog covers releases, church stories, and tutorials.

For anything private — security reports or general inquiries — email info@churchcrm.io or security@churchcrm.io (see the Security Policy).

Getting Support

Stuck on a feature? Check the documentation, ask on Discord, or search GitHub Discussions.

Found a bug? Check existing issues first, then file one using the Bug Reporting Guide — include your version, browser, and steps to reproduce.

Have a feature request? Open an issue explaining the problem it solves for your congregation. The community discusses whether it fits the project’s direction.

Security issue? Email security@churchcrm.io directly — never post vulnerabilities publicly.

Support here is community-driven, not a paid help desk: active issue tracking, documentation, and a responsive volunteer community — not SLAs, phone support, or commercial guarantees. That’s the tradeoff of free, community-owned software, and churches that choose ChurchCRM understand it. In practice, the community responds quickly and generously.

Leadership & Decision Making

A small group of long-term core maintainers oversees architecture and releases. Contributors — developers, translators, designers, writers — improve the project day to day. Users — churches and individuals — shape direction through feedback. Major decisions happen openly on Discord and GitHub, not behind closed doors.

It’s not a top-down hierarchy, so some discussions take longer — the tradeoff for software that actually listens to the people using it.

History & Evolution

ChurchCRM has existed in various forms since the 1990s (as ChurchInfo). It’s still here because the community kept investing in it — fixing bugs, translating it, documenting it, supporting each other. That’s still how it works today: the project only improves because volunteers choose to make it better.

All community spaces — Discord, GitHub, anywhere else — follow our Code of Conduct.

Ready to get involved? → Read the Contributing Guide or join us on Discord.