Flowise · Rate Limits

Flowise Rate Limits

Rate limit definitions for Flowise. Self-hosted Flowise has no built-in request-rate limits beyond what the operator configures (the enterprise build adds per-route rate limiting and restricted domains). Flowise Cloud enforces monthly prediction quotas per plan. Scaffold values reflect the publicly-documented per-tier prediction caps; per-minute caps are listed as scaffold defaults and should be reconciled with the operator's deployed configuration.

Flowise Rate Limits is the machine-readable rate-limit profile for Flowise on the APIs.io network, in the API Commons Rate Limits shape.

It captures 5 rate-limit definitions, across the free, starter, pro, enterprise, and self-hosted tiers, measuring predictions_per_month and requests_per_minute.

Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Agents, Agent Workflows, Artificial Intelligence, Large Language Models, and Rate Limiting.

5 Limits Exhausted: HTTP 429 Quota: 429 limitremainingresetretryAfter
Method: generated, dated 2026-05-24.
Written by API Evangelist on 2026-05-24 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
AgentsAgent WorkflowsArtificial IntelligenceLarge Language ModelsRate LimitingQuotasThrottling

Limits

Free Tier Predictions workspace
predictions_per_month · month
100
Starter Tier Predictions workspace
predictions_per_month · month
10000
Pro Tier Predictions workspace
predictions_per_month · month
50000
Enterprise Negotiated Predictions contract
predictions_per_month · month
-1
Self-Hosted Default instance
requests_per_minute · minute
-1
Self-hosted Flowise does not enforce request-rate limits by default. The Enterprise build supports configurable per-route rate limiting.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and respect Retry-After headers when returned.
Quota Reset
Cloud prediction quotas reset at the start of the workspace's billing cycle.
Enterprise Rate Limiting
Operators of the Flowise Enterprise build can configure per-route rate limiting and restricted domains, exposed in the admin configuration.
Horizontal Scaling
For high-throughput deployments, Flowise supports horizontal scaling via BullMQ workers and a message-queue backplane.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/flowise-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.