A
Erxes
87.6
4,112 stars · AGPL-3.0
CRM
EspoCRM leads by 4.1 · narrow
A
87.6
4,112 stars · AGPL-3.0
B · leads
91.7
3,630 stars · AGPL-3.0
Erxes versus EspoCRM is a CRM comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Erxes is written mainly in TypeScript; EspoCRM is written mainly in PHP. The composite score is 87.6 for Erxes and 91.7 for EspoCRM.
Erxes has 4,112 GitHub stars to EspoCRM's 3,630, a gap of 482 (1.13×). Forks are 1,337 for Erxes and 1,048 for EspoCRM. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 97.
Push history: Erxes was last pushed on 17 November 2026 (0 days ago), and EspoCRM was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,033 for Erxes (0.251 per star) and 67 for EspoCRM (0.018 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
Both Erxes and EspoCRM are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In CRM, both Erxes (4,112 stars) and EspoCRM (3,630 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: Erxes is open source, EspoCRM is open source.
The lead is split. Erxes is furthest ahead on fork community (100 to 97), while EspoCRM is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
EspoCRM finishes ahead at 91.7 against Erxes at 87.6, a 4.1 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Erxes | EspoCRM |
|---|---|---|
| GitHub stars | 4,112 | 3,630 |
| Forks | 1,337 | 1,048 |
| Open issues | 1,033 | 67 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 97 |
| Issue health | 34 | 84 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 87.6 | 91.7 |
Erxes is a marketing and customer-conversation platform that combines CRM records with inbox and campaign tools. It is designed for teams that want those functions on infrastructure they run.
EspoCRM is a web CRM with roles, streams, and a modular entity model. It is aimed at small and mid-size teams that want a classic self-hosted sales system.
Erxes has more GitHub stars: 4,112 versus 3,630 for EspoCRM. The gap is 482 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Erxes and EspoCRM as self-hostable. Confirm each project's deploy docs before you plan a migration.
Erxes is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. EspoCRM is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
EspoCRM scores 91.7 and Erxes scores 87.6. This page calls that a narrow lead for EspoCRM.