Stacks and Flows

Flowise

Archived visual builder for LLM agents and chatflows — self-hostable for teams with an explicit maintenance plan.

platform open-source Updated 2026-09-15
Visit Flowise →

Use when

  • JavaScript and TypeScript developers prototyping LLM apps without Python
  • Teams prepared to own a fork of the Apache-licensed code
  • Embedded use cases — chat widgets, API-driven agents inside Node.js apps

Operational upside

  • Code outside the repository's specified enterprise paths remains available under Apache 2.0
  • Node.js-native — JavaScript and TypeScript developers stay in their stack
  • Built-in chat widget, API, and embed surfaces
  • Good catalog of LLM, vector store, and document loader nodes out of the box

Avoid or plan for

  • The official repository is archived and official core-team maintenance ended August 31, 2026
  • Less depth on agent orchestration than LangGraph-style frameworks
  • New deployments need a maintenance or migration plan rather than assuming continued vendor support
  • Documentation is functional but thinner than competitors
  • Integration catalog skews AI-heavy; light on general SaaS connectors

What it is

Flowise is a visual builder for LLM applications, written in TypeScript and built on Node.js. The canvas wires together chains, agents, retrievers, memory, and tools. On July 29, 2026, the project’s maintainers announced a code freeze, repository archival, and end of official core-team presence on August 31, 2026. That date has passed and the official repository is archived. Code outside the repository’s specified enterprise paths remains under Apache 2.0; new adopters must plan for ownership or migration.

Flowise sits in the same broad space as Langflow and Dify: visual builder, API, and RAG support. Its JavaScript stack remains useful to teams willing to maintain the deployment, but the announced EOL changes the decision from “which builder is nicer” to “who will own the fork and migration path.”

Who it’s for

Flowise may still fit JavaScript and TypeScript teams that intentionally accept maintenance ownership of the available code and review the mixed licence boundary. For a new deployment that depends on vendor support or an actively maintained managed product, evaluate alternatives first.

It’s a poor fit for teams already deep in Python and LangChain (Langflow is the natural pick) and for teams who need a polished end-user agent product (Dify is further along).

Strengths

  • Source availability. Code outside specified enterprise-restricted paths is available under Apache 2.0; review the repository licence before forking or redistribution.
  • Node.js-native. Custom components are TypeScript classes; integration with existing JS apps is direct.
  • Visual builder. The Node.js canvas supports agent, retrieval, and tool components without a Python runtime.
  • Embedding surface. Chat widget, REST API, and SDK are available in the project.
  • Self-host path. Docker and Node.js deployment paths exist, but ongoing maintenance now needs an explicit owner.

Weaknesses / Watch out

  • End of life. Official core-team maintenance ended August 31, 2026, and the official repository is archived.
  • Agent orchestration is shallower. No native LangGraph-equivalent for complex multi-step or multi-agent flows.
  • Support continuity. Do not assume continued managed-cloud or core-team support beyond the announced timeline; verify the vendor’s current service status before purchase.
  • Documentation gaps. Covers the basics well, thin on edge cases and production deployment patterns.
  • SaaS integrations. AI-side is rich; non-AI connectors (CRMs, billing, ops tools) are limited compared to n8n or Dify.

Best paired with

  • OpenAI, Anthropic, or local models via the standard LLM nodes.
  • Pinecone, Chroma, or pgvector for vector storage; all have first-class nodes.
  • Next.js or Express apps as the host environment for embedded chat widgets.
  • n8n for SaaS plumbing around Flowise agents — same pattern as Dify or Langflow.

Verdict

Not a default choice for a new deployment after official maintenance ended. Existing users can keep running or fork the code under its applicable terms, but they need an explicit maintenance and migration plan. New teams should compare actively maintained alternatives unless owning the fork is a deliberate decision.

Sources

FAQ

Is Flowise free?
Flowise has a free tier or open-source edition. See pricing details on the official site for paid features and usage limits.
What is Flowise best for?
JavaScript and TypeScript developers prototyping LLM apps without Python Teams prepared to own a fork of the Apache-licensed code Embedded use cases — chat widgets, API-driven agents inside Node.js apps
What are the main downsides of Flowise?
The official repository is archived and official core-team maintenance ended August 31, 2026 Less depth on agent orchestration than LangGraph-style frameworks New deployments need a maintenance or migration plan rather than assuming continued vendor support
Who should use Flowise?
Archived visual builder for LLM agents and chatflows — self-hostable for teams with an explicit maintenance plan. See our review for the full pros and cons.