Discofork
Repository brief

n8n-io/n8n

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-29T22:05:42.219Z
3mo ago

n8n-io/n8n

n8n is a large, actively maintained workflow automation platform with native AI features, 400+ integrations, and both self-hosted and cloud deployment options. It is source-available under fair-code licenses rather than a standard permissive OSS license. The repo is very active, with recent commits on March 27-29, 2026, and a large community footprint (181,619 stars, 56,283 forks).

GitHub
Loading tags...
Stars181,619
Forks56,283
Default branchmaster
Last pushed2026-03-29T15:11:10Z
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

6 of 6 fork briefs
Selected

Choose this fork if you value Chinese localization and custom assistant-oriented workflows more than strict upstream parity. Avoid it if you need the safest path to upstream compatibility, because the fork is materially diverged and still trailing upstream changes.

Choose this fork if your priority is editor-native workflow collection management inside VSCode/Cursor/Antigravity. Choose upstream if you want the broadest current n8n feature set, fastest access to new fixes, and lower long-term maintenance risk.

Prefer this fork if you want an AI-centered n8n experience with agent interactions, approvals, and guided setup. Prefer upstream if you want the latest n8n features, lower maintenance risk, and the broadest compatibility.

Prefer this fork only if you need its added platform behavior and are willing to own long-term merge maintenance. If you want the broadest feature coverage, fastest fixes, and lowest upgrade risk, upstream n8n is the safer choice.

Prefer this fork if your goal is an AI-copilot-centric n8n distribution with repo automation and custom agent tooling. Prefer upstream n8n if you want the latest platform features, lower merge risk, and a more standard deployment path.

Choose this fork if browser automation and HTML parsing are the main goal and you value a preconfigured demo-oriented build. Choose upstream if you need the latest n8n capabilities, active maintenance, and lower upgrade risk.

n8n-io/n8n · Discofork