Sentra Cloud saved 41% on Google Cloud with committed-use discounts and idle clean-up
A 110-person cloud-native firm had GKE clusters sized for launch-day traffic, idle Compute Engine VMs and BigQuery queries scanning entire tables. Clean-up and committed-use discounts brought GCP spend from ₹7.2L to ₹4.2L a month.
- Cloud-native SaaS development
- 110 people · Mid-size
- Pune
- 5 weeks
Monthly spend
- Saved / month
- ₹3L
- Reduction
- 41%
- Payback
- 17 days
−41%
GCP spend
₹35.4L
Annual saving
37
Idle VMs removed
−58%
BigQuery bytes scanned
The challenge
Sentra had built fast and scaled early. Clusters were provisioned for traffic that never arrived, and dozens of VMs from finished proofs of concept were still running.
The team had never bought committed-use discounts because they were unsure what their baseline really was.

What we reviewed
- GCP billing export to BigQuery for 12 months
- 9 GKE clusters and node-pool utilization
- Compute Engine instances and idle-resource recommendations
- BigQuery job history and slot usage
- Cloud Storage classes and egress patterns
The approach
- 1
Remove what is idle
Thirty-seven idle VMs, unattached disks and unused static IPs were removed after owner sign-off.
- 2
Right-size GKE
Node pools were resized, cluster autoscaler tuned, and batch workloads moved to Spot VMs.
- 3
Buy commitments for the true baseline
Once the estate was clean, resource-based committed-use discounts covered the stable baseline.
- 4
Make BigQuery queries cheaper
Partitioning, clustering and query guardrails reduced bytes scanned by 58%.
Before and after
Monthly cost by line item, in Indian rupees.
Sentra Cloud — monthly cloud spend
Monthly| Line item | Before | After | Saving |
|---|---|---|---|
| Compute Engine VMs | ₹2,90,000 | ₹1,58,000 | −₹1,32,000 |
| GKE clusters | ₹1,70,000 | ₹98,000 | −₹72,000 |
| Cloud SQL | ₹1,05,000 | ₹72,000 | −₹33,000 |
| BigQuery | ₹85,000 | ₹52,000 | −₹33,000 |
| Cloud Storage and egress | ₹70,000 | ₹44,800 | −₹25,200 |
| Total | ₹7,20,000 | ₹4,24,800 | ₹2,95,200 (41%) |
Monthly spend over time
₹35.4L saved per yearTwo months before the engagement, then six months after the plan was delivered.
Timeline
Week 1
Billing analysis
Billing export and recommender data reviewed.
Weeks 2–3
Clean-up and right-sizing
Idle resources removed; cluster changes validated in staging.
Week 4
Commitment plan
CUD sizing finalized on the cleaned baseline.
Week 5
Delivery
Plan, guardrails and dashboards handed over.
“They gave us the confidence to commit, because they first showed us what our real baseline was. Forty-one percent is a number our board noticed.”
Related case studies
All case studies
CloudMonthly spend
₹6.4L → ₹3.9L
Northbridge Systems · 120 people · Bengaluru
Northbridge Systems cut its AWS bill from ₹6.4L to ₹3.9L a month
Read case study
CloudMonthly spend
₹8.4L → ₹5.7L
Orchid Softlabs · 105 people · Ahmedabad
Orchid Softlabs cut Azure and Microsoft 365 spend by 32% in one engagement
Read case study
CloudMonthly spend
₹1.8L → ₹1.1L
Vertex Labs India · 28 people · Ahmedabad
Vertex Labs reduced its Azure spend by 38% in four weeks
Read case studyFind out what your agency could save
Book a 20-minute call. We'll show you where the quickest wins usually are for a team like yours, with no data required and no obligation.
- Free 20-minute assessment
- NDA before any data is shared
- Fixed-scope quote, 30/70 payment terms
- 7 days of post-delivery support