On integrating DataHub, the DoiT team was very hands-on to the point where DoiT support put together the first ingestion script and pipeline to unlock us.
Kyle Espinola, Head of Platform Engineering
Google Cloud CUD optimization
Google Cloud CUDs. Without the big bet.
Spend-based CUDs across ten Google Cloud services, from Compute Engine and Cloud SQL to BigQuery Editions, are automatically provisioned in small steps, each checked against hourly usage.
10 Google Cloud services · Spend-based CUDs · Autonomous or approval-based
Google Cloud · CUDs · last 90 days
Effective Savings Rate
29.6%
▲ 6 pts this quarter
Coverage
80%
Utilization
98.8%
CommittedHourly usage
Purchase schedule · laddered
Compute Engine CUDOct 1 · $9/hr · 1 yrExecuted
Cloud SQL CUD · us-central1Oct 15 · $2.4/hr · 1 yrApproved
BigQuery Editions CUDNov 1 · $4/hr · 1 yrAwaiting approval
Next step, if usage holdsNov 15 · sized at the timePlanned
Each step is checked against fresh hourly usage before it executes.
how laddering works
Small steps. No big bets.
Instead of tying your full commitment to one forecast and one maturity date, we ladder CUD purchases and validate each step against fresh Google Cloud usage.
Get a free savings analysisEffective Savings Rate · last 6 months
31.4%, and climbing
18.2%
21.5%
24.9%
27.3%
29.8%
31.4%
Coverage
82%
Utilization
99.1%
Saved this quarter
$412K
One view of ESR, coverage and utilization across clouds.
google cloud services covered
Spend-based CUDs across ten services.
Compute, databases, analytics and messaging, optimized from one laddered plan. Cloud SQL and BigQuery Editions are managed per region; other CUD types apply across regions at the billing-account level. Flexible Spend CUDs for Compute and more Cloud SQL coverage are coming next.
Compute and data processing2 services
Compute Engine
DataflowDatabases6 services
Cloud SQL
AlloyDB
Cloud Spanner
Firestore
Bigtable
MemorystoreAnalytics and messaging2 services
BigQuery Editions
Managed Kafkaother tools push you to buy upfront
We ladder instead.
A large CUD bought on day one assumes Compute Engine, Cloud SQL and BigQuery usage only grows. Laddering keeps every step small and recent, so coverage follows your workloads.
The big bet
“Buy three years of coverage today.”
Based onOne forecast
If usage dropsYou pay anyway
Utilization74% by month 9
PerfectScale for Commitments
“Buy what holds, then buy again.”
Based onHourly usage, every hour
If usage dropsThe next step shrinks
Utilization99.1%
Finance
Approve before money moves.
FinOps
ESR you can report.
Engineering
Scale down without penalty.
Leadership
Savings without lock-in.
the full commitment cycle
Every CUD service type, one system
Ten-service CUD coverage
Compute Engine, Cloud SQL, BigQuery Editions and seven more.
CUD purchase schedules
Coverage gaps turned into measured, reviewable steps.
Purchase impact review
Projected coverage and history before you commit.
Autonomous or approval-based
Choose how purchases execute, with thresholds and limits.
Unified savings view
CUD outcomes next to your AWS commitments.
Compute and Cloud SQL roadmap
Flexible Spend CUDs for Compute in progress, Cloud SQL next.
recommendations within hours
How Google Cloud CUD optimization works
1
Connect your billing.
Link your cloud billing accounts. Usage analysis starts right away.
2
Set your guardrails.
Spend limits, pacing, coverage targets and approval rules.
3
Ladder in.
Purchases execute in small steps, each checked against fresh usage.
SOC 2 Type 2, ISO 27001, FinOps Certified Platform.
Free savings analysisPublic product claims reviewed July 31, 2026. "Not publicly listed" means no vendor support claim was found.
The commitment model matters as much as the CUD
| Capability | PerfectScale | ProsperOps | Opsima | nOps |
|---|---|---|---|---|
| Google Cloud service coverage | ||||
| Compute Engine | Supported | Supported | Not available Opsima lists Google Cloud support as coming. | Publicly listed |
| Cloud SQL | Supported | Early Access | Not available Opsima lists Google Cloud support as coming. | Publicly listed |
| BigQuery Editions | Supported | Not publicly listed | Not available Opsima lists Google Cloud support as coming. | Publicly listed |
| AlloyDB | Supported | Not publicly listed | Not available Opsima lists Google Cloud support as coming. | Publicly listed |
| Cloud Spanner | Supported | Not publicly listed | Not available Opsima lists Google Cloud support as coming. | Publicly listed |
| Cloud Firestore | Supported | Not publicly listed | Not available Opsima lists Google Cloud support as coming. | Publicly listed |
| Dataflow | Supported | Not publicly listed | Not available Opsima lists Google Cloud support as coming. | Publicly listed |
| Memorystore | Supported | Not publicly listed | Not available Opsima lists Google Cloud support as coming. | Publicly listed |
| Cloud Bigtable | Supported | Not publicly listed | Not available Opsima lists Google Cloud support as coming. | Publicly listed |
| Managed Service for Apache Kafka | Supported | Not publicly listed | Not available Opsima lists Google Cloud support as coming. | Not publicly listed |
| Cross-cloud coverage | ||||
| AWS commitments in the same platform | Savings Plans Includes Database Savings Plans. | Savings Plans and RIs | Savings Plans and RIs | Savings Plans and RIs |
| Unified multi-cloud commitment view | AWS and Google Cloud | Multi-cloud | AWS today | Multi-cloud |
| Automation and governance | ||||
| Approval before purchase execution | Optional per-purchase approval | Configurable guardrails Public materials emphasize autonomous execution. | Not available Google Cloud support is not currently listed. | Autonomous-first Public materials emphasize full autopilot. |
| Fully autonomous optimization | Available | Available | Not available Autonomous optimization is currently AWS-only. | Available |
| Staged CUD purchases | Intelligent laddering | Adaptive Laddering | Not available Google Cloud support is not currently listed. | Adaptive layering |
| Spend and risk guardrails | Limits, thresholds, and pacing | Risk and budget controls | Not available Google Cloud support is not currently listed. | Risk-aware automation |
| Re-evaluation and reporting | ||||
| Continuous usage re-evaluation | Hourly | Continuous | Not available Google Cloud support is not currently listed. | Hourly |
| Effective Savings Rate reporting | ESR, utilization, and coverage | ESR dashboards | Not available for GCP | ESR and net savings trends |
| Beyond commitment management | ||||
| Full FinOps platform | Cloud Intelligence™ Cost visibility, allocation, governance, optimization, and cloud expertise. | FinOps automation platform Rate optimization, workload integrations, reporting, and showback. | AWS commitment specialist Public product materials focus on rate optimization. | FinOps platform Cost management, allocation, commitments, and workload optimization. |
| Cost attribution without cloud-resource tagging | Attribute™ Maps costs to customers and business dimensions without requiring tag coverage. | Intelligent Showback Allocates commitment costs and savings by account, resource type, and region. | Native AWS allocation Public guidance relies on AWS billing dimensions, categories, and tags. | Automated allocation Allocates untagged and shared costs using billing and workload metadata. |
| Kubernetes workload optimization | PerfectScale for Kubernetes Pod rightsizing, bin packing, autoscaling, and continuous optimization. | Via Flexera Ocean Integrated Kubernetes workload and commitment optimization. | Rate optimization only Covers EKS compute commitments without changing infrastructure. | EKS optimization Node, pod, and pricing optimization. |
| Snowflake workload optimization | PerfectScale for Snowflake Automated warehouse optimization, workload insights, and cost visibility. | Not listed | Not listed | Cost visibility and allocation Snowflake cost ingestion is documented; workload automation is not. |
| Databricks workload optimization | PerfectScale for Databricks Automated compute savings, workload insights, and DBU visibility. | Not listed | Not listed | Cost visibility and allocation Databricks cost ingestion is documented; workload automation is not. |
| BigQuery workload optimization | PerfectScale for BigQuery Reservation, slot, and query optimization insights with workload visibility. | Via Alvin partnership Partner-led BigQuery query and reservation optimization. | Not listed | Cost visibility and allocation Google Cloud cost analysis is documented; workload automation is not. |
Native capabilityPartial / preview / via integrationNot available
What they say
Connecting IBM and AWS privately was the piece we needed to get right, and we wanted to move faster on it than we could on our own. DoiT worked through the options with us, found the subnet overlap that was breaking the routing, and made it stable. That unblocked everything else.
DevOps Lead, Software Projects
Attribute™'s platform is truly unique. We now have crystal-clear visibility into our cloud spend at the workload and tenant level, and that insight has already led to actionable savings and powerful insights as we further scale our service.
Paul White, VP of Engineering, Shasta Cloud
We have worked with DoiT for many years, and there has been an increasing number of capabilities and features in DoiT Cloud Intelligence. We've embedded features such as Cloud Analytics and Reports in our own FinOps processes, it's become core to what we do.
Martin Lee, Director of Operations
DoiT gave us the confidence to move from experimentation to production. They helped us understand the right way to build AI for the real world.
Milad Rezazadeh, CTO
Frequently asked
questions
Which Google Cloud commitments does PerfectScale manage?
PerfectScale manages spend-based CUDs for Compute Engine, Cloud SQL, BigQuery Editions, AlloyDB, Cloud Spanner, Cloud Firestore, Dataflow, Memorystore, Cloud Bigtable, and Managed Service for Apache Kafka.
How is PerfectScale different from ProsperOps for Google Cloud?
ProsperOps publicly lists Compute support and Cloud SQL in Early Access, but does not list the other eight services covered here. PerfectScale supports all ten and adds optional per-purchase approval inside Cloud Intelligence™.
Does Opsima manage Google Cloud CUDs?
No. Opsima currently describes its product as AWS commitment management and lists Google Cloud support as coming. PerfectScale manages Google Cloud CUDs today alongside AWS commitments.
How is PerfectScale different from nOps for Google Cloud?
nOps publicly lists nine of the ten services covered here; Managed Service for Apache Kafka is not listed. PerfectScale supports all ten and adds optional per-purchase approval plus access to DoiT cloud expertise.
Can our finance team approve CUD purchases?
Yes. PerfectScale can require approval before each purchase executes. You can also set spend limits and pacing controls, or move to autonomous execution when your team is ready.
What happens when Google Cloud usage changes?
PerfectScale re-evaluates usage hourly. Because purchases are staged, the next step can reflect current demand rather than extending a commitment level chosen from an older forecast.
What Google Cloud commitment support is coming next?
We are expanding Compute coverage with Google Cloud Flexible Spend CUDs, with additional Cloud SQL CUD capabilities coming right after.
Google Cloud savings. Without the lock-in.
See what staged, usage-aligned CUD coverage could save.