ferry vs n8n
Jira-driven development automation compared with visual workflows
ferry turns Jira ticket transitions into agent-driven development workflows, primarily through GitHub Actions. n8n connects services in visual workflows and supports custom code and AI processes; it is a broader automation platform with self-hosted and cloud options.
ferry: Turn Jira Ticket Moves Into Draft Pull Requests
Ferry uses Jira ticket transitions to start an agent pipeline in GitHub Actions, from refinement through review and merging. It suits teams seeking an automated development workflow, but requires Jira Cloud, GitHub Actions setup, and an LLM provider.
n8n: Build Visual Workflows and AI Agents
n8n connects apps and services in visual workflows, with custom code available for more complex automation. It suits teams that want to build AI-enabled processes and choose between self-hosting and cloud deployment.
| ferry | n8n | |
|---|---|---|
| Language | TypeScript | TypeScript |
| License | MIT | NOASSERTION |
| Stars | 3 | 207k |
| Forks | 1 | 61k |
| Last analyzed | Oct 4, 2026 | Oct 3, 2026 |
Key differences
- ferry focuses on Jira-triggered repository work that can proceed through refinement, development, review, and merging; n8n supports workflows connecting services across varied business processes.
- ferry's primary execution path is GitHub Actions and it requires Jira Cloud; n8n offers self-hosted and cloud deployment options.
- ferry documents a TypeScript CLI and local runner with per-ticket worktrees; n8n offers a visual editor, custom JavaScript and Python, and extensible nodes.
- ferry is licensed under MIT; n8n reports NOASSERTION for its repository license, and its README describes fair-code terms under the Sustainable Use License.
- ferry has 3 stars and 1 fork, while n8n has 207k stars and 61k forks.
Choose ferry if you…
- need Jira ticket transitions to initiate repository work through GitHub Actions.
- want agent phases for refining, developing, reviewing, and merging changes.
- prefer a local runner with isolated per-ticket worktrees as an option.
Choose n8n if you…
- want to connect services in visual, multi-step workflows.
- need custom JavaScript or Python logic alongside workflow design.
- want to choose between self-hosting and cloud deployment for automation or AI processes.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.