Skip to content
DevUtils Online

Workflow Automation

bruno vs edict

bruno leads by 10.9 · clear

A · leads

bruno

96.5

48,427 stars · MIT

B

edict

85.6

17,077 stars · MIT

bruno versus edict is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bruno is written mainly in JavaScript; edict is written mainly in Python. The composite score is 96.5 for bruno and 85.6 for edict.

bruno has 48,427 GitHub stars to edict's 17,077, a gap of 31,350 (2.84×). Forks are 3,115 for bruno and 1,771 for edict. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 93.

Push history: bruno was last pushed on 17 November 2026 (0 days ago), and edict was last pushed on 28 September 2026 (50 days ago). Open issues stand at 2,002 for bruno (0.041 per star) and 15 for edict (0.001 per star). Issue-health scores are 70 and 96; activity scores are 100 and 58.

Both bruno and edict are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Workflow Automation, both bruno (48,427 stars) and edict (17,077 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: bruno is open source, edict is open source.

The lead is split. bruno is furthest ahead on recent activity (100 to 58), while edict is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.

bruno finishes ahead at 96.5 against edict at 85.6, a 10.9 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

bruno versus edict metrics
Signal bruno edict
GitHub stars 48,427 17,077
Forks 3,115 1,771
Open issues 2,002 15
Adoption 100 90
Activity 100 58
Community 100 93
Issue health 70 96
License 96 96
Self-hosting 100 100
Composite 96.5 85.6

edict

🏛️ 三省六部制 · OpenClaw Multi-Agent Orchestration System — 9 specialized AI agents with real-time dashboard, model config, and full audit trails

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, bruno or edict?

bruno has more GitHub stars: 48,427 versus 17,077 for edict. The gap is 31,350 stars.

Which was updated more recently, bruno or edict?

bruno was pushed more recently: 17 November 2026 versus 28 September 2026 for edict. That is 50 days apart.

Can I self-host both bruno and edict?

Yes. This catalog marks both bruno and edict as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, bruno or edict?

bruno 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the bruno vs edict score?

bruno scores 96.5 and edict scores 85.6. This page calls that a clear lead for bruno.

Related comparisons