A
macro
82.1
6,359 stars · AGPL-3.0
CRM
platform leads by 10.5 · clear
A
82.1
6,359 stars · AGPL-3.0
B · leads
92.6
28,135 stars · EPL-2.0
macro versus platform is a CRM comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. macro is written mainly in Rust; platform is written mainly in TypeScript. The composite score is 82.1 for macro and 92.6 for platform.
platform has 28,135 GitHub stars to macro's 6,359, a gap of 21,776 (4.42×). Forks are 598 for macro and 2,194 for platform. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 83 versus 100.
Push history: macro was last pushed on 17 November 2026 (0 days ago), and platform was last pushed on 09 November 2026 (8 days ago). Open issues stand at 522 for macro (0.082 per star) and 698 for platform (0.025 per star). Issue-health scores are 52 and 70; activity scores are 100 and 92.
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. platform is listed as EPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 52 for macro and 78 for platform. This is a procurement signal, not legal advice.
In CRM, both macro (6,359 stars) and platform (28,135 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: macro is open source, platform is open source.
The lead is split. macro is furthest ahead on recent activity (100 to 92), while platform is furthest ahead on license flexibility (78 to 52). Choose the dimension a rollout cannot compromise on.
platform finishes ahead at 92.6 against macro at 82.1, 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 | macro | platform |
|---|---|---|
| GitHub stars | 6,359 | 28,135 |
| Forks | 598 | 2,194 |
| Open issues | 522 | 698 |
| Adoption | 86 | 100 |
| Activity | 100 | 92 |
| Community | 83 | 100 |
| Issue health | 52 | 70 |
| License | 52 | 78 |
| Self-hosting | 100 | 100 |
| Composite | 82.1 | 92.6 |
Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
Huly — All-in-One Project Management Platform (alternative to Linear, Jira, Slack, Notion, Motion)
platform has more GitHub stars: 28,135 versus 6,359 for macro. The gap is 21,776 stars.
macro was pushed more recently: 17 November 2026 versus 09 November 2026 for platform. That is 8 days apart.
Yes. This catalog marks both macro and platform as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. platform is listed as EPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
platform scores 92.6 and macro scores 82.1. This page calls that a clear lead for platform.