Discofork
Repository brief

twentyhq/twenty

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:31:51.443Z
1mo ago

twentyhq/twenty

Twenty is a large, active open-source CRM repository positioned as a modern alternative to Salesforce. It has strong community traction (43,219 stars, 5,708 forks), is not archived, and was updated and pushed on 2026-03-30. The repo is a Node.js/JavaScript monorepo with Nx, Yarn, and a React/TypeScript-heavy frontend stack.

GitHub
Loading tags...
Stars43,219
Forks5,708
Default branchmain
Last pushed2026-03-30T15:30:04Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork only if you value a frozen, older baseline and are willing to own the maintenance burden. If you want the newest CRM features and lower long-term risk, upstream is the better choice.

Choose this fork if you want a more experimental, developer-centric Twenty base with deeper schema and graph-editor customization. Choose upstream instead if you want the broadest feature completeness, smoother upgrades, and lower maintenance risk.

Prefer upstream unless you specifically need this fork's older custom workflow changes. For most adopters, the maintenance burden and missing upstream progress outweigh the added features.

Choose this fork only if its specific custom CRM workflow changes are the goal. For most adopters, upstream Twenty is the safer base because this fork looks stale and materially diverged, so ongoing maintenance and upgrade cost will be high.

Prefer this fork if you need a customized, API- and workflow-tuned Twenty derivative and you can maintain divergence yourself. Prefer upstream if you want the broadest feature set, lower integration risk, and ongoing maintenance.

Choose this fork only if you want its permission and workflow changes enough to accept heavy merge debt and missing upstream progress. For most adopters, upstream Twenty is the safer baseline.

Prefer this fork only if you specifically need its developer-tooling and syncable-entity work. For most adopters seeking a current, low-risk CRM, upstream Twenty is the better default because this fork is stale and materially diverged.

Choose this fork if you want a heavily operationalized Twenty workspace with autonomous upstream-sync and custom development rules. Choose upstream if you want the newest CRM behavior, fewer missing docs/workflows, and lower drift risk.

Choose this fork if you specifically want a mortgage-oriented CRM and are comfortable owning a large upstream divergence. Choose upstream Twenty if you want the broader feature set, faster maintenance, and lower upgrade risk.

Prefer this fork only if you need its custom workflow/auth changes and are prepared to maintain a significantly diverged codebase. If you want current Twenty features, translations, and upstream fixes with lower maintenance risk, upstream is the better default.

twentyhq/twenty · Discofork