Skip to content
DevUtils Online

CRM

macro vs Twenty

Twenty leads by 15.6 · decisive

A

macro

78.2

6,359 stars · AGPL-3.0

B · leads

Twenty

93.8

61,042 stars · AGPL-3.0

macro versus Twenty 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; Twenty is written mainly in TypeScript. The composite score is 78.2 for macro and 93.8 for Twenty.

Twenty has 61,042 GitHub stars to macro's 6,359, a gap of 54,683 (9.60×). Forks are 598 for macro and 10,113 for Twenty. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 69 versus 100.

Push history: macro was last pushed on 17 November 2026 (0 days ago), and Twenty was last pushed on 17 November 2026 (0 days ago). Open issues stand at 522 for macro (0.082 per star) and 146 for Twenty (0.002 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.

Both macro and Twenty 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 macro (6,359 stars) and Twenty (61,042 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, Twenty is freemium.

Twenty is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).

Twenty finishes ahead at 93.8 against macro at 78.2, a 15.6 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

macro versus Twenty metrics
Signal macro Twenty
GitHub stars 6,359 61,042
Forks 598 10,113
Open issues 522 146
Adoption 80 100
Activity 100 100
Community 69 100
Issue health 52 96
License 52 52
Self-hosting 100 100
Composite 78.2 93.8

macro

Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.

Project site · GitHub · Full profile

Twenty

Twenty is an open CRM aimed at teams that want a modern interface without adopting a closed SaaS contact database. It covers people, companies, and opportunities and is built to be self-hosted.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, macro or Twenty?

Twenty has more GitHub stars: 61,042 versus 6,359 for macro. The gap is 54,683 stars.

Which was updated more recently, macro or Twenty?

Both were last pushed on 17 November 2026.

Can I self-host both macro and Twenty?

Yes. This catalog marks both macro and Twenty as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, macro or Twenty?

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. Twenty 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.

Who wins the macro vs Twenty score?

Twenty scores 93.8 and macro scores 78.2. This page calls that a decisive lead for Twenty.

Related comparisons