Flowise

Flowise puts agent building on a canvas, where nodes are connected into agentflows and the result runs as an application you host yourself. Getting started is a global npm package and a start command on Node 20 or later, with Docker Compose or a locally built image as the alternatives.

The repository is a monorepo whose parts make the extension points clear.

• Server: the Node backend that serves the API logic.
• UI: the React frontend where flows are assembled.
• Components: the third-party node integrations.
• API documentation: Swagger interface docs generated from the Express routes.

Configuration goes through environment variables in a file inside the server package, and a development build reloads the running app whenever code changes. Self-hosting guides cover AWS, Azure, Google Cloud, DigitalOcean and Alibaba Cloud, along with Railway, Northflank and Render, while Flowise Cloud exists for teams that would rather not operate it.

One caveat matters before adopting it: the repository has been archived, and the README points readers to a discussion about the future of Flowise.

Licensing is split. Most of the code is Apache 2.0, third-party components keep their own terms, and an enterprise directory inside the server package is covered by a commercial license instead.