Skip to content

fix(comparisons): stop recommending Flowise after its end of life and source its facts from Flowise - #9239

Merged
waleedlatif1 merged 1 commit into
stagingfrom
fix/comparisons-flowise-eol-profile
Oct 20, 2026
Merged

waleedlatif1 merged 1 commit into
stagingfrom
fix/comparisons-flowise-eol-profile

Conversation

@waleedlatif1

Copy link
Copy Markdown
Collaborator

Summary

  • The Flowise comparison still recommended Flowise in its bottom line ("Choose Flowise if you specifically need…"), built from its first standout feature, even though the open-source project reached end of life on August 31, 2026. Adds an optional chooseCompetitorAnswer profile field that replaces the generated verdict, and sets it for Flowise: choose it only if you already run it and will maintain a fork
  • Adds the end of life as Flowise's first documented limitation, so the generated "main difference" and "documented limitations" FAQs state it
  • Re-sources the Cloud plan, pricing, deployment, support, SLA, community, data residency, and company facts to flowiseai.com and its sunset page (checked 2026-10-19), replacing a third-party pricing blog. Cloud plans are still listed on flowiseai.com and the sunset notice covers only the open-source project, so the facts say that rather than calling Cloud discontinued. The unsourced 99.99% SLA claim is now "no published SLA"
  • The re-dated sources move the page's "last verified", JSON-LD dateModified, and sitemap date to 2026-10-19; getLatestVerifiedDate only reads fact-source dates, so the earlier prose-only update never reached them
  • The Flowise FAQ no longer says the npm package and Docker image were marked deprecated: the sunset page said they would be, but npm shows no deprecation and the last release (3.1.4) shipped July 29, 2026
  • Sim's free-plan fact now reads "worth $5 on Sim Cloud", since self-hosted deployments can override the free allowance

Type of Change

  • Bug fix

Testing

  • Ran buildBottomLine, buildComparisonFaqs, and the latest-verified date for all 20 competitors before and after: only Flowise changed (verdict, limitation FAQs, date 2026-10-15 → 2026-10-19); Sim's verdict is byte-identical
  • Checked every new Flowise fact against the raw HTML of flowiseai.com and flowiseai.com/sunset, npm view flowise, and the GitHub repository
  • biome; check:source-conventions, check:comment-hygiene, check:unused-exports, check:site-urls

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing (new tests pass the test-audit authoring gate)
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

@vercel

vercel Bot commented Oct 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
docs Skipped Skipped Oct 20, 2026 12:21am UTC

Request Review

@waleedlatif1
waleedlatif1 merged commit 9a72a84 into staging Oct 20, 2026
41 checks passed
@waleedlatif1
waleedlatif1 deleted the fix/comparisons-flowise-eol-profile branch October 20, 2026 00:22
@greptile-apps

greptile-apps Bot commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Summary

Adds a profile-specific verdict so Flowise is recommended only for existing teams prepared to maintain a fork.

  • Flowise is recommended only to teams prepared to maintain a fork.
  • Flowise comparisons distinguish the ended open-source project from its listed Cloud plans.
  • The free-plan credit value is labeled as applying to Sim Cloud.

No actionable issues found.

Reviews (1) · Last reviewed commit: "fix(comparisons): stop recommending Flow..." · Reviewed by Greptile

This branch was previously deployed

1 inactive deployment
Preview — 33d70c66 Deployed Oct 20, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant