A
archify
93.6
97,376 stars · Apache-2.0
AI Agents
ECC leads by 5.5 · narrow
A
93.6
97,376 stars · Apache-2.0
B · leads
99.1
305,069 stars · MIT
archify versus ECC is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in JavaScript. The composite score is 93.6 for archify and 99.1 for ECC.
ECC has 305,069 GitHub stars to archify's 97,376, a gap of 207,693 (3.13×). Forks are 6,647 for archify and 44,923 for ECC. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 82 versus 100.
Push history: archify was last pushed on 17 November 2026 (0 days ago), and ECC was last pushed on 17 November 2026 (0 days ago). Open issues stand at 368 for archify (0.004 per star) and 149 for ECC (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
archify 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. ECC is listed as MIT, 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. License scores in this pair are 96 for archify and 96 for ECC. This is a procurement signal, not legal advice.
In AI Agents, both archify (97,376 stars) and ECC (305,069 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: archify is open source, ECC is open source.
ECC is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 18 points (82 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against archify at 93.6, a 5.5 point narrow 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 | archify | ECC |
|---|---|---|
| GitHub stars | 97,376 | 305,069 |
| Forks | 6,647 | 44,923 |
| Open issues | 368 | 149 |
| Adoption | 91 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.6 | 99.1 |
Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
ECC has more GitHub stars: 305,069 versus 97,376 for archify. The gap is 207,693 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both archify and ECC as self-hostable. Confirm each project's deploy docs before you plan a migration.
archify 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. ECC is listed as MIT, 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
ECC scores 99.1 and archify scores 93.6. This page calls that a narrow lead for ECC.