Flowise is shutting down — a hosted, no-code place to land
LLMGraph vs Flowise
Flowise, the open-source drag-and-drop builder for LLM chains and agents, announced on July 29, 2026 that it is winding down: feature development has stopped, the GitHub repository is archived on August 10, and core-team support ends August 31, 2026. The code stays public under Apache 2.0, but there is no official migration path — the team's guidance is to fork the repo and maintain it yourself. LLMGraph covers much of the same ground — visual LLM workflows, RAG chatbots, agents — as a fully hosted, no-code product with one-click deployment to a REST API and an embeddable chat widget. This page is an honest look at what maps over and what doesn't.
At a glance
| LLMGraph | Flowise | |
|---|---|---|
| Status | Actively developed, hosted product | Sunset announced July 29, 2026; repo archived Aug 10; end of life Aug 31, 2026 |
| Approach | Hosted no-code canvas, or build by chat | Open-source drag-and-drop UI for chains and agents (code frozen) |
| Hosting | Fully managed — no servers, no upgrades | Self-host a fork; no further releases, security patches, or support |
| Deployment | One-click REST API + embeddable chat widget per workflow | Expose flows as endpoints from a deployment you now maintain alone |
| Target user | Developers and non-developers alike | Developers willing to own an archived Node.js codebase |
| RAG / document search | Built in and managed — upload docs and go | Composable via nodes; you operate the vector store and the app |
| Pricing | Tiered plans (Hobby / Pro / Enterprise), free credits to start | Free to fork and self-host; all operational cost and risk is yours |
Choose Flowise if…
- You're prepared to fork the Apache 2.0 codebase and own maintenance, security patches, and dependency upgrades yourself
- Your flows lean on integrations LLMGraph doesn't cover, and rebuilding them elsewhere costs more than maintaining a fork
- You need everything on your own infrastructure, accepting that upstream development has ended
Choose LLMGraph if…
- You'd rather move to something actively maintained than adopt an archived codebase
- Your Flowise use was chatbots, RAG over documents, or agents — the ground LLMGraph is built for
- You want zero infrastructure — build in the browser, ship as an API and chat widget in one click
LLMGraph vs Flowise: FAQ
- Is Flowise shutting down?
- Yes. On July 29, 2026 the Flowise team announced it is winding down: active feature development stopped immediately, the GitHub repository is archived on August 10, 2026, and core-team support ends August 31, 2026. The code remains publicly visible under the Apache 2.0 license, and the team's guidance for continued use is to fork the repository.
- What happens to my Flowise chatflows after the shutdown?
- Self-hosted instances keep running — nothing switches off on your servers — but there will be no further releases, security patches, or official support, so the maintenance burden shifts entirely to you. If you rely on Flowise for production workloads, the realistic options are maintaining a fork or rebuilding on an actively developed platform.
- Can I import my Flowise chatflows into LLMGraph?
- There is no automatic importer today. The concepts map over directly, though — chat models, prompts, retrieval over documents, memory, and branching all have equivalents on the LLMGraph canvas — so rebuilding a typical chatflow is usually quick, and you can also describe the workflow in chat and have LLMGraph build it for you. Once it's rebuilt you get a managed REST API and embeddable chat widget without running anything.
- What is the best Flowise alternative?
- It depends on what you used Flowise for. If your flows were chatbots, RAG over your own documents, or agents, LLMGraph covers that as a hosted no-code product with one-click deployment. If your flows depended heavily on Flowise's breadth of community integrations or had to stay fully self-hosted, a maintained fork or another open-source builder may fit better. Be wary of any alternative that claims a lossless one-click migration — node semantics differ between tools.
- Do I need to migrate before August 31, 2026?
- Your self-hosted Flowise won't stop working on that date, but August 31 is when core-team support ends — after that there is no upstream to report bugs or security issues to. Migrating before the deadline means you can still compare behaviour side by side while your existing flows run; waiting means debugging an archived codebase alone.