OpenSourceCRMs

Methodology

How We Verify Every CRM in This Directory (and What We Leave Out)

• 5 min read • By the OpenSourceCRMs team

Our methodology: public source, not archived, real license file, recent activity. Plus the projects we removed or declined and why.

A directory is only useful if you can trust it. Here is exactly how we decide what gets listed, what the data on each page means, and which popular projects we excluded.

What a CRM must have to be listed

  1. A public source repository that anyone can read and clone.
  2. A real license file that we have opened and read, not just a badge or a claim on the website.
  3. An open license. Non-commercial and source-available licenses are excluded. Open-core projects are listed with a clear note.
  4. Not archived, and with repository activity in the last year.
  5. A real CRM function: managing contacts, leads, deals, customers, donors or similar relationships. ERP suites are included only when they ship a CRM module.

Where the data comes from

Stars, last update, language and archive status come from the public GitHub API. License text comes from each repository's LICENSE file. Descriptions are based on the project's own README and website. Every page shows the date we verified the data. Numbers change daily, so treat them as a snapshot.

What we do not do

  • We do not take money to list or rank a project.
  • We do not install and load-test every CRM, so we do not claim performance numbers.
  • We do not copy marketing copy. We summarize what the project documents.

Projects we removed or declined

These findings are as of 14 October 2026 and may change:

  • YetiForce: its GitHub repository is archived and the LICENSE file is a non-commercial license. We removed it from the active list.
  • NocoBase: the repository now carries a custom license agreement rather than an OSI-style license.
  • Erxes and AlphOne: both describe themselves as source-available.
  • Wukong CRM (the open source usage-agreement edition): distributed under a custom usage agreement.
  • DaybydayCRM: we could not find a LICENSE file in the repository.

If a project changes its license or a maintainer disagrees with how we have described it, contact us and we will review it.

Suggest a CRM

Know a project that meets these rules? Submit it and include the repository link. We check the license and activity before listing it.

Frequently asked questions

How do you verify the CRMs in this directory?

Each project needs a public repository, a real open license file that we have read, no archived status and recent activity. Data comes from the GitHub API and each repository LICENSE file.

Why was YetiForce removed from the active list?

When verified on 14 October 2026, its GitHub repository was archived and its LICENSE file was a non-commercial license rather than an open source license.

How can I suggest a CRM?

Use the submit page and include the repository link. We check the license and activity before listing it.

Keep reading

Browse all 50 open source CRMs →