メインコンテンツへスキップ

Planned purchases

After onboarding, purchase plans refresh automatically as usage, portfolio, and pricing signals change. Instead of one large purchase, PerfectScale for Commitments builds a commitment ladder, a sequence of incremental purchases spread over time. This approach maximizes savings while reducing the risk of over-commitment.

Required permissions

  • To view planned purchases: PerfectScale Commitments Read Only or PerfectScale Commitments Admin permission.

  • To change purchase state: PerfectScale Commitments Admin permission.

Understand laddering

Laddering is a risk-mitigation strategy where commitments are purchased in smaller, staggered chunks with different start and end dates, rather than one large lump sum. This creates a "ladder" of overlapping commitments.

Key principles of laddering commitments:

  • Smaller commitments do not lock you into a massive spend if your workload decreases.

  • Commitments expire gradually and avoid "renewal shock" where a large portion of your coverage drops overnight.

  • Each step of the ladder is an opportunity to re-evaluate your usage and optimize the next purchase.

Before every purchase step, the system re-evaluates your current usage.

  • If a dip is detected, PerfectScale pauses or reduces the size of the next purchase to prevent locking you into unneeded commitments.

  • When eligible spend drops significantly week over week, PerfectScale places the next purchase on hold to avoid over-committing. Once usage stabilizes, the laddering plan is re-evaluated and purchasing resumes automatically.

View planned purchases

The Planned Purchases page shows the commitment ladder that PerfectScale has generated based on your current commitment policy.

Planned Purchases tab - Ladder

  • The page header shows an Auto-updated indicator when the purchase ladder is refreshed automatically.

  • Summary at the top shows Recommended Commitment and Current Commitment ($/h). A ladder chart visualizes each scheduled step; hover over a bar to see the cumulative commitment at that point.

The chart highlights the No Purchase Window: the shaded period at the end of each month when new purchases are not scheduled, based on your Latest monthly purchase date in Settings. When a Commitment ceiling is configured, a dashed Commitment ceiling reference line appears on the chart at that $/h value. If the ceiling constrains the laddering plan, the chart tooltip includes a note explaining the cap.

On Google Cloud, when the Cloud SQL tab is selected and the billing account has Cloud SQL projections in more than one region, a region tab bar appears above the ladder chart. Select a region tab to view the commitment ladder and laddering policy summary for that region. When both Compute and Cloud SQL have active purchase steps, the page shows their commitment ladder charts side by side.

When a week-over-week drop in eligible spend triggers a purchasing hold, the chart also shows a gray Purchasing on hold band with dashed boundaries, marking the held planning cycle. This band is visually distinct from the amber No Purchase Window band. A Purchasing on hold chip appears next to the commitment type icon in the chart header. Hover over the chip to see the previous and current weekly eligible spend and the next evaluation date.

  • Purchase Steps ($/h): The commitment amount added at each step.

  • Commitment Term: 1 Year or 3 Years.

  • Max Single Purchase (% of total): The ceiling on how large any single step can be.

  • Prepayment Option (AWS only): No Upfront spreads the full cost across monthly payments with no money due at purchase. Partial Upfront requires at least half the total cost upfront and bills the rest monthly, in exchange for a lower rate. All Upfront charges the entire amount at purchase and offers the deepest discount. For more information, see AWS Savings Plans FAQ.

    Google Cloud CUDs do not have a prepayment option; they are always billed monthly (equivalent to No Upfront), so the Payment Option column and Prepayment Option setting do not appear for Google Cloud accounts.

  • Recommended Commitment ($/h): The target commitment the ladder is building toward.

  • Commitment ceiling ($/h): The configured maximum commitment value, or No Limit if no ceiling is set. This corresponds to the Commitment ceiling field in Settings.

  • Total Laddering Cost ($/h): The cumulative commitment cost once all steps are complete.

The Scheduled purchases table below the chart lists every step with its purchase date, commitment type, commitment amount, days until purchase, current status, and potential monthly savings. On AWS, rows also include payment option. When multiple commitment types are enabled, each row shows an icon indicating the commitment type for that step. On Google Cloud, when a commitment type with regional scope (such as Cloud SQL) is active, a Region column appears showing the target region for each purchase step.

Planned Purchases tab - Schedule purchases

