Feature access and limits
How plan limits map to Applications, databases, and Worker Nodes on dFlow Cloud.
Written By Zoro
Last updated 11 days ago
Plan limits
Plan limits are configured per plan record in the product. They gate how much included capacity you have before you need add-ons or a higher tier. Limits are numeric; feature names and marketing copy on the Plans page may use different wording.
Limit fields (reference)
Your effective limits are the maximum of what the plan grants and what you purchase through add-ons. If something is blocked, check both Plans and Cloud limits and expectations under dFlow Cloud in the sidebar.
Plan level
Plans use an internal plan level number for ordering and eligibility. Higher levels unlock more capability in the product rules. You do not need the number day to day; use the Plans screen to compare.
Disabled plans
Plans marked disabled in admin are not offered for new subscriptions. Existing subscribers may remain on retired plans until they change tier; follow in-app notices and support guidance.
Where to see your effective access
- Profile → Plans for tier, add-ons, and upgrade paths.
- Workspace views for Applications, Environments, and Services (see How dFlow is structured under Core Concepts in the sidebar).
- Worker Nodes overview under Worker Nodes and Compute in the sidebar for attach and purchase flows.
When usage is above the plan
If team members or custom worker nodes are above your plan, dFlow emails you before that extra access changes. Usage is above your plan gives the date the extra access stays available. Upgrade before that date to keep it. After the date, Access is now restricted means the extra team-member or custom worker node access is restricted. Custom worker nodes and their data are not deleted. Upgrade from Profile → Plans to restore access.
Related
Was this helpful?
More in Billing and Account
Billing overviewPayment methodsTransactions and invoicesUsage and billing behaviorStill need help? Ask the team