Learn how Customermates and Erxes 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
15 hours agoRepository age
8 monthsVersion
1.1.0License
AGPL-3.0Self-hosted
YesRepository
customermates
Last 30 days
Last commit
6 hours agoRepository age
10 yearsVersion
3.4.22License
AGPL-3.0Repository
erxes/erxes
Erxes appears to have several advantages over Customermates, particularly in popularity, growth and maturity. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Erxes significantly outpaces Customermates in community adoption with 4,113 stars compared to 222 stars on GitHub. This 18.5x difference suggests Erxes has a much larger and more active community. In terms of developer contributions, Erxes has 1,336 forks, indicating strong developer engagement.
Erxes is growing faster, adding 20 stars in the last 30 days (+0.5%) against losing 7 stars for Customermates (-3.1%). Erxes is both larger and pulling further ahead.
Both projects show recent activity, with Customermates last updated 15 hours ago and Erxes 6 hours ago.
Both tools share common technology foundations, being built with JavaScript, CSS, Bash, Typescript, JSX, Next.js, SCSS. However, they differ in their additional technology choices: Erxes leverages Python, Golang.
Erxes has been in development longer, starting 10 years ago, compared to Customermates which began 8 months ago. This 9.5-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 extends into Customer Communication Platforms, Marketing Automation.
Customermates 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