ClaraVerse vs Flowise
Self-hosted private AI workspace: chat, multi-agent crews with human review, a visual workflow builder and Telegram integration in one app — local models via Ollama/llama.cpp or your own keys. — versus — The 55k-star visual builder for LLM apps and agents — drag-and-drop chatflows and Agentflows, hundreds of nodes, self-hostable Node.js. Now ARCHIVED upstream (see 'Future of Flowise').
Self-hosted workspace with a visual workflow builder and agent crews; a fit for hobby/self-host users who chose Flowise for its no-code UI.
| ClaraVerse | Flowise | |
|---|---|---|
| Stars | 3.9k | 55k |
| Forks | 437 | 25k |
| Language | TypeScript | TypeScript |
| License | NOASSERTION | NOASSERTION |
| Last activity | 1 months ago | 29 days ago |
| Topics | local, agents | orchestration, agents |
| Curated connections | 4 | 5 |
ClaraVerse — the curator's take
The integration is the pitch: where a homelab stitches chat + n8n + agent runner, ClaraVerse is one AGPL app with crews, memory and workflows designed together — and it auto-detects Ollama/LM Studio with zero config. When NOT: one app means one surface to trust and its pace to accept; GitHub metadata says NOASSERTION while the README badges AGPL-3.0 — check LICENSE in the release you deploy; power users who want best-of-breed parts will feel boxed in.
Flowise — the curator's take
Flowise is the reference example of the visual-agent-builder category and still runs fine self-hosted, which is the only reason to reach for it today: the repo has been archived and development has stopped, so treat it as frozen. If you are starting new, go to sim or bytechef for the same drag-and-drop model with active maintenance, or to maxkb/claraverse if the RAG/chat-app angle matters more than the canvas. Existing Flowise deployments: plan the migration rather than extending them; the node ecosystem (LangChain/LlamaIndex bindings) will drift out of date quickly. Listed for lineage and for the many teams who still run it.