EspoCRM vs Krayin
Both are self-hosted customer relationship management (crm) projects. This page compares how well each one is actually maintained — the part you cannot see from a feature list.
| EspoCRM | Krayin | |
|---|---|---|
| Health score | 84/100 | 82/100 |
| Commits (11 mo) | 1524 | 450 |
| Commits (last 3 mo) | 502 | 228 |
| Stars | 3.4k | 24k |
| Latest release | 8 Sept 2026 | 10 Sept 2026 |
| Licence | AGPL-3.0 | MIT |
| Built with | PHP | PHP |
| Typical RAM | 1 GB | 1 GB |
EspoCRM
CRM with a frontend designed as a single page application, and a REST API.
High commit volume, frequent releases and growing activity.
Commit activity more than 86% of tracked projects; popularity more than 60%. How this is calculated.
Commits, last 11 months
Krayin
CRM solution for SMEs and Enterprises for complete customer lifecycle management.
High commit volume, frequent releases and growing activity.
Commit activity more than 61% of tracked projects; popularity more than 90%. How this is calculated.
Commits, last 11 months
How to read this
Everything above is measured, not opinion: commit counts and release dates come from the public repositories, and the health score ranks each project against all 1352 projects we track. Read the full method.
What this comparison deliberately does not do is tell you which has the better feature set. Maintenance health tells you which project will still be receiving security fixes in two years. Decide that first, then compare features on the projects that survive the filter.
See every option in this category: self-hosted customer relationship management (crm).