GDP Cloud plan and entitlement state can shape hosted usage, admission, capacity, and account-linked limits. Use live Profile and Pricing for current values; Help explains the boundary without freezing future prices, packages, or Desktop and Browser licensing decisions.
Read current plan values from live product surfaces
GDP Cloud has a canonical runtime plan manifest that the hosted billing and admission code can consume for plan dimensions such as gateway usage, queue priority, connected or registered capacity, and other account limits.
Those values can change as the product evolves. Use the current Pricing and GDP Cloud Profile surfaces for the plan, allowance, subscription, and entitlement values that apply to your account instead of relying on numbers copied into a Help article.
This Help page intentionally avoids duplicating current tier prices and numeric limits so an old documentation snapshot cannot silently become the commercial source of truth.
Separate entitlement from execution authority
Hosted entitlement can be an input to GDP Cloud admission, metering, queue priority, reviewer or gateway capacity, and account-linked service availability where those policies are enabled. It answers what hosted service the account is eligible to consume under the current commercial rules.
It does not answer whether a specific repository mutation, terminal command, node route, provider Send, claim, lease, or approval is authorized. Those effects still require the exact GDP target, current policy, fresh authority checks, and execution evidence.
A paid plan is not a repository permission.
A higher queue priority is not a local apply permission.
A registered-device allowance is not proof that a device is currently online or authorized for a specific mutation.
Security limits can block or throttle work independently of commercial plan limits.
Keep current Cloud packaging separate from future product packaging
The repository contains current and historical GDP Cloud tier material as well as an active commercial-distribution review for future customer-facing Desktop and Browser packaging. The current hosted plan manifest is useful operational truth for the Cloud system; it is not, by itself, a permanent promise about future Desktop or Browser pricing, source licensing, membership, or package boundaries.
When commercial packaging changes, the live Pricing/Profile surfaces and an explicitly approved current commercial source should change first. Historical Cloud copy should not be promoted into a broader product promise merely because it still exists in source or documentation history.
Billing, entitlement, license state, and package availability remain separate from GDP's execution-safety model. None of them may bypass target, policy, lease, or evidence requirements.
