A
Flowise
79.0
55,573 stars · Apache-2.0
AI Agents
Front-End-Checklist leads by 13.5 · clear
A
79.0
55,573 stars · Apache-2.0
B · leads
92.5
74,760 stars · MIT
Flowise versus Front-End-Checklist is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Flowise is written mainly in TypeScript; Front-End-Checklist is written mainly in MDX. The composite score is 79.0 for Flowise and 92.5 for Front-End-Checklist.
Front-End-Checklist has 74,760 GitHub stars to Flowise's 55,573, a gap of 19,187 (1.35×). Forks are 25,096 for Flowise and 6,781 for Front-End-Checklist. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 100 versus 87.
Push history: Flowise was last pushed on 13 August 2026 (96 days ago), and Front-End-Checklist was last pushed on 31 October 2026 (17 days ago). Open issues stand at 1,033 for Flowise (0.019 per star) and 22 for Front-End-Checklist (0.000 per star). Issue-health scores are 84 and 96; activity scores are 18 and 78. Flowise is archived on GitHub, so its activity score is capped.
Flowise 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. Front-End-Checklist 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. License scores in this pair are 96 for Flowise and 96 for Front-End-Checklist. This is a procurement signal, not legal advice.
In AI Agents, both Flowise (55,573 stars) and Front-End-Checklist (74,760 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: Flowise is open source, Front-End-Checklist is open source.
The lead is split. Flowise is furthest ahead on fork community (100 to 87), while Front-End-Checklist is furthest ahead on recent activity (78 to 18). Choose the dimension a rollout cannot compromise on.
Front-End-Checklist finishes ahead at 92.5 against Flowise at 79.0, a 13.5 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 | Flowise | Front-End-Checklist |
|---|---|---|
| GitHub stars | 55,573 | 74,760 |
| Forks | 25,096 | 6,781 |
| Open issues | 1,033 | 22 |
| Adoption | 97 | 100 |
| Activity | 18 | 78 |
| Community | 100 | 87 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 79.0 | 92.5 |
Flowise is a visual builder for LLM chains and agents on top of libraries such as LangChain. You design a flow in the browser and run it from a self-hosted Node service.
🗂 The essential checklist for modern web development, for humans and AI agents
Front-End-Checklist has more GitHub stars: 74,760 versus 55,573 for Flowise. The gap is 19,187 stars.
Front-End-Checklist was pushed more recently: 31 October 2026 versus 13 August 2026 for Flowise. That is 79 days apart.
Yes. This catalog marks both Flowise and Front-End-Checklist as self-hostable. Confirm each project's deploy docs before you plan a migration.
Flowise 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. Front-End-Checklist 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.
Front-End-Checklist scores 92.5 and Flowise scores 79.0. This page calls that a clear lead for Front-End-Checklist.