Flowise
flowiseai.com
- Free plan
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What Flowise is
Flowise is an open-source platform for building generative AI agents and workflows based on large language models. Its Assistant, Chatflow, and Agentflow visual builders cover assistants, chatbots, single- and multi-agent systems, and workflow orchestration. Listed capabilities include execution logs, visual debugging, evaluations, human review, and retrieval-augmented generation indexing pipelines. Documentation describes connections to more than 100 sources, tools, vector databases, and memories, including LangChain, LlamaIndex, and Zapier Zaps. Developers can use APIs, an embedded chat widget, and TypeScript or Python SDKs. Deployment options include cloud, on-premises, and self-hosting. Listed security controls include role-based access, single sign-on, encrypted credentials, secret managers, rate limits, and restricted domains. Flowise is winding down: active feature development ceased July 29, 2026; repository archival is listed for August 10, and end of life for August 31, 2026. Its source remains under Apache 2.0, and the notice encourages teams to fork it. The Free plan costs nothing; Starter costs $35 a month.
Who it suits
Flowise may suit developers and teams building AI assistants, agents, or LLM workflows who can account for its announced end of life. Its builders and deployment options are relevant to both cloud and self-hosted projects.
Good to know, and what to watch
- Visual builders cover assistants, chatbots, and multi-agent systems.
- Connects to more than 100 listed sources and tools.
- Offers APIs and TypeScript and Python SDKs.
- Documentation lists multiple security controls.
- Source remains under the Apache 2.0 license.
- Active feature development ceased July 29, 2026.
- End of life is listed for August 31, 2026.
- Packages and Docker images would be marked deprecated after archival.
Plans
Every plan and priceFree
Starter
Pro
Free plan
Getting started
- Visit https://flowiseai.com/.
- Choose the Free plan or Starter plan, or use the source code under Apache 2.0.
- Use the cloud or on-premises deployment route, or follow the repository's npm or Docker installation instructions.
- Build with Assistant, Chatflow, or Agentflow.
- Connect sources, tools, vector databases, or memories as needed.
Limits to check
The Free plan costs nothing and is limited to two flows and assistants, 100 predictions per month, and 5MB storage. Starter costs $35 a month and includes 10,000 predictions per month and 1GB storage; active feature development has ceased and end of life is listed for August 31, 2026.
The Club's review
Overview
Flowise is an open-source platform for building AI agents and LLM workflows. Its visual builders and developer interfaces suit teams that want to construct and operate workflows themselves, but its announced shutdown makes it a difficult choice for new deployments.
Assistant, Chatflow and Agentflow builders cover assistants, chatbots, single- and multi-agent systems, and workflow orchestration. That range supports both focused chatbot projects and more involved agent workflows. The major drawback is the maintenance timeline: active feature development ceased on July 29, 2026, repository archival is scheduled for August 10, and end of life for August 31, 2026.
Flowise says its source code will remain on GitHub under the Apache 2.0 license and encourages teams to fork it. That is a practical route for organizations prepared to own maintenance, but it is not a continuation of upstream development or official core-team support.
Key features
Execution logs, visual debugging, evaluations, human review, and RAG indexing pipelines extend the builders beyond basic workflow assembly. Teams can inspect executions, evaluate results, and incorporate human review—useful capabilities for developing grounded or multi-step applications. Flowise connects to more than 100 sources, tools, vector databases, and memories, including LangChain, LlamaIndex, and Zapier Zaps.
APIs, an embedded chat widget, and TypeScript and Python SDKs give developers several ways to connect Flowise workflows to other products. The documentation also lists RBAC, SSO, encrypted credentials, secret managers, rate limiting, and restricted domains. For production, Flowise recommends queue mode, PostgreSQL at scale, AWS S3 storage, and AWS Secret Manager for credential key management; that guidance signals that reliable larger deployments require operational planning, not just visual configuration.
The product site describes cloud and on-premises deployment, while npm and Docker installation instructions and self-hosting options are provided. Teams can choose a deployment approach, but should weigh that flexibility against the end-of-life schedule and the prospect of maintaining a fork themselves.
Pricing
The Free plan costs nothing and includes two Flows and Assistants, 100 Predictions per month, 5MB of storage, Evaluations & Metrics, custom embedded chatbot branding, and community support. It is enough to explore the builders or run a small project, but the flow, prediction, and storage caps make it a poor fit for sustained use at scale.
Starter costs $35 a month. It keeps the Free features while removing the flow-and-assistant cap, raising the allowance to 10,000 Predictions per month, and providing 1GB of storage. That is the more practical paid tier for a small deployment, though it still has a monthly prediction quota and community support.
Pro costs $65 a month and includes 50,000 Predictions per month, 10GB of storage, unlimited workspaces, admin roles and permissions, and priority support. It includes five users; each additional user costs $15/user/month. Those higher limits and controls better suit teams sharing work across projects, but the published end-of-life timeline undercuts the case for committing to a paid plan for long-term production use.
Platforms
Flowise supports API, Linux, macOS, self-hosted, web, and Windows environments. That breadth, along with cloud and on-premises deployment, gives technical teams options for where to run workflows. It does not remove the need to plan for the announced end of life.
Who it's for
Flowise is most appropriate for developers and teams evaluating visual AI workflow design, or for organizations willing and able to fork and maintain the Apache 2.0 code. Its builders, integrations, SDKs, and self-hosting options are a strong fit for that technically capable audience. It is not a sound default for teams seeking an actively developed, vendor-supported platform for new production systems.
Pros and cons
- Pros: Three visual builders address assistants, chatbots, single- and multi-agent systems, and orchestration in one platform.
- Pros: More than 100 integrations, developer APIs and SDKs, and deployment choices support varied technical workflows.
- Pros: Logs, debugging, evaluations, human review, and RAG pipelines support inspection and iteration beyond simple workflow assembly.
- Cons: Feature development has stopped, with repository archival and end of life scheduled for August 2026, making new production adoption risky.
- Cons: Teams that want to continue after the wind-down must take on the responsibility of maintaining a fork; official core-team presence in Discord and GitHub concluded on August 31, 2026.
- Cons: Free has only 100 Predictions per month and 5MB of storage, while Starter and Pro also impose prediction and storage limits.
Alternatives
For broader workflow automation rather than a platform specifically centered on AI agents and LLM workflows, consider Retool, which offers a free plan and a Team plan at $10 a month per builder, plus $5/mo per internal user and 5,000 workflow runs per month.
Camunda is an alternative if you want a freemium workflow platform with self-managed development and testing at no license cost; its development plan is not a production license.
Houston may fit small groups looking for a free personal workspace for up to three people, with limited usage and more than 1,000 integrations.
Workato Agentic is another option to compare if its free plan with 50,000 one-time credits or its Pro plan at $75 a month better fits your usage model.
Microsoft Copilot offers a free tier with access subject to capacity and usage limits, and may suit readers seeking a general-purpose assistant rather than a workflow-building platform.
Vellum offers a free starting tier with initial tasks and pay-as-you-go credits, while its Mighty plan costs $30 a month.
Google Agent Development Kit is a free open-source framework to consider if you prefer a framework approach; model and cloud service use may require separate access or billing.
Automation Anywhere Document Automation offers a Community Edition for eligible small businesses, including document automation for up to five machines and 100 pages per month.
Readers comparing the wider field can browse AI Agent Platforms and Retrieval-Augmented Generation Tools.
Verdict
Flowise is worth considering for teams exploring visual agent and LLM workflow development, especially if they value self-hosting and are prepared to maintain open-source software themselves. Its builders, integrations, and developer access are compelling, but the scheduled wind-down is the decisive constraint. For a new production system that needs ongoing development or official support, choose another platform.
The verdict
Flowise provides visual tools and developer access for building AI workflows, but its announced wind-down is central to any adoption decision. The Free plan costs nothing and Starter costs $35 a month.
Questions people ask
Is Flowise open source?
Yes. Flowise describes itself as open source, and its sunset notice says the source remains on GitHub under Apache 2.0.
What does the Free plan include?
It costs nothing and includes two flows and assistants, 100 predictions per month, 5MB storage, evaluations and metrics, custom embedded chatbot branding, and community support.
How much does Starter cost?
Starter costs $35 a month. It includes unlimited flows and assistants, 10,000 predictions per month, and 1GB storage.
Which platforms are supported?
Flowise lists API, Linux, macOS, self-hosted, web, and Windows.
Can Flowise be self-hosted?
Yes. The product site describes on-premises deployment, and the repository provides self-host deployment options plus npm and Docker installation instructions.
What is happening to the project?
Flowise says active feature development ceased July 29, 2026; it lists repository archival on August 10 and end of life on August 31, 2026.
What the maker publishes
- Deployment
- The product site describes cloud and on-premises deployment, while the repository provides npm and Docker installation instructions and self-host deployment options. source
- Developer access
- The homepage lists APIs, an embedded chat widget, and TypeScript and Python SDKs. source
- Features
- Its listed capabilities include visual orchestration, execution logs, visual debugging, evaluations, human review, and RAG indexing pipelines. source
- Integrations
- Flowise documentation says it connects to 100+ sources, tools, vector databases, and memories, and lists LangChain, LlamaIndex, and Zapier Zaps integrations. source
- License
- The sunset notice says Flowise source code remains on GitHub under the Apache 2.0 license and encourages teams to fork it. source
- Maintenance limit
- The sunset notice says active feature development ceased on July 29, 2026, and that npm packages and Docker images would be marked deprecated after repository archival. source
- Product
- Flowise is an open source generative AI development platform for building AI agents and LLM workflows. source
- Production guidance
- Production documentation recommends queue mode, PostgreSQL at scale, AWS S3 storage, and AWS Secret Manager for credential key management. source
- Security
- Documentation lists RBAC, SSO, encrypted credentials, secret managers, rate limiting, and restricted domains as security controls. source
- Sunset
- Flowise says it is winding down operations; its site lists a July 29, 2026 code freeze, August 10 repository archival, and August 31 end of life. source
- Support
- The documentation lists community support and vendor support including SLA support and consultations; the sunset notice says official core team presence in Discord and GitHub concluded on August 31, 2026. source
- Visual builders
- The platform provides Assistant, Chatflow, and Agentflow visual builders for assistants, chatbots, single-agent and multi-agent systems, and workflow orchestration. source
Checked against the maker's pages on 1 Oct 2026.