What happened
Flowise's own sunset page gave a code freeze on 29 July 2026, repository archival on 10 August 2026 and end of life on 31 August 2026. Its GitHub repository shows it was archived on 13 August 2026. The sunset page says the Apache 2.0 code remains yours to keep building on.
What this means if you still use it
- Do not expect new fixes from the original project. Check its sunset page for details.
- Check any cloud account, and export what you need.
- Review the security of anything exposed to the internet.
How Flowise and Hivelock compare
| Area | Hivelock | Flowise |
|---|---|---|
| Status | Early access | Sunset, repository archived |
| Builder | Visual workflow canvas and agent drafts | Visual Assistant, Chatflow and Agentflow builders |
| Self-hosting | Yes, with a free Community edition on GitHub | Yes, Apache 2.0 code remains available |
| Human approval | Built in. Changes in chat wait for a person | Human in the loop was documented |
| Integrations | 26+ connectors, plus remote MCP servers | 100+ sources, tools, vector databases and memories |
Details checked on 6 November 2026 against the Flowise sunset page, GitHub, docs. "Not stated" means we did not find it on those pages. Products change, so confirm details with the vendor.
How to move safely
- List your flows, models, tools and credentials.
- Rank them by business value and risk.
- Rebuild one flow on your chosen platform.
- Run both side by side and compare results.
- Rotate credentials once the old flow is off.
Hivelock has no automatic Flowise import. Flows are rebuilt by hand.
Common questions
Can I keep running Flowise?
The sunset page says the Apache 2.0 code is yours to keep building on. You would then be responsible for its fixes and security.
Compare with your own process.
Tell us what you want to automate. Get early access.