Flowise
Flowise
Low-code orchestration and agent workflow builder under an immediate feature freeze, with repository archival scheduled for August 10, 2026 and project end of life for August 31, 2026.
Curated by Tiberiu ArvaStale
Strengths
- Low-code orchestration builder
- Chatflow + agent workflow support
- Wide model/provider connectivity
Practitioner note
Active feature development has ceased. The repository is scheduled for archival on August 10, 2026 and official project support ends August 31, while the Apache-2.0 source remains available for internal or community forks.
Governance posture
Reviewed 2026-05-26Self-hosted deployment leaves data location under customer control; no current hosted-service residency commitment is asserted.
SourceThe Apache-2.0 source remains available for self-hosted forks; the official repository is scheduled for archival on August 10, 2026 and project EOL on August 31, 2026. (self-hosted)
SourceNo dedicated audit-log documentation; enterprise tier may add capabilities.
No SOC 2 certification announced by Flowise directly.
No ISO 27001 certification found in Flowise documentation.
Not mentioned in Flowise documentation.
Low-code agent/workflow builder tooling, not an AI model/provider. (role: not-applicable)
Apache-2.0 core + proprietary Commercial License for packages/server/src/enterprise (SSO/RBAC/audit). (medium)
SourceLicense history
Verified license transitions for Flowise, newest first. Relicensing is tracked as a first-class procurement risk — see the license-change feed for all tracked tools.
- More restrictive
MIT to Apache 2.0
Both licenses are permissive and OSI-approved — a minor technical tightening (NOTICE preservation, explicit patent grant), not a source-available shift.
FlowiseAI/Flowise LICENSE.md commit history
EU AI Act obligations
Risk tier: Not applicable · as of 2026-08-23Source-backed information mapped from Flowise's tracked risk tier — not legal advice. Obligations depend on how your organisation deploys the system; see the full obligation reference and timeline.
This record's EU AI Act risk tier is marked not applicable, so no tier-specific obligations attach. Deployers embedding it in an AI system in scope of the Act should assess that system's own tier.
Change history
Source-backed and auto-detected events for this tool, newest first.
- DeprecationHigh impact
Flowise announced an immediate feature-development freeze, repository archival on August 10, and project end of life on August 31; its Apache-2.0 source will remain available for forks.
The Future of Flowise - ReleaseHigh impact
Flowise 3.1.3 added chatflow-as-MCP-server and custom MCP server support, expanded Agentflow client filtering and knowledge fields, added initial observe package scaffolding, and fixed clickjacking plus frame-header handling.
Release flowise@3.1.3 · FlowiseAI/Flowise - ReleaseHigh impactFlowise release tightens security around CORS and MCP config
Flowise's April 14 release focused on security hardening, including a fix for a hardcoded CORS wildcard on the TTS endpoint and additional MCP server configuration protections.
Releases · FlowiseAI/Flowise - Auto-detectedgithubStars: 54516 → 55137
From snapshot diff 2026-07-17 → 2026-08-04.
- Auto-detectedgovernance.deployment: [object Object] → [object Object]
From snapshot diff 2026-07-17 → 2026-08-04.
- Auto-detectedlastRelease: 2026-06-25 → 2026-07-29
From snapshot diff 2026-07-17 → 2026-08-04.
- Auto-detectedHigh impactstatus: active → maintenance
From snapshot diff 2026-07-17 → 2026-08-04.
- Auto-detectedversion: 3.1.3 → 3.1.4
From snapshot diff 2026-07-17 → 2026-08-04.
- Auto-detectedgithubStars: 53392 → 54516
From snapshot diff 2026-06-07 → 2026-07-17.
- Auto-detectedlastRelease: — → 2026-06-25
From snapshot diff 2026-06-07 → 2026-07-17.
- Auto-detectedversion: 3.1.2 → 3.1.3
From snapshot diff 2026-06-07 → 2026-07-17.
Explore the category
Compare this tool against the rest of its category and the cloud platform foundation layer.
Return to the category grid to compare governance posture across every tracked tool.
Review Microsoft Foundry, Amazon Bedrock, and Gemini Enterprise Agent Platform as the foundation layer.
Track releases, deprecations, license changes, and other market movements.