When a week-over-week spend drop triggers a purchasing hold, the first scheduled step displays a Purchasing on hold status chip. Hover over the info icon on the chip to see the spend values that triggered the hold and the next evaluation date. If you manually pause purchases, the paused status takes precedence over the automatic hold.

Google Cloud read-only access

If your Google Cloud organization's Cloud Connect connection has only read access, a banner on this tab states that CUD purchasing is disabled, and the Approve Target Commitment and Manage actions stay disabled until you grant write access in Cloud Connect.

Your next step depends on your Commitment Execution settings.

Requires Approval

When you approve purchases, you allow PerfectScale to buy commitments one step at a time, following the laddering plan, up to the ladder's ending hourly total (Total Laddering Cost, $/h) at the time of approval. The next purchase runs automatically only if it keeps your cumulative hourly commitment within that approved total. If the next purchase would push you above this amount, that step waits until you approve the higher cost.

To approve purchases:

  1. Look for the orange dot on the commitment type tab or Planned Purchases in the sidebar. This indicates a new plan is waiting for your approval.

  2. At the top of the Planned Purchases tab, select Approve Target Commitment $X/h to open the approval dialog. The amount is the recommended target commitment rate.

  3. Review the Approve target commitment dialog, which summarizes what you are approving. When you have multiple commitment types enabled, the dialog shows a row for each type with an aggregated total:

    • Total Recommended Commitment (you are approving this rate): The target hourly commitment ($/h) the ladder is building toward. If you previously approved a lower rate, the dialog also shows Previously approved.

    • Current Commitment (Inventory): Your existing active commitment at the time of approval.

    • Purchase Steps: The number of individual purchases that will be scheduled.

    • Potential Savings (may change): Estimated monthly savings once the ladder is complete.

    A commitment breakdown bar visualizes the proportion of your current inventory versus new purchases for each commitment type.

    For Cloud SQL entries, a Region column appears showing the target region for each commitment.

  4. Select Approve Target Commitment $X/h to confirm. The status updates to green and the orange dot disappears.

注意

After approval, scheduled purchases execute automatically on their dates. You can pause at any time. On AWS, when a commitment plan expires, coverage can be renewed through laddering based on your Recommended Commitment at that time.

Autonomous Execution

In Autonomous Execution mode, PerfectScale sets commitment targets and purchases ladder steps automatically based on your commitment policy and eligible usage. You do not approve each target.

Use Planned Purchases to monitor the ladder and scheduled steps, confirm that your guardrails still match your risk tolerance, or pause purchases when you need to stop new commitments temporarily.

Purchases remain binding once completed. Switch back to Requires Approval in Commitment Execution if you want PerfectScale to wait for approval before future purchases.

Notifications

PerfectScale for Commitments notifications are enabled by default. You receive a notification each time PerfectScale completes a commitment purchase. As each scheduled step is its own purchase, you receive one notification per ladder step.

In Requires Approval mode, you are also notified when purchases need approval. Approval notifications do not apply in Autonomous Execution mode. You can change these preferences in notification settings.

Pause and resume purchases

You can pause execution at any time in either automation mode, for example, due to an upcoming workload migration, or a decommission that will reduce eligible usage. Pausing prevents new commitments from being purchased while you review the situation.

Pause and resume apply at the cloud provider and commitment type (product) level for the account you are viewing (for example, AWS Compute or Database, or Google Cloud Compute or Cloud SQL), not across every type at once. For Cloud SQL, the action is also scoped to the selected region. Confirm you are on the correct commitment type tab before pausing.

To pause, open Manage Purchases in the header of the Planned Purchases tab, then select Pause Purchases. In the dialog, optionally enter a note explaining the reason. The note is saved and visible in the scheduled purchases table. Select Pause to confirm. All remaining scheduled purchases for that type are stopped immediately.

To resume, open Manage Purchases and select Resume Purchases. PerfectScale continues from the next scheduled step for that type, executing remaining purchases on their original dates. In Requires Approval mode, purchasing continues within your previously approved target. In Autonomous Execution mode, purchasing continues toward the current recommended target within your guardrails.

注意

Purchasing on hold is separate from a manual pause. A hold is triggered automatically when eligible spend drops week over week and resolves on its own once usage stabilizes. A manual pause, set through Manage Purchases, stops all remaining purchases until you explicitly resume. If both conditions apply at the same time, the manual pause takes precedence.