A
rulego
81.3
1,635 stars · Apache-2.0
Workflow Automation
ToolJet leads by 9.9 · clear
A
81.3
1,635 stars · Apache-2.0
B · leads
91.2
41,239 stars · AGPL-3.0
rulego versus ToolJet is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. rulego is written mainly in Go; ToolJet is written mainly in HTML. The composite score is 81.3 for rulego and 91.2 for ToolJet.
ToolJet has 41,239 GitHub stars to rulego's 1,635, a gap of 39,604 (25.22×). Forks are 164 for rulego and 5,511 for ToolJet. On the log scale used inside this pair, adoption is 70 versus 100, and the fork community is 59 versus 100.
Push history: rulego was last pushed on 13 November 2026 (4 days ago), and ToolJet was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4 for rulego (0.002 per star) and 952 for ToolJet (0.023 per star). Issue-health scores are 96 and 70; activity scores are 92 and 100.
rulego 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. ToolJet is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for rulego and 52 for ToolJet. This is a procurement signal, not legal advice.
In Workflow Automation, both rulego (1,635 stars) and ToolJet (41,239 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: rulego is open source, ToolJet is open source.
The lead is split. rulego is furthest ahead on license flexibility (96 to 52), while ToolJet is furthest ahead on fork community (100 to 59). Choose the dimension a rollout cannot compromise on.
ToolJet finishes ahead at 91.2 against rulego at 81.3, a 9.9 point clear 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 | rulego | ToolJet |
|---|---|---|
| GitHub stars | 1,635 | 41,239 |
| Forks | 164 | 5,511 |
| Open issues | 4 | 952 |
| Adoption | 70 | 100 |
| Activity | 92 | 100 |
| Community | 59 | 100 |
| Issue health | 96 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 81.3 | 91.2 |
⛓️RuleGo is a lightweight, high-performance, embedded, next-generation component orchestration rule engine framework for Go.
Open-source foundation of ToolJet AI - the enterprise app generation platform for internal tools, dashboards, business applications, workflows and AI agents. Build visually, from a prompt, or from Claude Code, Codex and Cursor over MCP 🚀
ToolJet has more GitHub stars: 41,239 versus 1,635 for rulego. The gap is 39,604 stars.
ToolJet was pushed more recently: 17 November 2026 versus 13 November 2026 for rulego. That is 4 days apart.
Yes. This catalog marks both rulego and ToolJet as self-hostable. Confirm each project's deploy docs before you plan a migration.
rulego 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. ToolJet is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
ToolJet scores 91.2 and rulego scores 81.3. This page calls that a clear lead for ToolJet.