docs: fix and annotate research links after link check
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
15740a054f
commit
071910f5f5
@@ -160,7 +160,7 @@ The main criticisms: the enterprise features most teams need (SSO from $200/mo,
|
||||
- Reviews disagree on what is paywalled (SSO/SAML, audit logs, branding, RBAC, white-label). One notes that having the source does not grant rights to the commercial modules. — [ohaiknow](https://ohaiknow.com/reviews/activepieces/), [opsily (managed-n8n vendor, biased)](https://opsily.com/hosting/n8n/activepieces-self-hosted-limitations), [baeseokjae](https://baeseokjae.github.io/posts/activepieces-review-2026/)
|
||||
- Single-source claims: no sub-flow architecture, more manual error handling, a loop step failing silently on empty arrays, no native flow version control. — [syncgtm](https://syncgtm.com/blog/activepieces-review). The sub-flow claim conflicts with the product's documented Subflows piece; the versioning claim is unverified.
|
||||
- Smaller catalog (300+ vs Zapier's 7,000+), and some pieces have few triggers/actions. — [syncgtm](https://syncgtm.com/blog/activepieces-review), [workflowautomation.net](https://workflowautomation.net/reviews/activepieces)
|
||||
- Sparse or outdated docs for Kubernetes, multi-tenant, and enterprise SSO. Community-only support (Discord/GitHub) on free. No SOC 2 / HIPAA BAA for self-hosted. — [review roundup via search: noviqip](https://noviqip.com/blogs/guides/activepieces-review-2026), [digioffly](https://digioffly.com/activepieces-review/)
|
||||
- Sparse or outdated docs for Kubernetes, multi-tenant, and enterprise SSO. Community-only support (Discord/GitHub) on free. No SOC 2 / HIPAA BAA for self-hosted. — [review roundup via search: noviqip](https://noviqip.com/blogs/guides/activepieces-review-2026), [digioffly](https://digioffly.com/activepieces-review/) (unreachable as of 2026-10-30)
|
||||
- n8n is seen as more flexible and powerful for code-heavy users, while G2 reviewers praise Activepieces' easy setup. — [G2 compare](https://www.g2.com/compare/activepieces-vs-n8n), [agntable](https://www.agntable.com/blog/activepieces-vs-n8n)
|
||||
- Default `AP_EXECUTION_MODE=UNSANDBOXED` in CE. The docs call sandboxing "the most important security decision for multi-tenant deployments". — [docs: workers](https://www.activepieces.com/docs/install/architecture/workers), [docs: environment variables](https://www.activepieces.com/docs/install/reference/environment-variables)
|
||||
- The docs themselves warn that the default `AP_WORKER_CONCURRENCY=5` "widens the OOM blast radius", and that `AP_PREWARM_CACHE_ON_STARTUP` can OOM small workers. — [docs: workers](https://www.activepieces.com/docs/install/architecture/workers), [docs: environment variables](https://www.activepieces.com/docs/install/reference/environment-variables)
|
||||
|
||||
@@ -123,7 +123,7 @@ Community health is strong and well funded. The repo has about 30.1k GitHub star
|
||||
- 30.1k stars, 3.5k forks, 169 watchers, about 13.4k commits. The contributor count was not shown on the page — [GitHub](https://github.com/kestra-io/kestra)
|
||||
- Release cadence: roughly weekly. v2.0.4 (29 Sep), v2.0.5 (5 Oct), v2.0.6 (13 Oct), v2.0.7 (20 Oct), v2.0.8 (27 Oct), each shipped alongside a 1.3.x patch (v1.3.41 to v1.3.45) — [GitHub releases](https://github.com/kestra-io/kestra/releases)
|
||||
- 2.0 is an LTS release with one year of backported fixes. Launch post dated 8 Sep 2026 — [2.0 blog](https://kestra.io/blogs/release-2-0); [web search summary of Anna Geller's LinkedIn](https://de.linkedin.com/in/geller-anna)
|
||||
- Funding: $25M Series A on 31 Mar 2026, led by RTP Global with Alven, ISAI and Axeleo, about $36M total. Earlier: an $8M seed led by Alven (Sep 2024). Tech.eu lists €22M / €29M total, which is a currency or conversion discrepancy — [The Next Web](https://thenextweb.com/news/orchestration-platform-kestra-raises-25m); [Alven](https://alven.co/kestra-raises-8m-to-lead-the-future-of-orchestration-for-business-critical-workflows); [tech.eu](https://funding.tech.eu/companies/B53F386F-689A-4978-B511-29985B65967F)
|
||||
- Funding: $25M Series A on 31 Mar 2026, led by RTP Global with Alven, ISAI and Axeleo, about $36M total. Earlier: an $8M seed led by Alven (Sep 2024). Tech.eu lists €22M / €29M total, which is a currency or conversion discrepancy — [The Next Web](https://thenextweb.com/news/orchestration-platform-kestra-raises-25m); [Alven](https://alven.co/kestra-raises-8m-to-lead-the-future-of-orchestration-for-business-critical-workflows) (dead link as of 2026-10-30); [tech.eu](https://funding.tech.eu/companies/B53F386F-689A-4978-B511-29985B65967F)
|
||||
- Traction claims (vendor): enterprise revenue up 25x in 18 months, over 2B workflows executed in 2025, and Apple engineers among its users — [The Next Web](https://thenextweb.com/news/orchestration-platform-kestra-raises-25m); [Pulse 2.0](https://pulse2.com/kestra-25-million-raised-for-open-source-orchestration-platform-expansion/amp/)
|
||||
- Older snapshot comparison: n8n had about 184.8k stars versus Kestra's about 26.7k — [openalternative.co](https://openalternative.co/compare/kestra/vs/n8n)
|
||||
- The company is French; the CTO built the precursor at the game publisher Ankama for distributed cron jobs — [Pulse 2.0 interview](https://pulse2.com/kestra-profile-ludovic-dehon-interview/)
|
||||
|
||||
@@ -57,7 +57,7 @@ Several "gated" capabilities have free near-equivalents. Pruning and concurrency
|
||||
- External backend hooks are registered with `EXTERNAL_HOOK_FILES`. They are plain JS files that run server-side and include hooks such as `n8n.ready` and `frontend.settings` — [n8n docs: external hooks](https://docs.n8n.io/hosting/configuration/external-hooks) [V, via search summary]. External hooks are not on the CE exclusion list, and a community member reports they work without a license key — [community thread, 2026-03/04](https://community.n8n.io/t/question-about-sso-via-custom-hooks-and-sul-compliance/283373) [V]
|
||||
- A NixOS deployment puts n8n behind oauth2-proxy with Kanidm. An external hook logs users in automatically from the `X-Email` header. The hook code is not shown — [git.thalheim.io dotfiles](https://git.thalheim.io/janet/dotfiles/src/branch/main/machines/eve/modules/n8n) [V, via search summary]
|
||||
- `cweagans/n8n-oidc` describes itself as "bolt-on OIDC support for n8n" (JavaScript). An aggregator lists its last push as 2025-12-29 with 2 open issues. I did not check this on GitHub — [GitTrend](https://gittrend.io/repo/cweagans/n8n-oidc) [V, aggregator]. A forum reply also names `n8n-oidc` and `n8n-community-sso`. A search for the latter found no such project — [community thread](https://community.n8n.io/t/question-about-sso-via-custom-hooks-and-sul-compliance/283373) [V]
|
||||
- Proxy-gateway SSO is a known pattern: Authelia, Authentik, Pomerium, or Cloudflare Access enforce IdP MFA and groups before a request reaches n8n. n8n's own login still applies unless a hook maps the header to a session — [lumadock guide](https://lumadock.com/tutorials/n8n-sso-options) (403 on fetch; content seen only as a search summary) [V-partial]. Header trust is safe only if the backend is reachable solely through the proxy — [Authelia nginx docs](https://gitea.unej.ac.id/techies/authelia/raw/commit/bd5bb497e3cbcb6c54f1b150db70a97564e6b6ee/docs/proxies/nginx.md) [V, via search]
|
||||
- Proxy-gateway SSO is a known pattern: Authelia, Authentik, Pomerium, or Cloudflare Access enforce IdP MFA and groups before a request reaches n8n. n8n's own login still applies unless a hook maps the header to a session — [lumadock guide](https://lumadock.com/tutorials/n8n-sso-options) (403 on fetch; content seen only as a search summary) [V-partial]. Header trust is safe only if the backend is reachable solely through the proxy — [Authelia nginx docs](https://www.authelia.com/integration/proxies/nginx/) [V, via search]
|
||||
- Git backup and sync community tooling: n8n.io template 12721 offers bidirectional GitHub sync. It detects new, edited, renamed, and deleted workflows, runs a daily backup, and has a manual restore path — [n8n template 12721](https://n8n.io/workflows/12721-back-up-and-restore-n8n-workflows-with-github-sync/). Template 7304 does backups with change detection and name-based filenames — [n8n template 7304](https://n8n.io/workflows/7304-automated-workflow-backup-with-intelligent-change-detection-using-github/). The forum's "Ultimate GitHub ↔ n8n Workflow Backup System" adds a UI and lets you import from any commit — [community.n8n.io](https://community.n8n.io/t/the-ultimate-github-n8n-workflow-backup-system-with-ui-and-commit-level-visibility/181003). `wapad/n8n-data-manager` is a shell script that backs up and restores workflows, credentials, and env to GitHub — [ecosyste.ms topic](https://repos.ecosyste.ms/topics/workflow-backup) [V, via search]
|
||||
- [K] CLI: `n8n export:workflow --all --separate --backup --output=dir/`, `n8n export:credentials --all [--decrypted]`, `n8n import:workflow --separate --input=dir/`, `n8n import:credentials`. Public REST API (`/api/v1/workflows`, `/executions`, `/credentials`, `/tags`) with `X-N8N-API-KEY`, available on CE. Security audit with `n8n audit` CLI / `POST /api/v1/audit` (risk report, not an event log). Logging with `N8N_LOG_LEVEL` and `N8N_LOG_OUTPUT=console,file`, `N8N_LOG_FILE_LOCATION`. Credential overwrites with `CREDENTIALS_OVERWRITE_DATA` (JSON per credential type) or `CREDENTIALS_OVERWRITE_ENDPOINT`. Docker secrets through `_FILE`-suffixed env vars. Queue mode with `EXECUTIONS_MODE=queue` plus Redis (`QUEUE_BULL_REDIS_*`) and `n8n worker` processes. Error Workflow (Error Trigger node) is free.
|
||||
|
||||
@@ -129,7 +129,7 @@ Most "open-core" alternatives gate the same enterprise set as n8n: SSO, RBAC, au
|
||||
|
||||
### Cited Findings
|
||||
- **Windmill** Community Edition caps SSO users at 10, users at 50, workspaces at 3, and groups at 4. Git sync works for up to 2 users. There are no audit logs, no external secret backends (Vault/AKV/AWS SM), no multiplayer, no agent workers, no worker-group management UI, no autoscaling, and no concurrency limits. SAML and SCIM are Enterprise — [Windmill pricing](https://www.windmill.dev/pricing) [V]. The license is not stated on the pricing page. [K] The core is AGPLv3, with EE features under a proprietary license.
|
||||
- **Activepieces** pricing: Free $0 (1,000 credits, 5 users), Plus $20/mo, Team $200/mo (25 users, SSO and standard roles), Ultimate custom (SCIM, custom RBAC, audit logs, secret managers, Git sync/releases, branding), Embed from $36k/yr — [Activepieces pricing](https://www.activepieces.com/pricing) [V]. The core is MIT; enterprise code is under a commercial license — [Activepieces license docs](https://www.activepieces.com/docs/about/license) [V, via search]. Sources disagree on whether CE lacks projects, SSO, audit, and Git sync (third-party summary) or has "all features" (vendor editions page) — [editions](https://activepieces.com/docs/about/editions) [V, conflicting]
|
||||
- **Activepieces** pricing: Free $0 (1,000 credits, 5 users), Plus $20/mo, Team $200/mo (25 users, SSO and standard roles), Ultimate custom (SCIM, custom RBAC, audit logs, secret managers, Git sync/releases, branding), Embed from $36k/yr — [Activepieces pricing](https://www.activepieces.com/pricing) [V]. The core is MIT; enterprise code is under a commercial license — [Activepieces license docs](https://www.activepieces.com/docs/about/license) [V, via search]. Sources disagree on whether CE lacks projects, SSO, audit, and Git sync (third-party summary) or has "all features" (vendor editions page) — [editions](https://www.activepieces.com/docs/about/license) [V, conflicting]
|
||||
- **Kestra** OSS is Apache 2.0 at $0 and includes Git integration/versioning. Enterprise adds SSO (OIDC, LDAP, SCIM), RBAC, audit logs, secrets managers, multi-tenancy, worker groups, and namespace-level secrets/variables. It is sold as an annual per-instance subscription with no listed price — [Kestra pricing](https://kestra.io/pricing) [V]
|
||||
- [K, not re-verified] **Node-RED**: Apache-2.0, no paid tier in core. Its multi-user/auth support is basic (admin auth with a passport strategy allows OIDC/OAuth). FlowFuse sells team and enterprise features. **Huginn**: MIT, fully free, multi-user, aging. **Automatisch**: AGPL-3.0 core with enterprise features under a commercial license (SSO/SAML gated). **Apache Airflow**: Apache-2.0, all features free (RBAC, OAuth/LDAP via FAB auth manager, logs to remote stores), but it is code-first, not low-code. **Temporal**: MIT server, all features free self-hosted (Temporal Cloud is paid); code-first.
|
||||
- This part of the research (search-engine results only) found no reporting of an n8n fork that unlocks enterprise features — [search results summary](https://jimmysong.io/en/blog/n8n-deep-dive/) [V, negative result]. The licensing research did find that such forks exist; see [n8n-licensing-legal.md §7](n8n-licensing-legal.md) (they are not named).
|
||||
|
||||
@@ -218,7 +218,7 @@ There is no importer. Windmill itself states: "No, there is no automated n8n-to-
|
||||
|
||||
— [windmill.dev/compare/n8n](https://www.windmill.dev/compare/n8n)
|
||||
- The CFA Institute case study (vendor-published, January 2026): the SRE team evaluated Windmill for about a year and fully migrated off n8n in early 2025. "We were very quickly able to get our scripts out of n8n and transitioned over"; "only brief training sessions" were needed. Their reasons for leaving were wanting real programming capabilities and Git workflows. They run 25 synthetic tests every 5 minutes on Windmill Cloud EE. No workflow count or effort figure is given. — [CFA Institute case study](https://www.windmill.dev/case-studies/cfa-institute)
|
||||
- n8n workflows can be exported as JSON via the CLI (`--backup` = `--all --pretty --separate`), but credential secrets stay encrypted in the n8n database. — [n8n CLI import/export](https://www.mintlify.com/n8n-io/n8n/cli/import-export)
|
||||
- n8n workflows can be exported as JSON via the CLI (`--backup` = `--all --pretty --separate`), but credential secrets stay encrypted in the n8n database. — [n8n CLI import/export](https://docs.n8n.io/hosting/cli-commands/)
|
||||
- One third-party anecdote: Windmill's rollout took 9 days including SSO, against 3 days for n8n, for two UK clients. The author flags the small sample. — [automationatlas.io](https://automationatlas.io/guides/n8n-vs-windmill-2026-comparison/)
|
||||
|
||||
### Inferences
|
||||
@@ -238,7 +238,7 @@ The recurring criticisms are these: it is a developer-only tool with a steeper l
|
||||
- On HN commentary about Windmill's benchmark claims, commenters said predictable per-job performance under concurrency matters more than raw speed. — [GeekNews summary (2023-11)](https://news.hada.io/topic?id=12005) (secondhand, older)
|
||||
- An unverified community anecdote describes a problematic workflow affecting a broader instance. The source suggests checking worker isolation and resource limits. — [airframe.ai analysis](https://www.airframe.ai/product/windmill-dev/analysis) (low reliability)
|
||||
- "Windmill's curve is steeper"; the integration catalog is "smaller and closer to developer-leaning targets"; teams need per-language worker pools. — [automationatlas.io](https://automationatlas.io/guides/n8n-vs-windmill-2026-comparison/)
|
||||
- Self-hosting is a "slightly more complex due to multi-service architecture" setup. The question is framed as "do you want to click or do you want to type?", and for non-developers setting up webhooks, "n8n wins". — [Railway compare](https://railway.com/deploy/n8n-vs-windmill) (promotional)
|
||||
- Self-hosting is a "slightly more complex due to multi-service architecture" setup. The question is framed as "do you want to click or do you want to type?", and for non-developers setting up webhooks, "n8n wins". — [Railway compare](https://railway.com/deploy/n8n-vs-windmill) (dead link as of 2026-10-30) (promotional)
|
||||
- Postgres 18 is the default, and older data volumes (16 or earlier) block startup until you migrate. This is an upgrade friction point. — [Self-host docs](https://www.windmill.dev/docs/advanced/self_host)
|
||||
- The legacy low-code app editor is now labeled "legacy" in favor of full-code React or Svelte apps. — [Docs intro](https://www.windmill.dev/docs/intro)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user