Free scan
₹0
One account. Your total waste and the top 3 findings; the rest counted.
Start your free scanCut yourcloud bill.Safely.
CoverOps finds every rupee of cloud waste through a read-only role in your own account, prices it, and fixes only what your cloud team approves. Each fix can be rolled back.
Free scan on one account. Read-only access you create and can revoke any time.
- 5 EC2 servers idle for a weekStop₹41,600
- 2 stopped servers still paying for disksSnapshot and retire₹3,900
- 9 unattached EBS volumesSnapshot and delete₹7,200
- 2 RDS databases three sizes too bigRightsize₹28,300
Monthly waste ₹81,000 · each fix waits for your approval and can be rolled back
Illustrative figures. Your free scan shows your own.
Connects read-only to
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Oracle Cloud
From read-only access to a smaller bill
Four steps, and you can stop after any of them. Nothing changes in your cloud until a named person on your team approves it.
- 1
Connect
Read-only, revocable
Apply the read-only access CoverOps generates, as Terraform, CloudFormation or a CLI script. Never a password. Delete it and access ends at once.
- 2
Free scan
₹0, in minutes
Your total waste per month and the top 3 findings on one account, before anyone pays anything.
- 3
The audit
From ₹24,999, within 3 working days
Every finding with its evidence and the exact fix, reviewed by an engineer. Refunded if it finds less monthly waste than its fee.
- 4
The plan
From ₹14,999 a month
We keep it fixed: monitoring, approved fixes with rollback, a monthly review. The audit fee is credited if you start within 60 days.
Where the money leaks
Cloud and Kubernetes first: that is most of an Indian startup's bill. GPU and LLM-agent spend use the same engine and are shown on demo data today.
- Cloud accounts
Idle and oversized cloud resources
“Last year's launch, still billing every hour.”
Unattached volumes. Oversized instances. Servers left running in a region nobody uses. Servers stopped but still paying for their disks. Every finding arrives priced in rupees, with the fix attached.
- Read-only access you create and can revoke: a role with an External ID on AWS, read-only credentials on Azure, GCP, DigitalOcean and Oracle Cloud. Never a password
- Every enabled region scanned, cost and utilisation per resource
- Kubernetes cost: not built yet, on the roadmap with the in-cluster agent
- Fixes applied only after your cloud team approves, each with a rollback
- MLOps
GPU hours nobody is watching
Demo data today“Your job is running. Your GPUs are idle.”
Teams watch whether a job is alive. Nobody watches accelerator utilisation. So eight H100s sit at 30% for a fortnight and the bill looks completely normal.
See the arithmetic- Runs under 35% utilisation get flagged as starved, not compute-bound
- Only the idle share is priced as recoverable
- Spot runs without checkpointing, where one preemption bins the epochs you paid for
- Endpoints under 25% utilisation, holding a GPU warm between requests
- AgentOps
LLM tokens billed for answers nobody read
Demo data today“A blocked run costs nothing. That is the whole saving.”
Cached tokens cost a tenth of fresh ones. Most teams have caching off, or a prompt prefix that shifts just enough to miss it every time.
See the arithmetic- Every run metered against the catalog. Fresh, cached and output priced apart
- Frontier models doing work a cheaper tier handles at 96% success
- Caching off, or hitting under a quarter of the time
- Looping and timed-out runs that billed in full for nothing
- Guardrails run before billing. A blocked run is a clean saving
- AIOps
Alert noise that costs engineers, not dollars
“One outage should page once. Not three times.”
Every metric is measured against its own rolling baseline, so a signal has to be unusual to register. Related anomalies collapse into one incident with a probable cause attached.
- A rolling baseline, not a threshold nobody tuned
- Anomalies inside five minutes become one incident
- Playbooks propose the fix, or apply it with the same audit trail
- Automation can only do what an operator could
Put in your own node
Pick the accelerator, the count, and where utilisation actually sat on your last long training run. Not where the dashboard said the job was healthy.
Under 35%: flagged as starved on input, not compute-bound.
Recoverable per year
₹2,98,86,093
₹2.99 crore ($339,615 on a dollar bill)
- Node run rate
- ₹50,82,669/mo
- Idle accelerator share
- 70%
- Unavoidable-idle discount
- ×0.7
- Recoverable
- ₹24,90,508/mo
Arithmetic on our own accelerator price list, using the formula wasteReport() runs in the product. It is not a measured customer outcome. Rupees at ₹88 to the dollar.
The console opens on the money
One figure first: what your cloud wastes each month, in rupees, and whether it came from your bill or list prices. Every finding under it says what to do about it.
Monthly waste estimate scanned 4m ago
₹28,480
Cloud spend ₹5,86,762/mo · Share of spend 5% · Resources 58
| Finding | Per month | Fix |
|---|---|---|
| Unattached disk 5 volumesNot attached to any server; billed every month all the same. | ₹12,112 | Approve & apply |
| Oversized compute-7712-09CPU 5.8% and memory 33.5% against a full-size instance. | ₹9,437 | Approve & apply |
| Stopped, still billing ec2-5104-03The server is stopped, so its compute is not billed, but its attached disks still are. | ₹6,931 | Advice, with the command |
It runs in your account
CoverOps reads your accounts; it never hosts them. Your workloads never leave your cloud, and the worst case of trusting us is a role you wrote and can delete.
What it can do
- Read your cloud, cluster, GPU and agent inventory to price what it costs
- Raise fixes as proposals: stop, rightsize, scale to zero, delete an idle volume
- Apply a proposal only after a named person approves it
- Collect the metrics, logs and traces you route to it
- Run the remediations you have explicitly switched on
What it cannot do
- Hold your cloud root credentials
- Run your workloads on machines we own
- Change a resource you have not tagged coverops:managed=true
- Read your application data or database contents
- Keep working after you revoke the role
- Your account, your resources
- Everything lives in your AWS, Azure, GCP, DigitalOcean or Oracle Cloud account: your billing, your regions, your policies.
- A scoped role, no stored keys
- Access is a role you create from a policy CoverOps generates, read-only by default. Write access is a separate, deliberate step.
- Your audit log sees everything
- We act through your provider's API, so CloudTrail and Azure Activity Log record what we did, when, and as whom.
- Evidence an auditor will accept
- Change history, approvals and policy results export as audit artefacts. CoverOps is not a certification and does not pretend to be.
Built so you can leave
A platform that is painful to leave is one you should be nervous to join, so we designed the way out first.
Coming in
Apply a read-only role CoverOps generates for you. It reads what you already run. Nothing is rebuilt or migrated.
While you use it
Nothing changes until a named person approves it, only on resources you tag coverops:managed=true, and every change keeps a snapshot to roll back from.
Leaving
Delete the role and cancel. Your workloads never ran on us, so traffic never notices. Export the audit log on the way out.
Our test: if CoverOps disappeared overnight, your production environment should not notice. If that ever stops being true, we built the wrong thing.
Where we lose, and where we don't
Mature products already do cloud cost well. Nobody prices GPU and agent waste. That gap is why we exist, and it is why two of these rows go to someone else.
| Spreadsheet + scripts | Cloud-native cost tools | FinOps platforms | CoverOps | |
|---|---|---|---|---|
| Paid more when your bill grows | No | Yes, it is their bill | Often, priced as a share of spend | No. A fixed price set by your bill band (strongest) |
| Cloud cost visibility | Manual, monthly, already stale | Good, per provider | Excellent, multi-cloud (strongest) | Good, multi-cloud |
| Depth of cost reporting and chargeback | None | Strong within one cloud | Best in class, years of maturity (strongest) | Adequate, not our focus |
| GPU and accelerator waste | Invisible | Shows the spend, not the utilisation | Shows the spend, not the utilisation | Priced per starved run, with the fix (strongest) |
| LLM agent token spend | Invisible | Not covered | Not covered | Metered per run, guardrails before billing (strongest) |
| Findings arrive with the change attached | No | Recommendations only | Recommendations, mostly manual to apply | Evidence, the fix and a rollback snapshot (strongest) |
| Acts on the finding, with approval | No | No | Rarely, and rarely trusted | Playbooks that suggest or auto-apply (strongest) |
| Runs inside your own cloud account | N/A | Yes, by definition | Usually SaaS with read access | Yes, through a revocable scoped role |
Strongest on that line
Free scan, one audit, then a plan
Priced by the size of your monthly cloud bill, in rupees, plus GST. Never a percentage of your bill or of what you save. We aim for you to keep at least three times what you pay us; if the audit finds less monthly waste than its fee, the fee comes back.
| Your monthly cloud bill | Audit (once) | Plan (a month) | Engineer hours included |
|---|---|---|---|
| Starter: up to ₹10 lakh | ₹24,999 | ₹14,999 | 2 a month |
| Growth: up to ₹50 lakh | ₹49,999 | ₹39,999 | 6 a month |
| Scale: up to ₹2 crore | ₹99,999 | ₹99,999 | 15 a month |
The audit
from ₹24,999
plus GST, paid upfront
Every account you connect. Refunded if it finds less monthly waste than its fee.
Report within 3 working days
Get the auditEnterprise
Quoted
Cloud bills above ₹2 crore a month, groups of companies, migration projects.
Talk to usIn every audit
- Every cloud account you connect, every enabled region
- Idle, oversized and orphaned resources, priced per month in ₹
- The exact CLI or Terraform change for each fix
- Every figure labelled billed or estimate
- A 60-minute readout with your engineers and budget owner
Ops add-ons, ₹9,999 a month each
- Kubernetes ops. Our engineers run your clusters: node pools, requests against real usage, upgrades.
- CI/CD ops. Our engineers run your deploy pipelines behind named approvers, with rollback.
- Monitoring ops. Our engineers set up and route your alerts, anomaly playbooks and security findings.
Every plan shows the cost of your clusters, pipelines and monitoring; add-ons are our engineers doing the work. Cancel any month; prepay a year and pay 10 months for 12. Extra engineering hours ₹2,500 an hour. Prices exclude 18% GST; TDS as applicable. Your cloud bill stays in your own account and is never marked up. Full price list. Want to see the report first? Open the sample audit.
Scan one cloud account, free.
Sign up and apply the read-only role CoverOps generates. In minutes you see your total waste per month and the top three findings, before anyone pays anything.