> ## Documentation Index > Fetch the complete documentation index at: https://docs.cubic.dev/llms.txt > Use this file to discover all available pages before exploring further. # Flex capacity > How cubic bills extra reviewed-line capacity after your included usage runs out. Flex capacity keeps GitHub PR AI reviews running after your workspace uses its included reviewed-line capacity. You set a monthly spend limit, and cubic buys extra reviewed-line capacity only when a review would otherwise be paused. Flex capacity is available on paid workspaces billed through Stripe. Admins manage it in **Settings → Subscription** by setting a monthly spend limit. ## How flex capacity works Flex capacity turns a reviewed-line usage block into an automatic one-off charge: 1. Your workspace uses its included reviewed-line capacity for the billing period. 2. A new GitHub PR review would otherwise pause because the workspace is over its monthly limit. 3. cubic checks your flex capacity setting and monthly spend limit. 4. If the needed capacity fits under your spend limit, cubic charges the saved payment method immediately. 5. After payment succeeds, cubic adds the extra reviewed-line capacity for the current billing period and continues the review. Flex capacity applies only to GitHub PR AI review usage. CLI/local reviews, codebase scans, daily scans, wikis, and cubic coding agents use separate limits. ## Pricing Flex capacity costs **\$20 per 10,000 extra reviewed lines**. | Item | Amount | | -------------- | ------------------------------------------- | | Block size | 10,000 extra reviewed lines | | Price | \$20 per block | | Billing timing | Charged immediately when capacity is needed | | Availability | Current billing period only | The price is the same for Team and Pro workspaces, and the same for monthly and annual subscriptions. Flex capacity is separate from your seat subscription; it appears as a one-off invoice charge when cubic adds capacity. ## Example charges Flex capacity is bought in whole \$20 blocks. cubic buys enough blocks to cover the current overage, and it never buys a partial block. | Current overage | Blocks bought | Charge | Extra capacity granted | | --------------------- | ------------- | ------ | ---------------------- | | 4,000 reviewed lines | 1 block | \$20 | 10,000 reviewed lines | | 15,000 reviewed lines | 2 blocks | \$40 | 20,000 reviewed lines | | 30,000 reviewed lines | 3 blocks | \$60 | 30,000 reviewed lines | If a review is 15,000 reviewed lines over the included limit, cubic needs two blocks. If your remaining monthly flex spend limit is only \$20, cubic does not buy one block because that would charge you without unblocking the review. ## Spend limits A monthly spend limit is the most cubic can spend on flex capacity during one billing period. The setting is a hard stop: reviews can continue while the needed flex purchase fits under the limit, and reviews pause once the next needed purchase would exceed the limit. For example, a $60 monthly spend limit can buy up to 30,000 extra reviewed lines during the current billing period. If your workspace has already spent $40 and the next review needs two more blocks, cubic will not charge $40 and reviews will stay paused because that would exceed the $60 limit. Admins can set, raise, lower, or remove the spend limit from **Settings → Subscription → Flex capacity**. Removing the spend limit turns flex capacity off for future purchases. Extra capacity already bought during the billing period remains available until the period ends. ## Payment behavior Flex capacity is granted only after payment succeeds. If the payment method is declined, cubic does not grant the extra capacity and reviews stay paused at the current limit. Some cards require extra authentication, such as 3D Secure. When that happens, cubic emails workspace admins with a secure Stripe invoice link. The extra capacity is granted after the payment is confirmed. A failed flex capacity payment stops additional automatic flex purchase attempts for the same billing period. Update the payment method in billing settings to resume automatic flex capacity. ## How to turn it on Admins can enable flex capacity from the subscription settings: 1. Open **Settings → Subscription**. 2. Find **Flex capacity**. 3. Select **Set a spend limit**. 4. Enter a monthly dollar amount in \$10 increments. 5. Save the limit. The setting takes effect for future reviews. If reviews are already paused because your workspace is over the reviewed-line limit, setting a limit can let cubic buy the needed extra capacity and resume reviews. ## How to monitor usage Open **Settings → Usage** to see your reviewed-line usage, reset date, and flex capacity spend for the current billing period. The subscription page also shows flex spend, the monthly limit, and how many extra reviewed lines were bought this period. Flex capacity resets with your billing period. Unused extra capacity does not roll over. ## FAQ No. Seats still determine your included reviewed-line allowance and who has paid AI review access. Flex capacity covers temporary overages after your included reviewed-line capacity runs out. No. cubic charges flex capacity only when a review needs extra capacity and the purchase fits under your monthly spend limit. No. The spend limit is a hard cap. If the next required purchase would exceed the limit, cubic buys nothing and reviews stay paused until you raise the limit or the billing period resets. cubic buys whole 10,000-line blocks. A PR that is 10,001 reviewed lines over the limit requires two blocks, because one block would not unblock the review. cubic stops making future flex capacity purchases. Extra capacity already paid for during the current billing period remains available until the period resets. Your included reviewed-line allowance resets, flex spend returns to \$0 for the new period, and any unused extra flex capacity from the previous period expires. Flex capacity applies to your paid workspace's GitHub PR AI review usage. Public repositories may also be subject to separate fair-use and abuse-protection limits, which flex capacity does not override.