A · leads
aureuserp
97.4
12,251 stars · MIT
CRM
aureuserp leads by 10.5 · clear
A · leads
97.4
12,251 stars · MIT
B
86.9
6,359 stars · AGPL-3.0
aureuserp versus macro is a CRM comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. aureuserp is written mainly in PHP; macro is written mainly in Rust. The composite score is 97.4 for aureuserp and 86.9 for macro.
aureuserp has 12,251 GitHub stars to macro's 6,359, a gap of 5,892 (1.93×). Forks are 629 for aureuserp and 598 for macro. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 99.
Push history: aureuserp was last pushed on 06 November 2026 (11 days ago), and macro was last pushed on 17 November 2026 (0 days ago). Open issues stand at 45 for aureuserp (0.004 per star) and 522 for macro (0.082 per star). Issue-health scores are 96 and 52; activity scores are 92 and 100.
aureuserp is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. 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 96 for aureuserp and 52 for macro. This is a procurement signal, not legal advice.
In CRM, both aureuserp (12,251 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: aureuserp is open source, macro is open source.
The lead is split. aureuserp is furthest ahead on issue health (96 to 52), while macro is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
aureuserp finishes ahead at 97.4 against macro at 86.9, a 10.5 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 | aureuserp | macro |
|---|---|---|
| GitHub stars | 12,251 | 6,359 |
| Forks | 629 | 598 |
| Open issues | 45 | 522 |
| Adoption | 100 | 93 |
| Activity | 92 | 100 |
| Community | 100 | 99 |
| Issue health | 96 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 86.9 |
Free and Open Source ERP software
Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
aureuserp has more GitHub stars: 12,251 versus 6,359 for macro. The gap is 5,892 stars.
macro was pushed more recently: 17 November 2026 versus 06 November 2026 for aureuserp. That is 11 days apart.
Yes. This catalog marks both aureuserp and macro as self-hostable. Confirm each project's deploy docs before you plan a migration.
aureuserp is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. 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.
aureuserp scores 97.4 and macro scores 86.9. This page calls that a clear lead for aureuserp.