Flowise
Drag-and-drop visual builder for LangChain/LlamaIndex-based LLM apps, chatflows, and multi-agent flows.
About
Flowise is a Node.js + React visual canvas for composing LLM chains, agents, RAG pipelines, and chatbots, with API/SDK/embed publishing and Flowise Cloud hosting.
Critical: the GitHub repository was archived (~Aug 2026) — development has stopped, so no future security fixes should be expected. Fine for keeping existing self-hosted flows running; not a safe foundation for new production builds.
What it can do
- Visual drag-and-drop canvas for chains, agents, and multi-agent Agentflows
- Integrations for Pinecone, Qdrant, Weaviate, Chroma, pgvector, and 100+ LLMs/embeddings/vector DBs
- Chatflows with tool calling, memory, and RAG over multiple data sources
- Human-in-the-loop review steps and execution traces (Prometheus/OpenTelemetry)
- Publish via API, TypeScript/Python SDKs, or embedded chat widget
- Self-host on AWS/Azure/GCP/Docker/Railway/Render or use Flowise Cloud
Setup
- Install Node.js ≥ 20.
npm install -g flowisenpx flowise start- Open
http://localhost:3000— or deploy via Docker Compose. - Add LLM provider credentials and drag nodes onto the canvas.
Prerequisites
Node.js ≥ 20; LLM API keys; ~1 GiB RAM (lightest of the visual builders).
Use cases
Works with
Trust score — 6/10
Historically huge adoption (55.5k stars) with good docs and the lightest self-hosting footprint — an independent Apr 2026 review called it the fastest path from idea to working LangChain agent. But the repository is archived as of ~Aug 2026: development has stopped and no security patches will land. A competitor-authored comparison alleges serious 2026 CVEs (third-party-claimed, not independently verified).
★ 55,497 GitHub stars
How the trust score is built
Full methodology →- Adoption · stars/downloads, log-scaled vs peers
- 8.8/10
- Maintenance · recency, releases, issue load
- 2.0/10
- Openness · license + docs
- 10.0/10
- Manual review · sanity read + red-flag check
- 3.0/10
- · 55,497 GitHub stars (log-scaled vs catalog peers)
- · repository is archived — no future fixes expected
- · manual review: repo archived ~Aug 2026; alleged CVE-2026-22771 unconfirmed
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.