Polyer

Flowise

Deploy Flowise on Polyer to build LLM orchestration flows, chatbots and AI agents in a visual low-code editor. The template runs one public Flowise service; its SQLite database, encryption key, uploads and logs are stored on a volume at /root/.flowise. Review the generated credentials and the floating latest tag.

AI applicationsCoolify open catalog

What you can use it for

  • Prototype a retrieval-augmented chatbot that answers questions from your own documents.
  • Build an agent flow and call it from your application through the Flowise API.

What this template creates

flowiseflowiseai/flowise:3.1.3
Public endpoint Persistent volume

Configuration to review

This template has no additional declared inputs. Review the generated variables, endpoints and resource settings in the deployment form.

How to deploy

  1. Select Configure deployment and sign in or create an account.
  2. Choose a new or existing project and select an available region.
  3. Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
  4. Inspect deployment logs, complete the application's setup and test its endpoints before production use.

Operating this application

  • Set up the Flowise admin account once the service is reachable; current releases first ask for the generated FLOWISE_USERNAME and FLOWISE_PASSWORD values to confirm ownership.
  • Back up the whole /root/.flowise volume together, since stored credentials can only be decrypted with the encryption key saved alongside the database.
  • The flowiseai/flowise:latest tag can pull a newer release on redeploy, so pin a version or read the release notes and back up first. Model provider API keys and inference charges are separate from hosting.

Hosting costs

CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.

Review prices and estimate resource costs

Source and validation

This deployment configuration comes from Coolify's Apache-2.0 licensed open template collection and is adapted through Polyer's compose importer.

Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.

Editorial content reviewed: 2026-10-10

Upstream documentation Template source and license

Choose your next step

Related templates