CostOps

CostOps turns billing data from one cloud connection into a current spend view and agent-verified savings findings. It supports AWS, GCP, and Azure without combining their billing scopes or currencies.

​

How it works

1. Connect a cloud account — add an AWS, GCP, or Azure connection with read access.
2. Set the billing source — AWS uses the connected account. GCP uses one Cloud Billing Standard export, and Azure uses one readable subscription or billing scope.
3. Run the first scan — CostOps reads billing data, starts one full-connection cost scan, and keeps running in the background if you leave the page.
4. Review spend and findings — compare current spend, forecast, top services, and potential monthly savings for the selected connection.
5. Keep it current — daily refresh pulls new billing data and runs cost keepers. Turning it off is immediate; turning it on asks you to confirm, because it resumes agent spend.

The scan is read-only. A missing CostOps permission or billing source blocks CostOps, but it does not disconnect the cloud connection. The daily refresh control appears after the first scan produces cost data, and requires CostOps management permission.

​

What you can do

​

Provider behavior

If GCP or Azure has a readable billing source but no published rows, CostOps waits for the provider to publish data. The connection remains healthy.

​

Get started