Skip to content
buildbay.
Flowise logo

Flowise

FlowiseAI · Workflow automation

GitHub stars

55,401
—Not live-tracked

Not live-tracked

No measured star history yet

What is Flowise?

Flowise packages chat assistants and multi-agent workflows into a visual builder backed by APIs and SDKs. The upstream project has reached end of life: its repository is archived and the announced core-team support period ended on August 31, 2026. Teams continuing to use the source should plan for maintenance through an internal or community fork.

Flowise is an archived visual builder for AI agents and LLM workflows, with APIs, embedded chat, tracing, evaluations, and human-review steps. Active development ended in July 2026, the repository was archived on August 13, and the announced end-of-life date was August 31, 2026. Existing deployments need their own maintenance plan.

Core capabilities

  • Compose chat, agent, and multi-agent flows visually
  • Add retrieval, tool calling, human review, and execution tracing
  • Expose flows through APIs, SDKs, or embedded chat

Visual agent building

Agentflow coordinates multi-agent work, Chatflow supports assistants with tool calling and retrieval, and human-in-the-loop steps let reviewers intervene. Execution traces, evaluations, Prometheus, and OpenTelemetry support inspection after a flow runs.

  • Agentflow
  • Chatflow
  • RAG
  • observability

Archived project status

The maintainer announcement ended feature development on July 29, 2026 and set August 31 as the end of the core team's GitHub and Discord presence. GitHub confirms that the repository was archived on August 13. The Apache-2.0 source remains available for forks, but new adopters should evaluate who will maintain dependencies and address future issues.

  • archived
  • end of life
  • Apache-2.0

Where it fits

Use cases

  1. 01

    Maintain an existing Flowise deployment

    Operate or fork a current Flowise installation when its visual flows, embedded assistants, and integrations already support production work, while taking ownership of maintenance beyond the upstream project's end of life.

  2. 02

    Study a visual agent architecture

    Inspect the archived Apache-2.0 codebase to understand how Flowise composes model, retrieval, tool, state, and human-review nodes into agentic systems with observable execution traces.

  3. 03

    Fork a workflow platform internally

    Use the archived repository as a starting point for an internal or community-maintained fork, retaining API, SDK, embed, queue, worker, and on-premises deployment patterns under your own maintenance plan.