A · leads
erpnext
90.9
41,374 stars · GPL-3.0
CRM
erpnext leads by 12.0 · clear
A · leads
90.9
41,374 stars · GPL-3.0
B
78.9
6,359 stars · AGPL-3.0
erpnext versus macro is a CRM comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. erpnext is written mainly in Python; macro is written mainly in Rust. The composite score is 90.9 for erpnext and 78.9 for macro.
erpnext has 41,374 GitHub stars to macro's 6,359, a gap of 35,015 (6.51×). Forks are 13,544 for erpnext and 598 for macro. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 67.
Push history: erpnext was last pushed on 17 November 2026 (0 days ago), and macro was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,265 for erpnext (0.055 per star) and 522 for macro (0.082 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
erpnext is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. macro 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. License scores in this pair are 64 for erpnext and 52 for macro. This is a procurement signal, not legal advice.
In CRM, both erpnext (41,374 stars) and macro (6,359 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: erpnext is open source, macro is open source.
erpnext is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is fork community at 33 points (100 vs 67), and the tightest is self-hosting at 0 points (100 vs 100).
erpnext finishes ahead at 90.9 against macro at 78.9, a 12.0 point clear 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 | erpnext | macro |
|---|---|---|
| GitHub stars | 41,374 | 6,359 |
| Forks | 13,544 | 598 |
| Open issues | 2,265 | 522 |
| Adoption | 100 | 82 |
| Activity | 100 | 100 |
| Community | 100 | 67 |
| Issue health | 52 | 52 |
| License | 64 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 90.9 | 78.9 |
Free and Open Source Enterprise Resource Planning (ERP)
Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
erpnext has more GitHub stars: 41,374 versus 6,359 for macro. The gap is 35,015 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both erpnext and macro as self-hostable. Confirm each project's deploy docs before you plan a migration.
erpnext is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. macro 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.
erpnext scores 90.9 and macro scores 78.9. This page calls that a clear lead for erpnext.