CoreStack vs Harness comparison

"My advice for others looking into using CoreStack is that anyone who is looking to optimize their workload cost for public cloud services should start using CoreStack because of the reports and granularity it produces to optimize cost, which will benefit them."

"CoreStack has positively impacted my organization by saving hours of time for reporting—for example, the governance report which my employees used to take at least four hours for one customer, and since I'm sending out 20 reports every month, that equates to 80 hours, thus saving me two man-weeks every month and approximately $8,000 in pure savings if I estimate $100 an hour for my architect."

"Currently, I think CoreStack is the best FinOps tool available in the market, which is why we are using it."

"Mainly through improved cost visibility and optimization with CoreStack, we have achieved a good ROI, and for some customers we were able to achieve more than forty percent cost savings by identifying unused and idle resources in their accounts, leading to significant cost savings after we completed the cleanup of those resources."

"My advice for others looking into using CoreStack is that anyone who is looking to optimize their workload cost for public cloud services should start using CoreStack because of the reports and granularity it produces to optimize cost, which will benefit them."

"Production deployments are faster and more reliable, especially for Kubernetes and cloud-based services, with significant reduction in deployment-related incidents, faster recovery when issues occur, faster, more confident releases, increased deployment frequency with higher confidence, and better governance and compliance that improved visibility and coordination across Dev, QA, Ops, and SRE teams."

"By adopting templates and various different pipelines across our own IDP platform, we have saved upwards of 30 to 40% of development time and also reduced risks of failures or error rates by upwards of 70%."

"The features of Harness are valuable, supporting rolling deployments, basic deployments, and blue-green deployments with zero downtime."

"Harness starts integrating with organizations, making everything automated without the need for manual interruption."

"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place."

"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place, making it convenient."

"It's a highly customizable DevOps tool."

"Everything in Harness is configured and runs smoothly."

"I noticed that some of the cost optimization reports generated potential savings while considering systems that have only maximum utilization of 1% or 2%. The recommendations made in CoreStack to delete a machine have the potential to generate major cost savings, but such machines should not be listed for deletion if they have maximum CPU utilization of 1%."

"I noticed that some of the cost optimization reports generated potential savings while considering systems that have only maximum utilization of 1% or 2%. The recommendations made in CoreStack to delete a machine have the potential to generate major cost savings, but such machines should not be listed for deletion if they have maximum CPU utilization of 1%."

"I give it an eight because, as I mentioned, a few things from the billing operations need to be added, and we need more security features, particularly since the market is increasingly demanding better security tools for cloud management platforms, including cloud security posture assessments."

"I believe CoreStack already has very good features in the governance and security parts, but stability can definitely be improved."

"When integrating Harness with more than twenty applications in one place, it becomes less stable, causing improvements to be necessary."

"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."

"When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment."

"Harness setup and configurations could be made easier to configure, which would be helpful."

"The first point for improvement is the steep learning curve, where concepts such as services, environment, pipelines, and templates take time to understand."

"I prefer the previous less compact UI version of Harness, which showed more details on the screen."

"Infrastructure as code or pipeline as code is something that Harness severely lacks."

"Even with automation, there's a requirement for manual change requests for approvals."