Flowise pricing guide details
Sources checked: October 23, 2026: sunset notice and displayed Cloud pricing.
Pricing Overview
Flowise has announced its sunset. Treat it as an existing-deployment or fork-maintenance decision before considering a new subscription. Its notice scheduled a July 29 code freeze, August 10 repository archival and August 31, 2026 end of official core-team participation. Those dates describe the announced schedule; they do not establish a Cloud shutdown date.
The Apache 2.0 source remains available to fork. There is no software license charge for that code, but hosting, model access and maintenance still need a budget. A free license does not provide ongoing vendor support.
Cloud Prices Still Displayed
The homepage still displays the following monthly plans. Current signup availability, service continuity and fulfillment of the listed support terms are unverified after the sunset announcement. Confirm these directly before paying. These are displayed rates, not a recommendation to start a new deployment.
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Plan | Displayed monthly price | Published allowance |
|---|---|---|
| Free | $0 | 2 flows and assistants; 100 predictions; 5 MB storage |
| Starter | $35 | Unlimited flows and assistants; 10,000 predictions; 1 GB storage |
| Pro | $65 | 50,000 predictions; 10 GB storage; 5 users, with additional users listed at $15/user/month |
A prediction allowance is not an all-in model budget. Confirm what consumes a prediction, whether model-provider charges are separate and what happens at the limit. Do not infer an annual discount or a currently available enterprise contract from this matrix.
What Self-Hosting Costs
Build the estimate from the deployment you will operate: compute, storage, database services, model or API usage, monitoring, backups and security maintenance. No generic VM price or model bill is reliable without workload and provider choices.
Fork maintenance is now part of the decision. Assign responsibility for dependency updates, vulnerability fixes and recovery, and verify whether any community fork you consider has active maintainers. The sunset notice encourages forks; it does not promise their support or release cadence.
Which Path Makes Sense?
Existing deployment: inventory flows, credentials, data and external model dependencies. Test an export or migration path and identify who will maintain the code before committing more workloads.
New deployment: require an accountable maintenance path and confirmed hosting terms first. Compare supported alternatives on deployment ownership, migration effort and metering, rather than treating the displayed subscription as a complete operating cost.
How to Evaluate Alternatives
Use Flowise alternatives to shortlist options, then inspect the Dify pricing guide and LangChain pricing guide. Predictions, message credits, traces and seats meter different things; compare the same workload and include hosting and model costs. Check current vendor terms before buying.