head to head · open source
edict vs gronx
edict has 17,046 GitHub stars, 1,768 forks, 18 open issues and last shipped 1 months ago. gronx has 515 stars, 38 forks, 8 open issues and last shipped 1 months ago. edict leads on adoption by 3,210% (17,046 vs 515 stars). edict is written in Python under MIT; gronx is written in Go under MIT. edict has attracted 10% as many forks as stars, gronx 7%. edict was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| edict | gronx | |
|---|---|---|
| GitHub stars | ★ 17K | ★ 515 |
| License | MIT | MIT |
| Written in | Python | Go |
| Last push | 2026-09-28 | 2026-09-27 |
| Forks | ⑂ 1.8K | ⑂ 38 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick edict if
- You weight community size — 17K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick gronx if
- You want the gronx feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Go
- You evaluated both and gronx fits your workflow better
About edict
⚔️ 三省六部 · Edict 我用 1300 年前的帝国制度，重新设计了 AI 多 Agent 协作架构。 结果发现，古人比现代 AI 框架更懂分权制衡。 12 个 AI Agent（11 个业务角色 + 1 个兼容角色）组成三省六部：太子分拣、中书省规划、门下省审核封驳、尚书省派发、六部+吏部并行执行。 比 CrewAI 多一层 制度性审核 ，比 AutoGen 多一个 实时看板 。 🎬 看 Demo · 🚀 30 秒体验 · 🏛️ 架构 · 📋 看板功能 · 📚 架构文档 · English · 日本語 · 参与贡献 🎬 Demo 您的浏览器不支持视频播放，请查看下方 GIF 或 下载视频 。 🎥 三省六部 AI 多 Agent 协作全流程演示 📸 GIF 预览（加载更快） 飞书下旨 → 太子分拣 → 中书省规划 → 门下省审议 → 六部并行执行 → 奏折回报（30 秒） 🐳 没有 OpenClaw？ 跑一行 docker run p 7891:7891 cft0808/edict 即可体验完整看板 Demo（预置模拟数据）。 🤔 为什么是三省六部？ 大多数 Multi Agent 框架的套路是： "来，你们几个 AI 自己聊，聊完把结果给我。" 然后你拿到一坨不知道经过了什么处理的结果，无法复现，无法审计，无法干预。 三省六部的思路完全不同 —— 我们用了一个在中国存在 1400…
read the full edict overview →
About gronx
adhocore/gronx gronx is Golang cron expression parser ported from adhocore/cron expr with task runner and daemon that supports crontab like task list file. Use it programatically in Golang or as standalone binary instead of crond. If that's not enough, you can use gronx to find the next ( NextTick() ) or previous ( PrevTick() ) run time of an expression from any arbitrary point of time. Zero dependency. Very fast because it bails early in case a segment doesn't match. Built in crontab like daemon. Supports time granularity of Seconds. Find gronx in pkg.go.dev. Installation As a Go library Using Bash install…
read the full gronx overview →
More in Business Software
Related comparisons
More Project & Work Management projects
Compare either of these against the rest of the Project & Work Management field.
Frequently asked questions
Is edict or gronx more popular?
edict has 17,046 GitHub stars and gronx has 515. edict has the larger community by that measure.
Are edict and gronx free?
Both are open source. edict is licensed under MIT and gronx under MIT. Neither carries a licence fee.
What is the difference between edict and gronx?
edict is written in Python and gronx in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, edict or gronx?
Choose edict if you want the larger community (17,046 stars) or its MIT licence terms. Choose gronx if its feature set, stack or MIT licence fits better. Both are self-hostable.