Learn how Erxes and Twenty differ in their key features, development activity, technology stack and community adoption, so you can decide which of these crm systems is best for you.
Last 30 days
Last commit
1 hour agoRepository age
10 yearsVersion
3.4.25License
AGPL-3.0Repository
erxes/erxes
Last 30 days
Last commit
40 minutes agoRepository age
4 yearsVersion
v2.59.0License
AGPL-3.0Self-hosted
YesRepository
twentyhq/twenty
Twenty appears to have several advantages over Erxes, particularly in popularity, growth and features. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Twenty significantly outpaces Erxes in community adoption with 61,234 stars compared to 4,112 stars on GitHub. This 14.9x difference suggests Twenty has a much larger and more active community. In terms of developer contributions, Twenty has 10,155 forks, indicating strong developer engagement.
Twenty is growing faster, adding 2,196 stars in the last 30 days (+3.7%) against adding 21 stars for Erxes (+0.5%). Twenty is both larger and pulling further ahead.
Both projects show recent activity, with Erxes last updated 1 hour ago and Twenty 40 minutes ago.
Both tools share common technology foundations, being built with JavaScript, CSS, Bash, Typescript, JSX, Next.js. However, they differ in their additional technology choices: Erxes uses Python, Golang, SCSS while Twenty leverages NestJS.
Erxes has been in development longer, starting 10 years ago, compared to Twenty which began 4 years ago. This 6.1-year head start suggests Erxes may have more mature features and established processes.
Both projects use the AGPL-3.0 license, providing identical terms for usage and distribution.
Both tools serve similar use cases in CRM Systems. However, they also have distinct specializations: Erxes also focuses on Customer Communication Platforms, Marketing Automation.
Twenty provides self-hosting options for complete data control and customization, while Erxes may be primarily cloud-based or require different deployment approaches.
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs