Skip to content

Github · GitHub Repository Radar

FlowiseAI Flowise

Build AI Agents, Visually

Stars

55

Inactive

Forks

24,972

Watchers: 55,405

Repository Radar Score

48 / 100

Growth

7d
+0
30d
+0
%
0.0%

Not enough metric snapshots yet to chart growth for this repository.

Last observed: 2 weeks ago

Score breakdown

  • popularity 48
  • growth 0
  • activity 75
  • freshness 100
  • community 90

Need help integrating this stack?

Our team builds with modern open-source stacks. Tell us what you are shipping.

Get a quote →

Flowise has been archived. Refer to [Future of Flowise](#6727)

Build AI Agents, Visually

📚 Table of Contents

⚡Quick Start

Download and Install NodeJS >= 20.0.0

  1. Install Flowise

    npm install -g flowise
  2. Start Flowise

    npx flowise start
  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:

    docker build --no-cache -t flowise .
  2. Run image:

    docker run -d --name flowise -p 3000:3000 flowise
  3. Stop image:

    docker stop flowise

👨‍💻 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
    npm i -g pnpm

Setup

  1. Clone the repository:

    git clone https://github.com/FlowiseAI/Flowise.git
  2. Go into repository folder:

    cd Flowise
  3. Install all dependencies of all modules:

    pnpm install
  4. Build all the code:

    pnpm build
    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:
    # macOS / Linux / Git Bash
    export NODE_OPTIONS="--max-old-space-size=4096"
    
    # Windows PowerShell
    $env:NODE_OPTIONS="--max-old-space-size=4096"
    
    # Windows CMD
    set NODE_OPTIONS=--max-old-space-size=4096

    Then run:

    pnpm build
  5. Start the app:

    pnpm start

    You can now access the app on http://localhost:3000

  6. For development build:

    • Create .env file and specify the VITE_PORT (refer to .env.example) in packages/ui

    • Create .env file and specify the PORT (refer to .env.example) in packages/server

    • Run:

      pnpm dev

    Any code changes will reload the app automatically on http://localhost:8080

🌱 Env Variables

Flowise supports different environment variables to configure your instance. You can specify the following variables in the .env file inside packages/server folder. Read more

📖 Documentation

You can view the Flowise Docs here

🌐 Self Host

Deploy Flowise self-hosted in your existing infrastructure, we support various deployments

☁️ Flowise Cloud

Get Started with Flowise Cloud.

🙋 Support

Feel free to ask any questions, raise problems, and request new features in Discussion.

🙌 Contributing

Thanks go to these awesome contributors



See Contributing Guide. Reach out to us at Discord if you have any questions or issues.

Star History Chart

📄 License

Source code in this repository is made available under the Apache License Version 2.0.

Created: Mar 31, 2023

Last push: Aug 13, 2026

Default branch: main

Latest release: flowise@3.1.4

Languages

Share of the codebase by language, based on repository metadata from the host.

  • TypeScript 61.8%
  • JavaScript 27.3%
  • HTML 5.6%
  • Handlebars 5.0%
  • CSS 0.2%
  • SCSS 0.1%
  • Dockerfile 0.0%
  • Shell 0.0%
  • Batchfile 0.0%

Repository Radar analysis

Deterministic insights derived from public metadata and our observations — not personal testing or reviews.

Why this repository is interesting

  • Listed in our discovery index with public GitHub metadata for analysis.

Who should use it

  • Developers working primarily with TypeScript
  • Teams exploring AI tooling, agents, or ML infrastructure
  • Platform and DevOps engineers
  • Frontend engineers comparing UI frameworks and tools

Potential use cases

  • Reference or evaluate TypeScript open-source approaches in this domain
  • Prototype AI/agent workflows or study reference architectures
  • Evaluate automation, CI/CD, or infrastructure patterns

Strengths

  • README present in our index
  • Declared license: Other
  • Substantial fork count (24,972) suggests reuse and contribution interest

Limitations / considerations

  • Marked archived on the host — treat as historical unless revived

What to watch

  • Archived status

Source: GitHub (public metadata) + Repository Radar analysis. We do not claim ownership of third-party repositories.

Ready to ship something that compounds?

Share your roadmap. We’ll come back with scope options, timeline ranges, and who from Shriram IT Ventures should be in the room.

Popular with product teams