IBM Cloud cost optimization for engineering and finance teams.
Find out why your IBM Cloud bill grew, and what to cut. Omni FinOps will read your IBM Cloud billing snapshots, inventory and metrics through a read-only service ID, explain every jump in plain dollars, and list the waste with the ibmcloud command to fix it.
The IBM Cloud connector is coming soon. AWS and Google Cloud connect today; start a trial on one of them, and IBM Cloud joins the same account when it ships.
No card. Read-only access. Omni FinOps never changes your cloud.
Will read
- Daily usage, from billing report snapshots in Cloud Object Storage
- Inventory: virtual server instances and block storage volumes
- CPU metrics, from IBM Cloud Monitoring
Can’t
- Create, change, stop or delete anything
- Read any bucket but the one holding the reports
Delete the service ID or its API key and access ends.
What it will flag in IBM Cloud
Every refresh checks each resource against these rules. A match becomes a lead with its monthly saving, the evidence behind it and the command to fix it. Nothing changes until your team runs it.
- Idle instancesCPU under 5% every day for two weeks. Stop it, or delete it if nothing needs it.
- Dev and staging running 24/7Tagged dev, test, staging, QA or sandbox and running around the clock. Run it weekdays 08:00–20:00 only.
- Unattached volumes and disksAttached to no instance. Delete it, after a snapshot if anyone might need it.
How connecting IBM Cloud will work
IBM Cloud writes the month’s usage to a Cloud Object Storage bucket every day. A service ID with viewer and reader roles reads those reports, your inventory and its metrics.
- 1Export billing report snapshots. In Manage → Billing and usage → Reports, turn on Snapshots to a Cloud Object Storage bucket.
- 2Create a read-only service ID. Viewer sees billing and resources, Reader sees metrics and the reports bucket only. None of them can change anything. The last command prints the API key.
- 3Enter the details. Paste the account ID, the bucket and the API key into Cloud accounts.
The setup, in the terminal
ibmcloud iam service-id-create omni-finops-reader \ -d "Omni FinOps (read-only)" ibmcloud iam service-policy-create omni-finops-reader \ --roles Viewer --service-name billing ibmcloud iam service-policy-create omni-finops-reader --roles Viewer ibmcloud iam service-policy-create omni-finops-reader \ --roles Reader --service-name sysdig-monitor ibmcloud iam service-policy-create omni-finops-reader --roles Reader \ --service-name cloud-object-storage \ --service-instance <reports-cos-instance-id> \ --resource-type bucket --resource <reports-bucket> ibmcloud iam service-api-key-create omni-finops omni-finops-reader \ -d "Omni FinOps"
Questions about IBM Cloud
- Can I connect IBM Cloud today?
- Not yet. IBM Cloud shows as Coming soon in the app until its connector ships, and this page shows the setup it will use. AWS and Google Cloud connect today.
- What will it be able to change?
- Nothing. Viewer sees billing and resources, and Reader sees metrics and the reports bucket only.
- How will scheduling work without a built-in VM schedule?
- IBM Cloud has none, so the lead’s command stops and starts the instance from a Code Engine cron job.
- What will it flag on IBM Cloud?
- Idle virtual server instances, dev and staging instances running around the clock, and block storage volumes attached to nothing, each with the ibmcloud command to fix it.
Start with AWS or Google Cloud today.
No card. Read-only access. Omni FinOps never changes your cloud.