FAQ
How does PerfectScale for Commitments differ from Flexsave?
PerfectScale for Commitments is DoiT's customer-owned commitments offering alongside Flexsave for Compute. Flexsave delivers managed savings with minimal operational work, while PerfectScale for Commitments lets you optimize your own commitment strategy using advanced FinOps tools for control, visibility, and automation.
Flexsave applies Savings Plans from DoiT's inventory, so DoiT holds the commitments and carries unused commitment risk. PerfectScale for Commitments purchases commitments in your cloud provider account(s), so you own the commitments and your organization carries unused commitment risk.
Flexsave for Compute is available on AWS only. On Google Cloud, PerfectScale for Commitments is the DoiT path for managing customer-owned Committed Use Discounts (CUDs) with recommendations, laddering, and approvals.
If Flexsave is active, why would I consider self-managed commitments?
Flexsave for Compute is low-effort and DoiT carries unused commitment risk, but customer-owned Savings Plans can deliver deeper discounts when a portion of your AWS spend is stable and predictable. The tradeoff is lock-in: you own the commitment for the 1- or 3-year term.
Use Commitment Simulator to compare self-managed Savings Plan costs against your Flexsave baseline and decide whether the extra savings justify that risk. If you move ahead, PerfectScale for Commitments helps you plan, approve, and ladder purchases over time.
Who owns commitments purchased through PerfectScale for Commitments?
PerfectScale for Commitments purchases commitments in your cloud environment. On AWS, each onboarded payer account has a Commitments purchasing account where Savings Plans for that payer are bought. On Google Cloud, CUDs are purchased on the Cloud Billing account itself. Those commitments are owned by your organization, billed to your payer or billing account, and are not DoiT-owned commitments.
Can I cancel a commitment after purchasing it?
Almost never. Cloud commitments are a long-term obligation: the committed hourly rate is due for the full 1- or 3-year term.
AWS allows Savings Plan returns under strict conditions. The plan must have an hourly commitment of $100 or less, be returned within 7 days of purchase and within the same calendar month, and you have a limit of 10 returns per management account per calendar year. Outside of those conditions, there is no way to reduce or exit a commitment. Google Cloud spend-based CUDs are binding for the selected term. Treat every purchase as a lock-in.
Which cloud providers does PerfectScale for Commitments support?
PerfectScale for Commitments supports AWS and Google Cloud. For details on supported commitments and types, see Supported commitments and types. Azure commitments are on the roadmap.
Does PerfectScale for Commitments purchase commitments for me?
Yes, when configured. After set up, you can review laddered purchase plans in Planned purchases and optionally enable auto-purchase with approval notifications.
How does PerfectScale for Commitments reduce risk?
The platform is built to manage uncertainty. Teams can choose a risk posture (Conservative, Balanced, Max Savings), set commitment ceilings, and use paced buying strategies. Drift detection continuously checks whether actual usage still matches commitments and highlights when action is needed.