Plans and capacity
Supply Chain plans control continuous private-repository monitoring, hosted-scan allowances, and managed policy coverage for one Workspace. Capacity is enforced before new work starts; it does not create a surprise overage charge.
Plan scope
Section titled “Plan scope”The plan belongs to the selected Workspace. Each Workspace has its own effective plan, capacity, usage, trial, and scheduled changes.
The launch catalog includes Free, Team, Scale, and Enterprise. The Control Plane is the source for the current offer, validity dates, scheduled changes, usage, and management options. Public repositories do not consume private-repository capacity.
Each new Workspace receives one card-free 14-day Team trial with Team repository capacity, hosted-scan allowance, and policy coverage. The trial belongs to that Workspace and is not renewed by adding another user or reconnecting GitHub.
Repository capacity
Section titled “Repository capacity”A private or internal repository consumes capacity only when continuous monitoring is selected. Connecting GitHub, discovering a repository, running another scan, or adding a Workspace user does not consume a repository unit.
When capacity is full, existing monitored repositories continue to work and another private or internal repository cannot be selected. The service does not choose repositories to stop monitoring automatically.
Hosted-scan allowance
Section titled “Hosted-scan allowance”Hosted browser, CLI, and Customer API scans use a separate allowance. The plan response shows current usage, remaining capacity, and the reset time. A rejected request does not create paid usage.
Plan changes
Section titled “Plan changes”An upgrade can apply immediately after the billing provider confirms it. A downgrade or cancellation is scheduled for the end of the current paid period. The confirmation explains repository, hosted-scan, and policy effects before the change is submitted.
When paid access or the Team trial ends, private and internal repositories outside the Free entitlement become Not monitored. Existing repositories, findings, and scan history remain available. The Workspace can select monitored repositories again when capacity becomes available.