Senior Solution Architect at Hitachi Systems India Private Ltd
Real User
Top 5
Dec 12, 2025
My main use case for CoreStack is cloud cost governance and FinOps maturity. We are using CoreStack for our operations team and we have multiple cloud customers from different hyperscalers. For a specific use case, there is a customer who is using their AWS, Azure, and GCP environment. With this particular tool, we offered them a consolidated overview of CloudOps and FinOps and where they can save cost. We have reduced their cloud spend by 20% with the cost governance and FinOps options available in CoreStack. Currently, we are using CoreStack for cost governance and FinOps only, but we are trying to integrate Ops Automation and SecOps offerings from CoreStack.
Senior Vice President at a tech services company with 10,001+ employees
Real User
Top 5
Dec 9, 2025
My main use case for CoreStack is for cost optimization and billing operations, and I'm using it a bit for SecOps and CloudOps, but majorly for FinOps and BillOps. A specific example of how I use CoreStack for FinOps or billing operations is for many of our customers who are running their workload on the cloud; whether AWS, Microsoft Azure, OCI, or Google, everyone is looking for continuous cost optimizations. That is one of the reasons we have opted for CoreStack. It gives a detailed review of the account running in AWS, providing recommendations on reserved instances, saving plans, and orphan volumes. It gives extensive details on the FinOps and the cost optimization, which helps us to optimize the workload for the customer, thus giving us stickiness. The major thing about my main use case is that we are using CoreStack for BillOps as well, where we give a detailed invoice to the customer with the blended cost, using unblended raw data from AWS and blending it with our margins before sharing the invoices with the customer. While the major use case is FinOps, we also utilize it for BillOps.
CoreStack® Enterprise Enables You to be agile and eliminate waste while proactively mitigating risks by making your cloud governance intelligent and autonomous. It applies Cloud-as-Code™ approach to govern the four critical components of your cloud
My main use case for CoreStack is cloud cost governance and FinOps maturity. We are using CoreStack for our operations team and we have multiple cloud customers from different hyperscalers. For a specific use case, there is a customer who is using their AWS, Azure, and GCP environment. With this particular tool, we offered them a consolidated overview of CloudOps and FinOps and where they can save cost. We have reduced their cloud spend by 20% with the cost governance and FinOps options available in CoreStack. Currently, we are using CoreStack for cost governance and FinOps only, but we are trying to integrate Ops Automation and SecOps offerings from CoreStack.
My main use case for CoreStack is for cost optimization and billing operations, and I'm using it a bit for SecOps and CloudOps, but majorly for FinOps and BillOps. A specific example of how I use CoreStack for FinOps or billing operations is for many of our customers who are running their workload on the cloud; whether AWS, Microsoft Azure, OCI, or Google, everyone is looking for continuous cost optimizations. That is one of the reasons we have opted for CoreStack. It gives a detailed review of the account running in AWS, providing recommendations on reserved instances, saving plans, and orphan volumes. It gives extensive details on the FinOps and the cost optimization, which helps us to optimize the workload for the customer, thus giving us stickiness. The major thing about my main use case is that we are using CoreStack for BillOps as well, where we give a detailed invoice to the customer with the blended cost, using unblended raw data from AWS and blending it with our margins before sharing the invoices with the customer. While the major use case is FinOps, we also utilize it for BillOps.