Free, open-source church management software — built by the community, for the Church.
ChurchCRM helps congregations manage membership, groups, events, and finances — with no licensing fees, no vendor lock-in, and full data ownership. Used by churches worldwide, available in 40+ languages.
| Repo | What it is | Who it's for |
|---|---|---|
| CRM | The main ChurchCRM application — PHP/Slim 4 backend, Tabler + Bootstrap 5 UI, Propel ORM, Cypress tests | Developers contributing features, bug fixes, and tests |
| Docker | Standalone Docker Compose setup for self-hosting ChurchCRM | System admins and self-hosters who want a containerized deployment outside of the main repo |
| Repo | What it is | Who it's for |
|---|---|---|
| ChurchCRM.io | The public marketing website at churchcrm.io | Designers and writers improving the homepage, blog, and landing pages |
| docs.churchcrm.io | User and administrator documentation at docs.churchcrm.io — built with TypeScript/Docusaurus | Anyone improving guides, tutorials, admin docs, or developer references |
| Repo | What it is | Who it's for |
|---|---|---|
| community-plugin-hello-world | Minimal reference plugin — the starting point for building a ChurchCRM community plugin | Plugin authors learning the plugin API and scaffold |
| WordPress-ChurchCRM-Calendar | WordPress plugin that displays ChurchCRM events on a public-facing church website | Developers extending ChurchCRM into WordPress sites |
churchcrm.io ← public marketing website (ChurchCRM.io repo)
│
└─ "Get Started" → docs.churchcrm.io ← user & admin docs (docs.churchcrm.io repo)
│
└─ "For Developers" → github.com/ChurchCRM/CRM ← the app itself
│
├─ core plugins (src/plugins/core/)
└─ community plugins (community-plugin-hello-world as template)
Self-hosting → Docker repo (standalone Compose setup, separate from dev containers in CRM)
Church website integration → WordPress-ChurchCRM-Calendar repo
Using ChurchCRM: → docs.churchcrm.io — installation, configuration, user guides
Contributing: → Join Discord and ask what's a good place to start — maintainers will point you to something concrete → See CONTRIBUTING.md for the full contributor guide → No code required — translators, writers, testers, and designers are all welcome
Reporting a bug: → Use Support → Report an Issue inside your ChurchCRM installation (auto-captures system info) → Or open a GitHub issue directly
ChurchCRM is built by volunteers and exists to serve the Church. Every contribution — code, translation, documentation, or feedback — helps a congregation somewhere run a little better.