N8NChatUI vs Flowise (Flowise Is Sunsetting — What to Do Instead)
A widget built for n8n workflows — actively developed, with a secure proxy, real-time analytics, and a documented JS API. A stable landing spot for the chat front end if you're migrating logic off a platform that's being discontinued.
An open-source visual builder for LLM/agent chains, with its own embeddable chat widget — but Flowise is being sunset. Its GitHub repository was archived in August 2026, the core team is winding down support through the end of that month, and no successor product has been announced.
This isn't a routine feature comparison — it's a heads-up. Flowise's own team announced they're sunsetting the project: code froze July 29, 2026, the GitHub repo was archived August 10–13, and the team is stepping back from Discord and GitHub entirely by August 31, 2026. Their stated reasoning is that rigid low-code workflow builders "hit the limit when it comes to complexity" compared to reasoning models and coding agents. No successor was named. The Apache 2.0 code stays available to self-host or fork indefinitely, but there's no active development, no roadmap, and no support channel going forward.
If you're one of the people who used Flowise to power a chat widget — its own chatflow builder as the "brain," with the flowise-embed widget as the front end — that combination now has an expiration date measured in how long you're willing to run unmaintained infrastructure. Worth deciding on a migration path rather than waiting for something to break.
n8n is a reasonable landing spot for the logic itself, since it's under active development and already has documented (if manual) integration patterns with tools like Flowise's API. Pairing an n8n workflow with a Managed Widget replaces both halves — the flow logic and the widget — with actively maintained pieces.
Feature-by-feature
| Feature | N8N Chat UI (Managed Widgets) | Flowise |
|---|---|---|
| Project status | Actively developed and maintained | GitHub repo archived Aug 2026; core team departing; no successor announced |
| Price | $70 / 25,000 messages (Professional tier), 100 free credits to start | Cloud: Free (2 flows/100 predictions), Starter $35/mo (10,000 predictions), Pro $65/mo (50,000 predictions) — long-term availability of paid cloud tiers is now uncertain given the sunset |
| Self-hosting | Managed only | Free to self-host (Apache 2.0); code remains available indefinitely, frozen at its last release |
| Where the logic lives | Your n8n workflow | Flowise's own visual chatflow builder — a platform alternative to n8n, not a companion to it |
| n8n connectivity | n8n workflow is the entire backend | No native node either direction — the common pattern is n8n's HTTP Request node calling Flowise's prediction API |
| Webhook / endpoint exposure | Hidden — routed through a proxy | apiHost and chatflow ID exposed client-side by default; docs mention an optional proxy setup to conceal them |
| Domain restrictions | Domain restrictions + geofencing | "Allowed Domains" allowlist per chatflow — open to all domains by default if unconfigured |
| Rate limiting | Built in | Available per-chatflow |
| Analytics | Real-time dashboard — usage, sessions, performance | No native dashboard — relies on third-party observability tools (Langsmith, Langfuse, and similar) |
| Voice / uploads | Voice input supported | Speech-to-text and file/image uploads configurable per chatflow (unclear if this covers the embedded widget or only Flowise's internal test UI) |
| Programmatic JS API | open()/close(), sendMessage() with metadata, live updateTheme(), updatePrompts() mid-conversation | init()/initFull(), clearChat(), and observer callbacks — no open/close/sendMessage or live theme-update API documented |
| RTL / language support | Yes (Arabic, Hebrew, Persian, and others) | English-only, left-to-right; RTL/i18n is an open, unimplemented GitHub feature request |
Flowise's Apache 2.0 license means self-hosting the frozen code stays technically possible indefinitely — if your setup already works and you're comfortable running unmaintained infrastructure with no security patches going forward, there's no immediate forcing function to move.
For anyone building new, or uncomfortable depending on a project with no active team behind it, moving the workflow logic to n8n and pairing it with a Managed Widget replaces both the "brain" and the front end with actively maintained pieces — proxy, security controls, and analytics included from day one rather than something you configure per-chatflow on a platform that's no longer being developed.
Skip the trade-offs — build with N8N Chat UI
Start free with 100 credits, no card required. A secure, branded chat widget for your n8n workflow, live in minutes.