feat(vs/n8n): highlight persistence and resilience as Kestra differentiators#4898
Draft
elliotgunn wants to merge 9 commits into
Draft
feat(vs/n8n): highlight persistence and resilience as Kestra differentiators#4898elliotgunn wants to merge 9 commits into
elliotgunn wants to merge 9 commits into
Conversation
…tiators Add state persistence row to feature grid, new platform strength card, FAQ on crash recovery, and updated decision guide and footer text to surface the "n8n is for prototyping, Kestra for business-critical" framing. Also corrects plugin count from 1,200+ to 1,300+.
997748c to
c7f8e9a
Compare
…uage - Correct persistence claims: n8n has crash recovery but no step-level checkpointing; crashed workflows must restart from scratch, not resume - Reframe AI row from feature comparison to production reliability angle - Rename air-gapped deployment row to Deployment with run-anywhere copy - Sharpen license row with plain-language Apache 2.0 description - Fix plugin count in integration FAQ (1,200+ -> 1,300+) - Remove two em dashes (seeHowBody, AI FAQ answer) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
☁️ Cloudflare Worker Preview Deployed!🔗 https://ks-fix-n8n-vs-page-resilience-mes-docs.kestra-io.workers.dev ## 🔦 Lighthouse Benchmark
Scores (0–100, higher is better)
Core Web Vitals (lower is better)
Legend🟢 improved · 🔻 regressed · (blank) no significant change |
…chestration angle
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Positioning context
n8n wins on visual simplicity: it's the right tool for connecting SaaS apps and prototyping AI agent workflows fast. Kestra wins on production reliability: persistent execution state, step-level checkpointing, language-agnostic execution, and deployment anywhere. This page draws that line clearly rather than competing on n8n's turf.
Summary
Positioning and copy updates to the vs/n8n page based on feedback from vendor partner Stefan Fritz (SI space, SMB segment), who has been advocating Kestra over n8n to his clients and shared what wasn't landing.
Changes from initial pass
Changes from Stefan Fritz call follow-up
Fact-check corrections