Build
Connect & operate
Design & teams
Start hereScope a build in one callBring a spec, a wireframe, or a paragraph. You leave with an architecture, a timeline, and a number.Book a scoping call
AI software
LLM & data systems
Vibe coding
Ready to ship?Put AI where the work isAgents, RAG, and private LLMs wired into the systems your team already uses — not a chatbot bolted to a homepage.Discuss an AI project
Domain firstWe learn your workflow before we model itRegulated, operational, or high-volume — the constraints belong in the schema, not in a training doc.Talk about your domain
Plan smarterEstimate before you commitCost ranges, scope templates, and the questions we ask in discovery — free, no form.Open the cost calculator
Real conversationsTalk with a technical leadNo SDR, no discovery gauntlet. The person on the call is the one who scopes the build.Book a call
Open-Source CRM · ChurchCRM

CRM

ChurchCRM is a free, open-source church management system written in PHP that handles membership, groups, events, and finances. Licensed under MIT, it supports 40+ languages and has an active community with 909 stars and recent releases.

Source: GitHub — github.com/ChurchCRM/CRM
909
GitHub stars
553
Forks
PHP
Primary language
MIT
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
RepositoryChurchCRM/CRM
OwnerChurchCRM
Primary languagePHP
LicenseMIT — OSI-approved
Stars909
Forks553
Open issues193
Latest release7.4.1 (2026-07-06)
Last updated2026-07-07
Sourcehttps://github.com/ChurchCRM/CRM

What CRM is

PHP-based web application providing attendance tracking, calendar management, and database-driven member/finance workflows. Last pushed July 2026 with 7.4.1 release; 193 open issues suggest ongoing development activity.

Quickstart

Get the CRM source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/ChurchCRM/CRM.gitcd CRM# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Small to mid-sized church membership management

Ideal for congregations needing donor/member tracking, attendance records, and event scheduling without licensing fees or vendor lock-in.

Multilingual deployments

40+ locale support makes it suitable for international or multicultural congregations seeking localized interfaces.

Self-hosted financial transparency

Open-source architecture allows churches to maintain full control over sensitive financial and membership data on internal servers.

Implementation considerations

  • PHP 7.x+ and database (MySQL/PostgreSQL) infrastructure required; verify hosting environment compatibility before deployment.
  • 193 open issues indicate active development; production deployment should account for potential breaking changes between minor versions.
  • Localization is crowdsourced via POEditor; translation completeness varies by language—review audit report before targeting specific locales.
  • No mention of API documentation, webhooks, or third-party integrations; assess custom integration requirements early.
  • Demo environment is read-write and shared; avoid testing with production data; use isolated staging instance.

When to avoid it — and what to weigh

  • Enterprise-scale deployments requiring SLA — No formal support, SLA, or hosted commercial service mentioned; not suitable for critical systems requiring guaranteed uptime.
  • Require advanced analytics or real-time reporting — No mention of BI tools, real-time dashboards, or export capabilities; may require custom development for complex reporting needs.
  • No in-house technical team — Self-hosted PHP application requires DevOps expertise for setup, maintenance, security patching, and database backups.
  • Strict regulatory/compliance requirements — No documented compliance certifications (GDPR, HIPAA, SOC2); requires audit before use with sensitive data in regulated contexts.

License & commercial use

MIT License—permissive open-source license permitting commercial use, modification, and distribution with minimal restrictions (retain copyright notice and license text).

MIT permits commercial deployment and customization. However, no formal support, warranty, or liability indemnity is provided. Organizations offering ChurchCRM-based services should clarify liability, support terms, and upstream attribution in their agreements.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityModerate
DEV.co fitGood
Assessment confidenceHigh
Security considerations

No security audit, CVE history, or formal security policy documented. As a PHP web app handling membership and financial data, review for SQL injection, CSRF, XSS, and authentication/authorization. Deployment must include HTTPS, regular patching, and database backups. Recommend security review before production use with sensitive data.

Alternatives to consider

Planning Center Online (PCO)

Commercial SaaS alternative with built-in support, compliance certifications, and hosted infrastructure; no self-hosting or coding required but involves licensing costs.

Breeze Church Management

Commercial cloud-based CRM with strong UX, real-time collaboration, and vendor support; trade-off: subscription cost and data ownership.

Elvanto

SaaS church management focused on mobile-first design and integrations; vendor-maintained with support tier but recurring fees.

Software development agency

Build on CRM with DEV.co software developers

Assess infrastructure, security, and integration requirements with our technical team. We can help plan deployment, customization, or migration from legacy systems.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

CRM FAQ

Can we use ChurchCRM for free in production?
Yes. MIT license allows free deployment, modification, and distribution. However, community support is voluntary; no SLA or guarantee is provided.
What data does ChurchCRM store and how is it protected?
Membership, financial, attendance, and event data stored in MySQL/PostgreSQL. Security depends on deployment environment (SSL, firewall, patching, access controls). No formal audit or compliance certification documented; review before handling PII or regulated data.
How do we get help or report bugs?
GitHub issues (193 open), Discord community, and documentation. No commercial support tier; fixes depend on maintainer capacity and community contributions.
Can ChurchCRM integrate with our existing tools (Stripe, Google Workspace, etc.)?
Not clearly stated. Database design suggests custom API or export is possible, but specific integrations and webhooks not documented. May require custom development.

Software development & web development with DEV.co

From first prototype to production, DEV.co delivers custom software development around tools like CRM. We staff experienced engineers for integrations, web development, and ongoing support across open-source crm and beyond.

Ready to evaluate ChurchCRM for your organization?

Assess infrastructure, security, and integration requirements with our technical team. We can help plan deployment, customization, or migration from legacy systems.