About Flowise 3.1.4 — Visual AI Agent Builder (Final Release, End of Life)
Flowise is a visual builder for AI agents and LLM workflows. You connect nodes on a canvas to build chatflows and agentflows, test them in the browser, and call them through an API. It is written in TypeScript and runs on Node.js.
This page links to GitHub’s source archive of flowise@3.1.4, the final release. Bineret did not build Flowise and is not affiliated with FlowiseAI.
Flowise has been shut down
Read this before anything else. On 29 July 2026 FlowiseAI announced it was winding down the project. Their reason, in short: developers are increasingly building with coding agents, and a rigid low-code workflow tool hits its limits as tasks get more complex. The timeline they published:
- 29 July 2026: announcement and code freeze. No new features, and pull requests are no longer reviewed.
- 13 August 2026: the GitHub repository became a public archive. Issues and pull requests are locked, and the announcement says the npm packages and Docker images will be marked deprecated.
- 31 August 2026: end of life. The core team left Discord and GitHub.
The code stays on GitHub, and FlowiseAI encourages teams to fork it.
What this means for you: 3.1.4 gets no more bug fixes, no security patches, and no updates for new models or APIs. Any vulnerability found from now on stays open unless you or a community fork fixes it.
Who this download is still for
If you already run Flowise, 3.1.4 is the version to be on. It came out on the day of the code freeze and is mostly security work: session ID validation, an operator-controlled allowlist for custom MCP stdio commands, fixes to cross-workspace authorization and tenant validation, and deny-list checks in the web scrapers and some chat model nodes. The release before it fixed clickjacking. Upgrade to 3.1.4, then plan where you are going next.
If you want to fork it, this is the last state of the code the core team shipped.
If you are starting something new, do not start it on Flowise. An actively maintained visual builder such as Langflow covers the same ground and still receives security fixes.
What it does
- Visual canvas for chatflows and agentflows, with nodes for models, tools, memory, document loaders and vector stores.
- Runs locally or self-hosted, with deployment guides for AWS, Azure, Google Cloud, DigitalOcean and others.
- Every flow is callable through an API, and 3.1.3 added turning a chatflow into an MCP server.
- A monorepo with a Node server, a React UI, the third-party node integrations, and generated API documentation.
Licence
Most of the code is Apache 2.0. The exception is everything under packages/server/src/enterprise, plus files carrying their own copyright notice such as IdentityManager.ts, which are under a separate commercial licence. If you fork Flowise, check which side of that line the code you change sits on.
Requirements
The package.json at 3.1.4 declares Node.js 24 and pnpm 10.26 or newer, though the README’s quick start still says Node 20. Go with 24. Flowise serves its UI on http://localhost:3000.
Key capabilities
The project has ended
Code freeze on 29 July 2026, public archive on 13 August, end of life on 31 August. No more bug fixes, security patches or model updates from FlowiseAI, and issues on GitHub are locked.
The version to be on
3.1.4 is mostly security work: session ID validation, an operator-controlled MCP stdio allowlist, cross-workspace authorization and tenant validation fixes, and deny-list checks in scrapers and chat model nodes.
Good for forks, not new builds
FlowiseAI encourages teams to fork the code. For a new project, pick a maintained visual builder that still ships security fixes instead of inheriting every future vulnerability.
A licence with a line in it
Apache 2.0 covers most of the code. packages/server/src/enterprise and files with their own copyright notice, such as IdentityManager.ts, are under a commercial licence. Check which side your changes fall on.
Chatflows and agentflows
Connect nodes for models, tools, memory, loaders and vector stores on a canvas, test in the browser, and call flows through the API. 3.1.3 added serving a chatflow as an MCP server.
Questions & Answers
Is Flowise still maintained?
No. FlowiseAI froze the code on 29 July 2026, archived the repository on 13 August and ended the project on 31 August. There will be no further releases from them.
Should I start a new project on it?
No. Without security fixes, every vulnerability found from now on stays open. Choose an actively maintained builder instead, such as Langflow.
I already run Flowise. What should I do?
Upgrade to 3.1.4, which is mostly security fixes, and do not expose the instance to the internet without authentication in front. Then plan a migration, or move to a maintained community fork if one suits you.
Can I fork it?
Yes, FlowiseAI encourages it. Most of the code is Apache 2.0, but packages/server/src/enterprise and files with their own copyright notice, such as IdentityManager.ts, are under a commercial licence.
Will npm and Docker keep working?
The code and packages remain available. The announcement says npm packages and Docker images will be marked deprecated. When we checked on 13 September 2026, npm's latest for flowise was still 3.1.4 with no deprecation notice.
Which Node.js version?
Node.js 24. The package.json at 3.1.4 requires it, even though the README quick start still mentions Node 20.
Is Bineret connected to FlowiseAI?
No. This page describes Flowise and links to the source archive GitHub generates for its final tag.
Tutorials
Read the end-of-life notice first
Flowise reached end of life on 31 August 2026 and receives no more security fixes. Use this to keep an existing install current or as the base for a fork, not for a new project. The announcement is The Future of Flowise.
Upgrade an existing npm install to 3.1.4
npm install -g flowise@3.1.4
npx flowise startBack up your Flowise data before upgrading. Then open http://localhost:3000 and check your flows still run.
Build from the source archive
You need Node.js 24 and pnpm 10.26 or newer.
npm i -g pnpm
unzip Flowise-flowise-3.1.4.zip
cd Flowise-flowise-3.1.4
pnpm install
pnpm build
pnpm startIf the build stops with exit code 134 (JavaScript heap out of memory), raise Node's heap and build again:
export NODE_OPTIONS="--max-old-space-size=4096" # PowerShell: $env:NODE_OPTIONS="--max-old-space-size=4096"
pnpm buildRun with Docker Compose
From the unpacked archive, go to the docker folder, copy .env.example to .env, and start it:
cd docker
cp .env.example .env
docker compose up -dStop it with docker compose stop.
Planning a move
Export the flows you depend on before you need to, and note which nodes and credentials each one uses. That list is what you will rebuild in whatever replaces Flowise.
Support
There is no official support any more
FlowiseAI's core team left GitHub and Discord at end of life on 31 August 2026, and the repository's issues are locked. The documentation is the remaining official reference, for as long as it stays online.
Where to look instead
Community forks are the only place fixes can come from now. Before relying on one, check that it is actually receiving commits and security fixes.
What Bineret covers
This page. If the download link is broken or something written here is wrong, tell us and we will fix it. We do not maintain Flowise or a fork of it.
No warranty
Apache 2.0 provides the software as-is, and with the project ended nobody is fixing what breaks. Keep any instance you still run off the public internet.