Flowise

Verdict

Do not start a new support-dependent production deployment on Flowise. The official project froze development on July 29, archived the repository on August 13, and ended core-team support on August 31, 2026. Existing users can keep running the last release or an independently maintained fork, but they now own security patches, provider compatibility, upgrades, incident response, and recovery. Migrate unless the visual flows are valuable enough to justify that maintenance commitment.

Flowise was a visual builder for LLM applications, RAG pipelines, and multi-agent workflows. Workday acquired it in August 2025, but the standalone project later ended. The acquisition does not establish support for archived deployments or a drop-in Workday successor.

Use the self-hosted AI automation shortlist to choose a maintained deployment target, or the broader AI workflow automation guide when managed services are also in scope. n8n is closer to general business automation with AI nodes; Dify is closer to visual LLM application and agent orchestration. The no-code AI workflow guide covers approvals, idempotency, evaluation, and fallbacks to preserve during migration.

Decision criteria

Current status and last advertised pricing

The official end-of-life announcement says npm packages and Docker images would be deprecated. GitHub shows 3.1.4, released July 29, as the final upstream release.

The homepage still displays Cloud cards while also saying Flowise is being sunset. /pricing redirected to login during our October 14 check, and the linked Cloud host did not resolve from our research environment. That does not prove every tenant is offline. It does mean no current purchasable offer was verified; these are preserved pre-EOL terms.

The billing label was predictions per month. Retained API docs call POST /api/v1/prediction/:id the primary flow/assistant interaction endpoint, but do not define quota treatment for retries, resumed checkpoints, failures, or internal nodes. Model, vector database, storage, and tool-provider costs remain separate when self-hosting.

Self-hosted edition and governance

The retained production guide recommends Redis queue mode, load-balanced main servers, workers, PostgreSQL instead of default SQLite, external blob storage, and a managed encryption key. This is an operations recipe, not support. Pin the source digest, mirror packages/images, scan dependencies, restrict code and MCP capabilities, and name a patch owner.

Governance had an edition boundary: workspaces/RBAC were Cloud or Enterprise, while SSO was Enterprise-only. The repository is mixed-license. packages/server/src/enterprise and explicitly marked files are commercial; code outside those restrictions is Apache 2.0. The EOL notice preserves Apache-licensed code, not enterprise rights. Existing enterprise users should check signed terms before redeployment.

Privacy and external calls

Self-hosting controls where Flowise's database, files, logs, and credential key live. It does not keep data local when nodes call model, vector, HTTP, MCP, or tracing providers. Flowise also fetched its model list from GitHub by default unless operators supplied a local file; optional analytics integrations created further data routes.

The privacy policy, last updated June 3, 2024, says self-hosted Flowise sends no metrics/data to FlowiseAI; Cloud used PostHog and Stripe and stored data in AWS US East 1. It predates the acquisition and EOL, so treat it as historical evidence, not a current Cloud retention commitment.

Credential recovery depends on the encryption key. The docs warn that regeneration or a path change can make credentials undecryptable. Preserve the key or secrets-manager state and test decryption after restore.

Human approval and recovery

Agentflow V2 supported Human Input nodes and a per-tool Require Human Input flag. Its docs say checkpoints survive an application restart. Validate parameters, reviewer identity, timeout, duplicate submission, denial, changed downstream state, and idempotent retry behavior.

In an archived community issue, LarsEbt reported on October 23, 2025 that a Condition or Human Input path could stall when its target already had a value/connection. The self-hosted Enterprise “v2” issue remained open at archive; another user reported a related case on August 6, 2026. This is version-specific, unreproduced evidence. Test the exact approval graph.

Recovery docs say to stop Flowise, disconnect database users, back up the database, and test the restore. Also preserve blob storage, configuration, provider resources, and the encryption key. In a January 22, 2024 community discussion, maintainer Henry Heng said native versioning was still on the roadmap and teams should script database snapshots.

We did not run a flow, test failover/restore, reproduce the issue, or audit the source. Existing users should inventory flows, credentials, document stores, external dependencies, approvals, and recovery material, then rebuild the highest-risk workflow on a maintained target.

Sources & further reading

• Official Flowise end-of-life announcement
• Archived repository and final upstream release
• Flowise 3.1.4 release
• Flowise mixed Apache and commercial license
• Workday acquisition announcement
• Retained Flowise Cloud plan cards
• Agentflow V2 orchestration and human checkpoints
• Prediction API and runtime input
• Queue-mode architecture
• Production deployment guidance
• Workspaces and RBAC boundary
• Enterprise SSO boundary
• Storage, credential encryption, and external model-list configuration
• Database backup and restore guidance
• Flowise privacy policy
• Community report of Agentflow V2 Human Input stalling
• Community and maintainer discussion of backup versioning