01
What changed at Flowise end of life
Flowise's official sunset plan reaches its final milestone on August 31, 2026. Active feature development was frozen in July, the main GitHub repository is archived and read-only, and the original core team's official GitHub and Discord presence ends.
- The source code remains available under Apache 2.0.
- Existing self-hosted installations can continue running if their dependencies still work.
- End of life removes a normally maintained upstream; it is not a remote kill switch.
02
What EOL changes for production users
A stable deployment can keep working while becoming harder to operate over time. Model APIs, OAuth flows, Node.js versions, databases and third-party packages continue changing even when the application around them is frozen.
- Monitor vulnerabilities and dependency advisories yourself.
- Pin and document a known-good runtime before changing versions.
- Inventory every model provider, vector store, webhook, custom component and credential your flows depend on.
03
Keep, fork or migrate
Keeping Flowise can be reasonable for a stable internal deployment owned by an engineering team that accepts maintenance responsibility. Forking preserves the architecture but turns your team into the upstream maintainer. Migrating transfers more maintenance back to an active project but requires careful rebuilding and testing.
- Keep: best when the deployment is stable, controlled and actively owned.
- Fork: best when Flowise is deeply embedded and your team can maintain the codebase.
- Migrate: best when long-term upstream maintenance matters more than minimizing short-term change.
04
What to do now
Before changing anything, export and back up the system you know works. Preserve flow definitions, database state, custom components, provider settings, external integrations and a representative test set. Keep credentials in a proper secret store rather than inside migration documents.
- Create a restorable backup.
- Document runtime and dependency versions.
- Choose an explicit maintenance or migration owner.
- Do not begin a new production dependency on the archived upstream unless you intentionally accept that burden.
Sources
Primary and supporting sources
Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.