When an SMB buyer asks an AI assistant which open source CRM to deploy, a shortlist comes back. We asked 44 different phrasings of that question across 2 engines, 88 answers in total, and counted every product named. This is the result. Nobody paid to be on it, and no vendor list was written in advance — the 29 vendors below are simply everyone the engines named.
Free to read, raw data included.
The board is re-measured every month. For $9.99 a month you get one email when your own row moves — your rank and answer count, who took the mentions you were absent from, and which of the 44 questions started or stopped naming you. Leave your address and I reply by hand with what your row reads today. What is in it, and the $29.99 one-off report →
sonar) searches the web while it answers and returned the sources used beside every one of those 44 answers — that column is what gets retrieved. Gemini (gemini-flash-latest) was called through its API with no tools and the near-empty system prompt quoted in the method below, so it answers out of the model’s own weights — not one of those 44 answers came back with a source. That column is what the model already remembers. Both are worth counting and they are not the same measurement: a product can be named often by what the models remember and rarely by what they retrieve, or the reverse, and the totals in the Answers column add the two together.“Answers” is how many of the 88 answers named that product.
Share is the same number as a percentage. The two right-hand
columns split it by engine.
Every row has its own link — the # beside a vendor name gives you
something like connexion.me/c/oscrm/#espocrm.
Click a vendor's name to see which of the 44 questions named them, and
click one of those to read the answer it was counted from, word for word.
| # | Vendor | Answers | Share | Gemini | Perplexity | |
|---|---|---|---|---|---|---|
| 1 | EspoCRM# | 82 | 93.2% | 43 | 39 | |
| 2 | SuiteCRM# | 81 | 92.0% | 41 | 40 | |
| 3 | Odoo (Community Edition)# | 43 | 48.9% | 27 | 16 | |
| 4 | Twenty# | 41 | 46.6% | 11 | 30 | |
| 5 | SugarCRM# | 16 | 18.2% | 16 | 0 | |
| 6 | Vtiger# | 16 | 18.2% | 8 | 8 | |
| 7 | ERPNext# | 11 | 12.5% | 8 | 3 | |
| 8 | Krayin# | 9 | 10.2% | 1 | 8 | |
| 9 | Dolibarr# | 4 | 4.5% | 1 | 3 | |
| 10 | YetiForce# | 4 | 4.5% | 0 | 4 | |
| 11 | CiviCRM# | 3 | 3.4% | 2 | 1 | |
| 12 | OroCRM# | 3 | 3.4% | 0 | 3 | |
| 13 | Frappe CRM# | 2 | 2.3% | 0 | 2 | |
| 14 | Bitrix24 On-Premise# | 1 | 1.1% | 0 | 1 | |
| 15 | BottleCRM# | 1 | 1.1% | 0 | 1 | |
| 16 | CRMX# | 1 | 1.1% | 0 | 1 | |
| 17 | Crust CRM/Corteza CRM# | 1 | 1.1% | 0 | 1 | |
| 18 | Django CRM# | 1 | 1.1% | 0 | 1 | |
| 19 | Erxes# | 1 | 1.1% | 0 | 1 | |
| 20 | Fat Free CRM# | 1 | 1.1% | 1 | 0 | |
| 21 | Grow CRM# | 1 | 1.1% | 0 | 1 | |
| 22 | Horilla CRM# | 1 | 1.1% | 0 | 1 | |
| 23 | InsulaCRM# | 1 | 1.1% | 0 | 1 | |
| 24 | LeadHub# | 1 | 1.1% | 0 | 1 | |
| 25 | openCRX# | 1 | 1.1% | 0 | 1 | |
| 26 | OpenEMR# | 1 | 1.1% | 0 | 1 | |
| 27 | PHP CRM# | 1 | 1.1% | 0 | 1 | |
| 28 | Relaticle# | 1 | 1.1% | 0 | 1 | |
| 29 | X2CRM# | 1 | 1.1% | 0 | 1 |
Everything above is free and stays free — the leaderboard, the method, all 88 raw answers and the machine-readable ranking, published in full at the bottom of this page. No vendor paid to be listed, no vendor can pay to move, and nothing here goes behind a login later.
What is for sale is one vendor's row, watched: $9.99 a month to be told when your rank moves, who took your mentions, and which phrasings started or stopped naming you — the board is re-run monthly and you get what changed. A one-off $29.99 deep report on a single row is the other option. What is in each →
Every claim on this page is reproducible from the files linked at the bottom.
Gemini (gemini-flash-latest), Perplexity (sonar). Each was called through its public API with a near-empty system prompt —
“answer the user's question directly and concisely” — and nothing else. The engines were
not asked to produce a list, rank anything, or name vendors. Steering them toward a list
would have manufactured the thing being measured.
44 distinct phrasings of one purchase decision, written before any measurement was run. No vendor name appears in any of them.
Each of the 88 answers was read back and every named product extracted. The vendor list is discovered: a product appears here if and only if an engine named it. Counted are open source and self-hostable customer relationship management (CRM) tools, and broader open source suites whose CRM module was named. Excluded, even when named: proprietary SaaS-only CRMs with no self-hosted edition, standalone marketing automation tools, help desk ticketing systems, ERP platforms with no CRM module named, content management systems, generic low-code backend/database tools with no pre-built CRM logic, project management tools, personal contact managers, and companies named only as an example user.
Spelling variants of one product are folded together, and a trailing “by company” is dropped. This run collapsed 25 spellings onto 6 of the rows below: “Odoo (Community Edition)”, “Odoo” and “Odoo Community” are one row — the one the table prints as Odoo (Community Edition). An edition name is folded into its product when it is that product’s name followed by a further word, and the plain name is at least three times as common. This run folded 2 such names, among them “Odoo CE” counts as Odoo (Community Edition) and “Vtiger CRM CE” counts as Vtiger. A name that merely begins with the same letters is a different product and keeps its own row. No pair was merged by hand in this category: every fold above is the rule applied mechanically, with no human judgement about who is who.
Beyond those folds a product is counted as the engines spelled it, and two rows in the table are never merged into one. When a product has been renamed or acquired and the engines still answer with both names, both names keep their own row: this page carries no hand-maintained list of who is now who, because that list would be a human claim about a mechanical count and nothing here could check it. What it has instead is the answers. Where an answer itself writes two of the rows below as one product renamed — the construction “X (formerly Y)” — the line beside those rows quotes that sentence and gives the overlap and the total, so the union is on the page. Nothing else produces that line. Two rows being named in the same answers does not, however often: the engines answer in shortlists, so the leaders of a category are named together whatever they are called. No answer in this run wrote two rows below that way, so no row below carries that line.
A product is counted once per answer, however many times that answer mentions it.
A leaderboard whose top ten reshuffles between runs would not be worth publishing, so this check was run before the page was, and the page ships only because it passed.
This measures what two answer engines said on 6 August 2026, in response to these questions, through their APIs. It is not a quality ranking, not a review, and not advice on which open source self-hosted CRM to choose. A product can be excellent and rank low here — that gap is the point.
All 88 answers, verbatim, one JSON object per line: run A · run B. The per-answer extracted product names: run A · run B. Machine-readable ranking: ranking.json.
What Perplexity was reading. It is the only one of these engines that returns a source
list, and the markers in its answers above — [1], [2] — point into
it. Every URL it cited, with the title, date and the excerpt it actually retrieved, one JSON
object per answer: run A ·
run B. Join on index to the
answers file, and read [n] as citations[n-1]. Perplexity returned a source list on 44 of its 44 answers. Gemini returned no sources at all — no citation, grounding or search-result field of any kind appears anywhere in its API response, on any of the 44 answers it gave. That is a fact about the engine, not a gap in this page.
Run A's 44 Perplexity answers cited 878 URLs across 159 distinct domains. Below are the 45 that were cited in three or more separate answers. Citations counts every URL from that domain, so a domain cited three times in one answer counts three times; Answers is how many of the 44 answers cited it at all.
| Domain | Citations | Answers |
|---|---|---|
| reddit.com | 101 | 44 |
| github.com | 45 | 27 |
| crm.org | 40 | 40 |
| youtube.com | 39 | 25 |
| suitecrm.com | 35 | 35 |
| marmelab.com | 34 | 34 |
| techradar.com | 34 | 34 |
| opensourcealternatives.to | 33 | 33 |
| technologyadvice.com | 29 | 29 |
| twenty.com | 28 | 28 |
| growcrm.io | 26 | 26 |
| espocrm.com | 25 | 19 |
| forbes.com | 24 | 24 |
| dev.to | 24 | 19 |
| techsy.io | 23 | 19 |
| gist.github.com | 17 | 17 |
| ossalt.com | 15 | 12 |
| medevel.com | 14 | 14 |
| monday.com | 14 | 14 |
| nutshell.com | 12 | 12 |
| selfhostedcrm.com | 12 | 11 |
| devdiligent.com | 11 | 9 |
| softwarerecs.stackexchange.com | 9 | 8 |
| krayincrm.com | 8 | 8 |
| techesperto.com | 7 | 7 |
| croclub.com | 6 | 6 |
| medium.com | 6 | 6 |
| omr.com | 6 | 6 |
| smesoftwarehelp.co.uk | 6 | 6 |
| techrepublic.com | 6 | 6 |
| bitrix24.com | 5 | 5 |
| gitnux.org | 5 | 5 |
| prospeo.io | 5 | 5 |
| solutionsreview.com | 5 | 5 |
| bottlecrm.io | 4 | 4 |
| cloudinfrastructureservices.co.uk | 4 | 4 |
| founding.dev | 4 | 4 |
| getapp.com | 4 | 4 |
| sourceforge.net | 4 | 4 |
| zeeg.me | 4 | 4 |
| opensourceprojects.cc | 3 | 3 |
| railway.com | 3 | 3 |
| selfhosting.sh | 3 | 3 |
| softwaresuggest.com | 3 | 3 |
| webkul.com | 3 | 3 |
A domain missing from this table was cited in fewer than three answers, or was never cited at all — the run A file linked above is the complete list either way, and it is the only way to tell those two apart. Cited is not endorsed: a page the engine retrieved is not a page that recommended anyone, and this counts what was read, not what it said.
The answer a vendor panel shows you is read straight out of the run A file linked above — the page fetches the one line it needs and displays it unaltered, so what you read there and what you get by downloading the file are the same bytes.
What one line of each file holds, and the terms you may re-use them under — the raw answers may be re-used in any medium, commercially and inside open-source software, with attribution.