Flowise is by FlowiseAI — not by us.
We indexed this project so people can find it. We are not selling it, we host no copy of the code, and we are not affiliated with or endorsed by its authors — get it from them.
The core of this project is Apache-2.0-licensed (detected from the license text; GitHub could not classify it automatically) and free to use. A separate portion is commercially licensed by the publisher — from the upstream license: "Portions of this software are licensed as follows". Read the upstream LICENSE before relying on any enterprise feature.
We flag this because a repository page rarely makes the boundary obvious — you often find out which features are paid only after building on them.
Indexed Aug 1, 2026 · 55,074 stars at index time. Maintainers: claiming verifies your identity and unlocks a higher assurance tier. Removal requests are honored.
Flowise
Build AI Agents, Visually
by Open Source Community · New publisher
Build AI Agents, Visually
**FlowiseAI/Flowise** is an open-source project by FlowiseAI: Build AI Agents, Visually. Indexed here so it can be found — not resold.
It is free. Get it from the upstream repository: https://github.com/FlowiseAI/Flowise
From the project's own README (excerpt, reproduced for discovery under its null license):
English 繁體中文 简体中文 日本語 한국어
Build AI Agents, Visually
📚 Table of Contents • ⚡ Quick Start • 🐳 Docker • 👨💻 Developers • 🌱 Env Variables • 📖 Documentation • 🌐 Self Host • ☁️ Flowise Cloud • 🙋 Support • 🙌 Contributing • 📄 License
⚡Quick Start
Download and Install NodeJS >= 20.0.0
1. Install Flowise 2. Start Flowise
3. Open http://localhost:3000
🐳 Docker
Docker Compose
1. Clone the Flowise project 2. Go to docker folder at the root of the project 3. Copy .env.example file, paste it into the same location, and rename to .env file 4. docker compose up -d 5. Open http://localhost:3000 6. You can bring the containers down by docker compose stop
Docker Image
1. Build the image locally:
2. Run image:
3. Stop image:
👨💻 Developers
Flowise has 3 different modules in a single mono repository. • server: Node backend to serve API logics • ui: React frontend • components: Third-party nodes integrations • api-documentation: Auto-generated swagger-ui API docs from express
Prerequisite • Install PNPM
Setup
1. Clone the repository:
2. Go into repository folder:
3. Install all dependencies of all modules:
4. Build all the code:
Exit code 134 (JavaScript heap out of memory) If you get this error when running the above build script, try increasing the Node.js heap size and run the script again:
Then run:
5. Start the app:
You can now access the app on http://localhost:3000
6. For development build: • Create .env file and specify the VITEPORT (refer to .env.example) in packages/ui • Create .env file and specify the PORT (refer to .env.example) in packages/server • Run:
Any code changes will reload the app automatically on http://localhost:8080
🌱 Env Variables
Flowise supports different…
Preview
See what it does before you commit. Previews show behavior, never source code.
Capabilities
Requirements & stack
Depends on
- → PostgreSQL database
- → Authentication
- → Programmatic API
Credentials needed
None declared
Stack
Companions & conflicts
- None declared
Community
No endorsements yetEndorsements come from verified purchasers and vetted trusted reviewers, weighted by standing. They grade quality and trustworthiness — security is verified separately and community votes can never override the security gate.
Sign in with a verified purchase to endorse.
Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
This listing is unclaimed, so publisher identity cannot be verified and it stays below the “verified” tier by design — that is a statement about the listing, not about the project’s quality. Our automated scans still ran; a maintainer who claims it unlocks identity verification.
- publisher identity Publisher status verified; 0 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns detected in reviewed content
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 0.0.0 | stable | Aug 1, 2026 | Indexed listing — see the upstream repository for real release history. |
Similar products
Nearest matches by capability and description — not curated alternatives.