A · leads
edict
89.9
17,077 stars · MIT
Workflow Automation
edict leads by 4.7 · narrow
A · leads
89.9
17,077 stars · MIT
B
85.2
11,787 stars · license n/a
edict versus ekko-studio is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. edict is written mainly in Python; ekko-studio is written mainly in TypeScript. The composite score is 89.9 for edict and 85.2 for ekko-studio.
edict has 17,077 GitHub stars to ekko-studio's 11,787, a gap of 5,290 (1.45×). Forks are 1,771 for edict and 1,476 for ekko-studio. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 98.
Push history: edict was last pushed on 28 September 2026 (50 days ago), and ekko-studio was last pushed on 17 November 2026 (0 days ago). Open issues stand at 15 for edict (0.001 per star) and 592 for ekko-studio (0.050 per star). Issue-health scores are 96 and 52; activity scores are 58 and 100.
edict 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. ekko-studio is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for edict and 30 for ekko-studio. This is a procurement signal, not legal advice.
In Workflow Automation, both edict (17,077 stars) and ekko-studio (11,787 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: edict is open source, ekko-studio is unpriced in this catalog.
The lead is split. edict is furthest ahead on license flexibility (96 to 30), while ekko-studio is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.
edict finishes ahead at 89.9 against ekko-studio at 85.2, a 4.7 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 | edict | ekko-studio |
|---|---|---|
| GitHub stars | 17,077 | 11,787 |
| Forks | 1,771 | 1,476 |
| Open issues | 15 | 592 |
| Adoption | 100 | 96 |
| Activity | 58 | 100 |
| Community | 100 | 98 |
| Issue health | 96 | 52 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 89.9 | 85.2 |
🏛️ 三省六部制 · OpenClaw Multi-Agent Orchestration System — 9 specialized AI agents with real-time dashboard, model config, and full audit trails
Ekko Studio is a local-first AI workspace for multi-agent chat, coding, and visual workflows, available on desktop and the web.
edict has more GitHub stars: 17,077 versus 11,787 for ekko-studio. The gap is 5,290 stars.
ekko-studio was pushed more recently: 17 November 2026 versus 28 September 2026 for edict. That is 50 days apart.
Yes. This catalog marks both edict and ekko-studio as self-hostable. Confirm each project's deploy docs before you plan a migration.
edict 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. ekko-studio is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
edict scores 89.9 and ekko-studio scores 85.2. This page calls that a narrow lead for edict.