Plan limits
An empty cell means the limit is unset — there is no cap. A zero in a numeric limit reads the same way: “no limit”, not “nothing allowed”.
| Limit | Free | Paid |
|---|---|---|
Bring-your-own LLM connectionsallow_custom_llm | — | ✓ |
Public chatallow_public_chat | ✓ | ✓ |
White-label brandingallow_white_label | — | ✓ |
Allowed connection kindsallowed_connection_kinds | unset (no limit) | unset (no limit) |
Deploy channelsallowed_deploy_targets | web | web, telegram, webhook, cron |
Allowed modelsallowed_llm_models | unset (no limit) | unset (no limit) |
API requests per minuteapi_rate_per_min | unset (no limit) | unset (no limit) |
Renewal periodcredit_period | month | month |
Credits per periodcredits_included | 100 | 10,000 |
Minimum cron interval, scron_min_interval_seconds | unset (no limit) | 300 |
Collection storagedb_quota_bytes | 100 MB | 10 GB |
Run history retention, daysexecution_retention_days | 7 | 90 |
File storagefiles_quota_bytes | 100 MB | 10 GB |
Knowledge-base storagekb_quota_bytes | 100 MB | 10 GB |
Document collectionsmax_collections | 5 | unset (no limit) |
Concurrent nodes per runmax_concurrent_nodes | 3 | 10 |
Concurrent runsmax_concurrent_workflows | 1 | 20 |
Connectionsmax_connections | 3 | unset (no limit) |
Deployed workflowsmax_deployed_workflows | 1 | unset (no limit) |
Filesmax_files | 100 | unset (no limit) |
Knowledge basesmax_knowledge_bases | 2 | unset (no limit) |
Loop iterationsmax_loop_iterations | unset (no limit) | unset (no limit) |
Members per workspacemax_members_per_workspace | 1 | 10 |
Node executions per runmax_node_executions_per_run | unset (no limit) | unset (no limit) |
Subgraph recursion depthmax_recursion_depth | unset (no limit) | unset (no limit) |
Chat session queue depthmax_session_queue_depth | unset (no limit) | unset (no limit) |
Single upload sizemax_upload_bytes | 10 MB | 1 GB |
Vector pointsmax_vector_points | 50,000 | 5,000,000 |
Run time ceiling, smax_workflow_timeout_seconds | 120 | 900 |
Workflowsmax_workflows | 5 | unset (no limit) |
Workspacesmax_workspaces | 1 | unset (no limit) |
Per-node parameter capsnode_param_caps | unset (no limit) | unset (no limit) |
Node accessnode_types | all but a few | all but a few |
Allow negative credit balanceoverage_allowed | — | ✓ |
Telegram messages per chattelegram_history_max_messages | 500 | 2,000 |
Telegram history retention, daystelegram_history_retention_days | 7 | 30 |
How the limits are applied
- Credits and concurrency are checked when a run is admitted: too low a balance and the run is rejected; a full concurrency quota and it waits in the queue.
- Storage quotas are counted per owner, not per workspace: extra workspaces do not add extra room.
- Deploy channels are checked at deploy time. Free allows the web chat only — unattended triggers are a paid-shaped workload.
- Retention decides how long runs and logs live; after that a background sweep removes them and the UI marks the run as purged.
What next
- Credits and cost — what a run costs.
- Usage — where to see spend and quotas.