Flowise alternative
Moving off Flowise? Bring your flows with you.
The Flowise team has wound the project down. Export your agentflow or chatflow, paste it into Nodagentry and see it as a graph with the cost of every step. Then run it, cut its cost and publish it.
Free, no account. Your export is read in your browser.
Move a flow in three steps
- In Flowise, open the flow, open its settings menu at the top right of the canvas and choose Export. You get a
.jsonfile. - In Nodagentry, open Import agent code and paste the file, or use Upload file. The panel shows the steps and models it found.
- Choose Import to canvas and Run baseline. The simulator needs no key and shows the route and the cost of every step. Apply the top insight and run again to compare.
Signed in, each import is saved as a new workflow you can test, publish and run from events.
How Flowise nodes map
| In Flowise | In Nodagentry |
|---|---|
| Start | Input |
| Agent, LLM | Model step, priced at its model's list price |
| Condition Agent | Model step, then a branch per scenario |
| Condition | Branch point, one route per condition |
| Human Input | Approval gate |
| Tool, Retriever, HTTP | Tool step (a stand-in in the simulator) |
| Custom Function | Code step, costs nothing |
| Loop | Drawn as one pass, and listed so you know |
| Iteration | Its steps, counted for one item |
| Chatflow chain or agent + chat model | Model step on that model, with its tools after it |
Flowise and Nodagentry, side by side
An honest comparison. Nodagentry is narrower than Flowise and focused on what a flow costs and how to cut it.
| Flowise | Nodagentry | |
|---|---|---|
| Visual editor for multi-agent flows | ||
| Cost of every step before you run | ||
| Free simulator, no API key | ||
| Suggested fixes with before/after compare | ||
| Import LangGraph, CrewAI, OpenAI Agents code | ||
| Cost check on pull requests | ||
| Start a flow from an API call or webhook | ||
| Hundreds of integrations and vector stores | ||
| Embeddable chat widget | ||
| Self-hosted | ||
| Maintained | Archived Aug 2026 |
Questions
- Is Flowise shut down?
- The Flowise team announced it is winding down Flowise: a code freeze on 29 July 2026, the GitHub repository archived on 10 August 2026 and end of life on 31 August 2026. The Apache 2.0 code stays on GitHub and can be forked, but the core team no longer develops or supports it.
- Which Flowise flows can I import?
- Agentflow V2 exports (Start, Agent, LLM, Condition, Condition Agent, Human Input, Loop, Iteration, Tool, Retriever, HTTP, Custom Function and Direct Reply nodes), Sequential Agents and Multi Agents agentflows, and chatflows built from chains or agents with their chat model, tools and retrievers.
- Is my Flowise export uploaded?
- No. The export is read in your browser. Nothing is sent to a server unless you sign in and save the imported workflow to your account. Exports hold credential IDs, not API keys, and Nodagentry ignores them.
- What doesn't come across?
- Credentials, vector store contents, document loaders, memory settings and the chat embed widget. Tools and retrievers come across as stand-in steps, so the simulator can run the flow and price it; custom JavaScript functions become code steps.
- Does Nodagentry replace Flowise entirely?
- Not one for one. Flowise has hundreds of integrations and a chat widget; Nodagentry focuses on seeing and cutting what a multi-agent flow costs, testing it before and after a change, and running it from webhooks and events. If you need the integrations, a community fork of Flowise may suit you better.
Nodagentry is an independent product by Wasapile Labs and isn't affiliated with FlowiseAI. Flowise is a trademark of its owners.