n8n vs flyto-core

Two of the top projects in Workflow automation with AI, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.

11st of 5 in Workflow automation with AI

n8n

Visual workflow automation with AI agent nodes and 1500+ integrations

#55th of 5 in Workflow automation with AI

flyto-core

Python engine that runs YAML workflows of browser, API and file steps

Verdict

n8n ranks higher, 95 to 55. Of the 4 score parts we measure for both, n8n leads on 3, flyto-core on none and 1 is even.

  • Adoptionn8n leads by 100 points, 100 to 0: a wide gap.
  • FreshnessEven at 100.
  • Maintenancen8n leads by 9 points, 92 to 83.
  • Agent-readyn8n leads by 70 points, 70 to 0: a wide gap.

Pick n8n if you are

Teams wiring LLMs and agents into existing SaaS tools, self-hosted or cloud

  • 1500+ integrations and 9,000+ templates cover most common SaaS wiring
  • Visual canvas with JavaScript, Python and npm code when needed

Pick flyto-core if you are

Engineers scripting repeatable browser, API and file workflows

  • Per-step run records, with checkpoints and replay where safe
  • Usable from Python, YAML, local HTTP API or MCP
n8n vs flyto-core: score parts and facts
What we comparen8nflyto-core
Score parts, out of 100
Adoption100, widely used0, niche
Freshness100, active100, active
Maintenance92, healthy83, healthy
Agent-ready70, partly0, none
Facts from GitHub and the README
Stars211.6k483
Licensecustom license (read the license)Apache-2.0 (permissive)
Last commitNov 2026Nov 2026
Last releaseNov 2026Nov 2026
LanguageTypeScriptPython
DockerYesYes
GPUNot neededNot needed
arm64 or Apple SiliconNot statedNot stated

n8n

n8n is a node-based canvas for building workflows and multi-step AI agents, with JavaScript, Python and npm packages usable inside nodes. It connects to OpenAI, Anthropic, Google and open-source models, and lists 1500+ integrations and 9,000+ workflow templates. It runs self-hosted or on n8n Cloud, under the Sustainable Use License rather than an OSI license.

Who it is for: Teams wiring LLMs and agents into existing SaaS tools, self-hosted or cloud

Strengths

  • 1500+ integrations and 9,000+ templates cover most common SaaS wiring
  • Visual canvas with JavaScript, Python and npm code when needed
  • Model-agnostic: OpenAI, Anthropic, Google or open-source models
  • Supports human approvals and observability for multi-step AI workflows

Weaknesses

  • Fair-code Sustainable Use License, not OSI open source; use is restricted
  • Role-based access and audit trails fall under the Enterprise License
  • Documented quick start requires Docker
  • no GPU
  • Needs Docker
  • Models: OpenAI, Anthropic, Google, open-source models
  • port 5678

flyto-core

flyto-core is the Python execution engine behind Flyto2. It ships 482 registered modules and 41 built-in recipes covering browser automation, APIs, files and data, and can be driven from Python, YAML workflows, a local HTTP API or an MCP server. Each run keeps a per-step record, with checkpoints and replay where safe.

Who it is for: Engineers scripting repeatable browser, API and file workflows

Strengths

  • Per-step run records, with checkpoints and replay where safe
  • Usable from Python, YAML, local HTTP API or MCP
  • 482 modules and 41 built-in recipes ready to run
  • Checks reported tool evidence against the action's contract

Weaknesses

  • ROS 2 robot support still lacks full end-to-end hardware sign-off
  • Physical device actions need a trusted host to approve them
  • Browser recipes need Playwright and a Chromium install
  • README gives no LLM or model integration details
  • no GPU
  • Docker
  • Needs Python, Playwright, Chromium

More in Workflow automation with AI

Building with these?

We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.