Discofork
Repository brief

FlowiseAI/Flowise

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:47:18.079Z
1mo ago

FlowiseAI/Flowise

FlowiseAI/Flowise is a large, active open source platform for building AI agents visually. It has strong adoption signals (51,255 stars, 24,001 forks) and very recent maintenance, with commits on 2026-03-30 and 2026-03-27. The repo is set up for self-hosting and local development, with Docker support and a monorepo structure centered on Node.js/JavaScript.

GitHub
Loading tags...
Stars51,255
Forks24,001
Default branchmain
Last pushed2026-03-30T13:00:47Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork only if you specifically want a near-stock Flowise base for your own customization. If you want the latest fixes and features, upstream is the better choice.

Choose this fork if you want a customized Flowise-based product with added workflows and operational scaffolding. Choose upstream if you want the newest security fixes and lowest-maintenance path, because this fork is materially behind mainline.

Choose this fork only if its chatbot-specific customizations and bundled workflows are the main product value. If you need an actively maintained Flowise base, upstream is the safer default because this fork is stale and significantly behind.

Choose this fork only if you want an essentially stock Flowise snapshot and are comfortable absorbing upstream lag yourself; otherwise the upstream repo is the better default.

Adopt this only if you specifically want an older, near-vanilla Flowise snapshot. For most users, upstream is the better choice because this fork adds no concrete capabilities and is materially behind recent fixes.

Choose this fork only if its specific customizations match your target workflow and you are comfortable owning a stale, highly divergent codebase. If you want current Flowise capabilities, active maintenance, or security updates, upstream is the safer choice.

Choose this fork if you need the added MCP/agentflow customization and can absorb maintenance burden. Choose upstream if you want the newest fixes, broader feature parity, and lower operational risk.

Choose this fork only if its custom agentflow/templates are the main value and you can own long-term maintenance. For most adopters, upstream Flowise is the safer default because it is much more current and actively patched.

Choose this fork only if its extra Agentflow/integration work matches your needs. Otherwise, upstream is the safer default because it is much newer and has recent security and stability fixes the fork appears to miss.

Choose this fork if you need the Zylon-specific workflow additions and can tolerate substantial drift from upstream. Choose upstream if you want the newest security fixes, lower maintenance burden, and the broader Flowise release stream.