n8n released 3.0 in beta on October 27, with stable planned for early December. It is a reliability and security release, and it removes a lot of old behavior.
According to n8n's announcement and its breaking-changes documentation, version 3.0.0 is available as an early access beta. n8n says the stable release follows in early December. On n8n Cloud you can pick "3.0.0 Beta (early access)" when changing your n8n version. n8n states the changes apply to self-hosted Community, Cloud, and Enterprise/Business editions. Neither page we reviewed mentions any change to pricing or licensing.
n8n 3.0 no longer supports installs run with npm or npx and does not publish a runnable n8n package to npm. Existing Docker Compose setups need no change, and n8n says Kubernetes and Helm are not affected. If you currently run n8n with npx on a spare server, you will need to move to Docker before you can adopt 3.0.
The documentation lists a long set of removed nodes, including Function, Function Item, Item Lists, Cron, Interval, the legacy OpenAI nodes and AI Agent v1. Workflows that use them will fail, and published ones stop activating. Replacements exist for many (for example, Function becomes the Code node, and Cron and Interval become Schedule Trigger), but n8n notes some have none, such as SerpApi. Check the official list against your own workflows rather than relying on our summary.
n8n recommends updating to the latest 2.x release first. Every instance on 2.39 or later has a Migration Report under Settings, which lists affected workflows and settings, auto-fixes many issues as new workflow versions for you to review, and can export a CSV. The suggested sequence is: fix or mark "won't fix" everything flagged, take a full backup, upgrade a staging instance, then production. n8n is explicit that moving to 3.x is one way with no rollback, so the backup is not optional.
Timing also matters. n8n says there is no direct path from 1.x to 3.x, and that support for 1.x ends December 31, 2026. After stable, it says 2.x will get security and critical bug fixes for 12 months. If you are still on 1.x, plan a move to 2.x first.
| Option | Who handles upgrades | Practical implication |
|---|---|---|
| n8n self-hosted | You | You own the Docker move, migration testing and backups |
| n8n Cloud | You choose the version; n8n runs the servers | No server work, but you still need to check workflows for removed nodes |
| Zapier / Make | The vendor | Fewer infrastructure decisions, with their own pricing and deprecation changes |
None of this makes n8n a bad choice. Tighter security defaults are arguably what you want after October's batch of advisories (see our n8n security update explainer). It does show that "free" self-hosting carries a recurring maintenance cost in time. For managed-tool pricing and feature differences, see our Make vs Zapier breakdown.
If you run n8n for a small team, do not rush onto the beta. Use the next few weeks to get onto the latest 2.x, run the Migration Report, and list which workflows depend on removed nodes. If nobody on your team wants to own that work, a hosted n8n plan or a managed platform is the lower-effort route.
Note that StackPilot's comparisons are based on research of public information and vendor documentation, not hands-on testing. Details can change before the stable release; confirm in n8n's official documentation.