AIHostBox
Client area Deploy an app
All 57 applications
CategoriesAI assistants & chatLLM runtimesAgents & RAGGateways & LLM opsVector & dataAutomationSpeech, image & videoSearch & web agentsSupport & CXML platformMCP servers
SolutionsPrivate team chatUnlimited automationCompany knowledge AIAI gateway & observability
More PricingGuides ComparisonsToolsPrivate LLM hosting LicensingSecurity SupportClient area

Flowise hosting

Drag-and-drop LLM flows, agents and chatbots you can embed anywhere.

Agents & RAGApache-2.0from $11.99/mo
In short

Flowise hosting at AIHostBox means a dedicated, single-tenant Flowise instance on our infrastructure: we install it, pin it to a reviewed release, put it behind TLS on your domain, back it up nightly and keep it patched. Plans start at $11.99 per month and the admin account, the data and any API keys are yours.

Visual canvasAgentsEmbeddable widgetAPIVector storesTools

Flowise turns LangChain-style building blocks into a canvas: connect a document loader to a splitter, an embedding model and a vector store, drop an LLM node on the end, and you have a RAG chatbot with an API and an embeddable widget. It is the fastest way to get a working prototype in front of someone who needs to see it before they believe it.

One operational note we take seriously: Flowise instances are internet-facing and earlier releases carried a critical remote code execution advisory (CVE-2025-59528, fixed in 3.0.6). We never deploy below the fixed release, we keep instances pinned to a reviewed version, and authentication is on from the first boot.

Flowise hosting plans

PlusRecommended minimum
4 GB RAM · 2 vCPU · NVMe
$11.99/mo
Order
ProTeams & heavier load
8 GB RAM · 3 vCPU · NVMe
$18.99/mo
Order

Every plan is a dedicated single-tenant instance with NVMe storage, nightly off-box backups, TLS and managed patching. Quarterly, semi-annual and annual terms are discounted at checkout. Model tokens are not included — you bring your own key.

How we run Flowise

The Flowise Node.js server on port 3000 with its database (SQLite by default, Postgres on request), local blob storage for uploads, and optional Redis plus a worker when queue mode is needed.

What we configure for you

  • Pinned to a reviewed 3.x release at or above 3.0.6
  • JWT_AUTH_TOKEN_SECRET, JWT_REFRESH_TOKEN_SECRET and EXPRESS_SESSION_SECRET generated per instance
  • Credential encryption key via SECRETKEY_PATH on persistent storage
  • APP_URL and SMTP_* settings so invitations and password resets work
  • STORAGE_TYPE local or s3 for uploaded documents
  • MODE=queue with REDIS_URL and a worker on busy instances

Which plan fits

Plus (4 GB) is right for building flows and serving a chatbot to a site with modest traffic. Pro (8 GB) suits a team building several flows at once, larger in-memory document processing, or queue mode with a separate worker.

The honest limits

SSO, workspaces with role-based access and audit logs belong to Flowise Enterprise and are not in the open-source build we host. Flowise orchestrates models; the LLM and embeddings come from your key or another plan.

What people run Flowise for

Website chatbot

Build the flow, embed the widget, keep the data on your instance.

Internal RAG prototype

Prove the retrieval idea before anyone writes production code.

Tool-using agent

Give a model access to APIs and let it decide when to call them.

Licence and version policy

ItemPosition
Upstream licenceApache-2.0
Sold as managed hostingYes
TenancySingle tenant — one customer per instance
PatchingCritical advisories within 24 hours, high severity within 72

Our full position on licences, including the applications we decline to sell, is on the licensing page.

Reading on Flowise

Comparisonn8n alternatives you can host commerciallyComparisonDify vs Flowise vs Langflow

Works well with Flowise

Qdrant logo

Qdrant

A fast vector database with real filtering, written in Rust.

from $5.99/moDetails →Ollama logo

Ollama

Your private LLM server — pull a model, get an API, keep every token on your own box.

from $16.99/moDetails →LiteLLM logo

LiteLLM

One OpenAI-compatible endpoint in front of every model provider you use.

from $5.99/moDetails →Crawl4AI logo

Crawl4AI

A crawler that returns clean Markdown instead of raw HTML.

from $11.99/moDetails →

More Agents & RAG we host

Dify logo

Dify

A visual studio for building LLM apps, agents and RAG pipelines.

from $18.99/moDetails →Langflow logo

Langflow

A visual builder for LangChain flows and multi-agent systems.

from $11.99/moDetails →AnythingLLM logo

AnythingLLM

A private document workspace — drop files in, ask questions, get cited answers.

from $18.99/moDetails →RAGFlow logo

RAGFlow

Deep document understanding for RAG — tables, layouts and scanned pages.

from $36.99/moDetails →
Questions

Flowise hosting: your questions

Is Flowise safe to run on the public internet?
With the right version and authentication, yes. We pin instances to 3.0.6 or newer because earlier builds carry a critical remote code execution advisory (CVE-2025-59528), enable authentication by default, and patch on the schedule published on our security page.
How is it different from Dify?
Flowise is lighter and canvas-first; Dify is a fuller platform with datasets, workspaces and app management. Flowise wins on time-to-prototype, Dify on running something long-term.
Where does Flowise keep my flows and credentials?
In its database — SQLite by default, or Postgres/MySQL via DATABASE_TYPE — with third-party API keys stored as encrypted credentials. The encryption key sits in a separate secret file. Both are in the nightly backup; restore the database without that key and saved credentials cannot be decrypted.
How does login work in Flowise 3?
From 3.0.1 Flowise uses its own email and password accounts with JWT sessions instead of the old FLOWISE_USERNAME/FLOWISE_PASSWORD pair. We create the admin account at setup. Single sign-on through OIDC is part of Flowise Enterprise, not the open-source edition.
Can I import flows from another Flowise install?
Yes. Export chatflows or agentflows as JSON from your current instance and load them on the canvas here. Credentials are not included in exports, so you re-enter API keys once. For a full move we can migrate the database file and encryption key together.
What happens when many people use the chatbot at once?
By default one Flowise process handles every prediction. For heavier traffic Flowise has a queue mode (MODE=queue) where the main server hands jobs to workers through Redis. On Pro we can run it that way if a public widget starts to queue up.

Run Flowise without running a server

A dedicated Flowise instance, deployed and maintained by us. Month to month, cancel whenever.

Browse the catalogue Talk to a human