Flowise Is Shutting Down
Flowise, a platform for building AI apps, is shutting down due to a shift in how people build and the increasing reliance on new coding agents. The decision was made to wind down operations, and the team will no longer be reviewing or accepting new pull requests. The Flowise source code will remain on Github and is available for teams to fork and maintain their own internal updates.
- ▪Flowise is shutting down due to a shift in how people build and the increasing reliance on new coding agents.
- ▪The Flowise GitHub repository will be moved to Public Archive status on August 10, 2026.
- ▪The Flowise source code will remain on Github and is available for teams to fork and maintain their own internal updates.
Hacker News (Front Page) files mainly under programming. We currently carry 1,215 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Flowiseai |
| Canonical URL | https://flowiseai.com/sunset |
| Publication time | Wed, 05 Aug 2026 00:02:40 +0000 |
| Retrieval time | 2026-08-05T00:45:47.127Z |
| Last seen | 2026-08-05T00:45:47.127Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
The Future of FlowiseHey everyone,When we started Flowise, we wanted to make building AI apps easier and more fun for everyone. Seeing what you've built, from simple bots to massive workflows has truly been the best part of this journey. You have made this project what it is today.Over the last few months, we've noticed a significant shift in how people build. As AI models become more capable at reasoning, we've noticed that developers are increasingly relying on new coding agents such as Claude Code/OpenClaw to handle complex tasks. The typical rigid workflow low code approach quickly hits the limit when it comes to complexity.It's with these shifts in mind that we've decided to wind down our operations for Flowise.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Flowiseai.
Discussion
0 commentsMore from Flowiseai
