A
tego
69.5
1,107 stars · Apache-2.0
CRM
Twenty leads by 24.3 · decisive
A
69.5
1,107 stars · Apache-2.0
B · leads
93.8
61,042 stars · AGPL-3.0
tego versus Twenty is a CRM comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 69.5 for tego and 93.8 for Twenty.
Twenty has 61,042 GitHub stars to tego's 1,107, a gap of 59,935 (55.14×). Forks are 116 for tego and 10,113 for Twenty. On the log scale used inside this pair, adoption is 64 versus 100, and the fork community is 52 versus 100.
Push history: tego was last pushed on 24 September 2026 (54 days ago), and Twenty was last pushed on 17 November 2026 (0 days ago). Open issues stand at 19 for tego (0.017 per star) and 146 for Twenty (0.002 per star). Issue-health scores are 84 and 96; activity scores are 58 and 100.
tego is listed as Apache-2.0, 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. 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. License scores in this pair are 96 for tego and 52 for Twenty. This is a procurement signal, not legal advice.
In CRM, both tego (1,107 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: tego is open source, Twenty is freemium.
The lead is split. tego is furthest ahead on license flexibility (96 to 52), while Twenty is furthest ahead on fork community (100 to 52). Choose the dimension a rollout cannot compromise on.
Twenty finishes ahead at 93.8 against tego at 69.5, a 24.3 point decisive 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 | tego | Twenty |
|---|---|---|
| GitHub stars | 1,107 | 61,042 |
| Forks | 116 | 10,113 |
| Open issues | 19 | 146 |
| Adoption | 64 | 100 |
| Activity | 58 | 100 |
| Community | 52 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 69.5 | 93.8 |
Tego is a pluggable Node.js framework for building customizable development platforms. It enables developers to create their own no-code/low-code systems or event-driven applications, while the core focuses on stability and environment adaptability.
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.
Twenty has more GitHub stars: 61,042 versus 1,107 for tego. The gap is 59,935 stars.
Twenty was pushed more recently: 17 November 2026 versus 24 September 2026 for tego. That is 54 days apart.
Yes. This catalog marks both tego and Twenty as self-hostable. Confirm each project's deploy docs before you plan a migration.
tego is listed as Apache-2.0, 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. 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.
Twenty scores 93.8 and tego scores 69.5. This page calls that a decisive lead for Twenty.