head to head · open source

edict vs invobook

edict has 17,040 GitHub stars, 1,767 forks, 18 open issues and last shipped 1 months ago. invobook has 2,235 stars, 607 forks, 9 open issues and last shipped 3 days ago. edict leads on adoption by 662% (17,040 vs 2,235 stars). edict is written in Python under MIT; invobook is written in Blade under MIT. edict has attracted 10% as many forks as stars, invobook 27%. invobook 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.

edict ★ 17K invobook ★ 2.2K category Business Software

← all 20902 open source comparisons

Side by side

edict invobook
GitHub stars ★ 17K ★ 2.2K
License MIT MIT
Written in Python Blade
Last push 2026-09-28 2026-10-31
Forks ⑂ 1.8K ⑂ 607
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

full edict profile →

pick invobook if

  • You want the invobook feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches Blade
  • You evaluated both and invobook fits your workflow better

full invobook profile →

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 invobook

InvoBook Self hosted app for Time Tracking, Invoice Generation, Project & Client Management, built with Laravel & Filament. Hire me I'm available for contractual work on this stack (Filament, Laravel, Livewire, AlpineJS, TailwindCSS). Reach me via email or discord About Invobook Invobook is a self hosted app to manage team/clients, project & tasks, time tracking, create and sending invoice and more. It is build upon Filament and TALL stack. Installation Screenshots Contributing Supporting Credits License Installation Clone the repository Set env variables Install composer packages Screenshots ↑Top Contributing…

read the full invobook 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 invobook more popular?

edict has 17,040 GitHub stars and invobook has 2,235. edict has the larger community by that measure.

Are edict and invobook free?

Both are open source. edict is licensed under MIT and invobook under MIT. Neither carries a licence fee.

What is the difference between edict and invobook?

edict is written in Python and invobook in Blade. 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 invobook?

Choose edict if you want the larger community (17,040 stars) or its MIT licence terms. Choose invobook if its feature set, stack or MIT licence fits better. Both are self-hostable.