Feature
Cost & FinOps
Price every plan against live AWS, Azure, GCP and OCI price lists before it deploys, track spend over time, and find savings in what already runs.
Most teams find out what a change costs when the bill arrives. By then the resources are running and the money is spent.
OrchesTerra moves the cost question to the point where a change is still a plan.
Cost before deploy
Every plan is priced before it reaches review:
- prices come from live AWS, Azure, Google Cloud and Oracle Cloud (OCI) price lists,
- the estimate shows on the provisioning form while you fill it in,
- reviewers see the monthly cost of a change next to the diff they are approving.
A reviewer can reject a change because it is too expensive, not only because it is wrong.
Spend history
Your cloud billing data feeds a spend history, so you can see how cost moved over time and which services drove it. AWS Cost Explorer is the main source today.
Savings findings
OrchesTerra scans what is already running and flags waste, such as unused IP addresses and unattached volumes. Fixing a finding (release, delete, snapshot or terminate) waits for the same approval workflow as any other change.
Related: Orbit can answer cost questions about your estate in plain words.
FAQ
Are the estimates exact?
They are estimates from public price lists, so they will not include your negotiated discounts or usage you can't know in advance, such as data transfer. They are close enough to catch the expensive mistake before it ships.
Which clouds are priced?
AWS, Azure, Google Cloud and OCI.