REVIEWS / GENERAL / OWNER INSIGHTS
🦉 WE READ 572 OWNER COMMENTS
Workflo: what owners actually say
Owners appreciate the self-hostable, extensible workflow automation but the Commons Clause license sparks heated debate about whether it's truly open source
What owners complain about
- Licensing ambiguity COMMON
Multiple users point out the Apache 2.0 with Commons Clause license is NOT OSI-approved open source, despite the project being marketed as 'Open Source'. The Commons Clause applies a commercial restriction that disqualifies it from being true open source.
- Contributor reluctance SOME
Users express reluctance to contribute free code when the project maintainer retains exclusive commercial rights. One commenter notes: 'I do not want to contribute code to a project for free when somebody else can make money with it... It's that you, the project maintainer, will be reaping all the monetary benefits for yourself.'
- Non-programmer interfaces remain unproven FEW
One experienced commenter is skeptical of supposedly non-programmer-friendly visual workflow tools, saying they are 'guilty until proven innocent' and requesting that authors provide more clarity about what's actually happening behind the scenes.
- Security trust concerns SOME
Users worry about prompt injection and other security risks when installing such tools, asking how they can verify safety. One user notes they 'would not trust Grok to tell me something is safe' and questions whether automation is being over-delegated.
- Consulting revenue cap confusion FEW
The $30,000 (written as 30.000) annual consulting allowance without permission sparked confusion and debate about how practical or generous that limit actually is.
What owners love
- Self-hosting for regulated industries
Users value that it can be self-hosted, noting that keeping data within your own network removes significant compliance legwork for PCI/SOC/HIPPA requirements in highly regulated organisations.
- Trustworthy alternative to closed platforms
Multiple users express they would never trust a closed platform like Zapier or IFTTT for workflow automation but would consider using n8n because it can be self-hosted and is extensible.
- Simplicity vs. Node-RED
Users appreciate that it targets a different, more accessible market than Node-RED by offering a catalog model where you don't need to know what's going on behind the scenes, sacrificing low-level control for simplicity.
- Extensibility for internal tools
Owners praise the ability to easily extend the tool and use it with internal tools, making it practical for custom enterprise use cases.
Surprising patterns
- The licensing debate completely dominated the launch discussion, with users spending more time arguing about Commons Clause semantics and the ethics of monetisation than discussing the actual product features or capabilities.
- The tool is frequently compared to Node-RED, but users note Node-RED explicitly discourages writing high-level nodes in favour of lower-level ones — positioning n8n as the simpler, higher-level alternative rather than a direct competitor.
- Users who defend the license point out a fundamental gap: they argue current OSI licenses don't adequately serve a class of applications where the creator needs sustainable revenue, suggesting n8n's model could motivate similar projects.
WHO SHOULD SKIP IT
Buyers who need a genuinely OSI-certified open source tool — or who want to freely commercialise, redistribute, or contribute to a project without restrictions — should look elsewhere, as the Commons Clause explicitly limits commercial use.
Synthesised from 572 real owner comments across 5 platforms. Every point is grounded in the comments — no marketing, no AI guessing. How we do it →