Cloud limits and expectations

Plan, fair use, builds, and support expectations for dFlow Cloud vs self-hosted control planes.

Written By Zoro

Last updated 3 days ago

dFlow Cloud limits & overview

dFlow Cloud hosts the control plane; Worker Nodes (yours or managed) run Services. Limits therefore come from your plan, provider APIs, and the capacity attached to Environments, not from a single universal quota table in docs. Use this page to set expectations and know where to look next.

What is covered here vs self-hosting

Topic	dFlow Cloud	Self-hosting control plane
Dashboard availability	dFlow operates app.dflow.sh	You operate the stack; see Self-hosting overview under Self-Hosting dFlow in the sidebar
Workload CPU / RAM	Your Worker Nodes or managed compute	Same model; you supply or buy compute
Build concurrency	Plan and fair-use policies on the service	Depends on your hardware and configuration

Plan and organisation

Features (managed compute regions, seats, advanced integrations) depend on the subscription shown in Billing.
Organisation boundaries define who sees Applications and Environments; see Organisations and tenants under Core Concepts in the sidebar.
Legacy Projects may coexist with Applications during migration; see Legacy Projects vs Applications under Core Concepts in the sidebar.

Builds, Git, and APIs

Builds compete for shared infrastructure on the cloud control plane; very large queues or repeated failures may be throttled or require support.
Git providers apply their own rate limits; heavy webhook or API usage can slow clones or status updates.
The product may enforce reasonable automation limits on API or UI actions to protect the platform.

Data and retention

Logs and deployment history visibility may be time-bounded or plan-bounded; export anything you must keep long term.
Backups of Service data are your responsibility unless a specific dFlow feature states otherwise for your plan; start from Backups under Core Concepts in the sidebar.

Support and status

Use in-app support or your account channel for plan-specific limits and temporary raises.
Operational incidents are communicated through dFlow’s normal status and communication channels (follow whatever link or email your organisation uses).

If you hit a limit

Check Billing for the active plan and upgrade path: Billing overview under Billing and Account in the sidebar.
Review Worker Node health and size: Worker Nodes overview under Worker Nodes and Compute in the sidebar.
For Git errors, confirm integration scopes: Integrations overview under Integrations in the sidebar.