Kubecost vs. Virtana Optimize

Well suited for a k8 platform and the clients on the platform however doesn’t help as much for a total enterprise cloud cost that is not running on k8

Incentivized

Very suited for medium to the large-sized infrastructure where you have a lot of services to monitor. It may be overkill for small infrastructures where you can use the providers' source of metrics instead.

Incentivized

• Show namespace level cost and usage
• Allow rightisizibg At namespace level
• Show effectiveness of current resources allocation

Incentivized

• AWS Cost analysis across multiple accounts.
• Identification of orphaned and underutilized resources.
• Easy integration to your AWS account.
• Simple and intuitive user interface.

Incentivized

• Agents installation and the ping fed integration
• The amount of CPU Kubecost agents use

Incentivized

• It can be tricky to set-up depending on what you want to do.
• They have their own proprietary way of visualizing metrics, which is clever but does have a slight learning curve.

Incentivized

Anytime we've had issues they have been very responsive and professional.

Incentivized

Namespace cost, usage and efficiency data and ability to optimize for k8 containers

Incentivized

We strongly prefer Metricly for AWS Cost Analysis -- whereas other tools are easier to use on a traditional monitoring basis. To be clear, Merticly's monitoring tools are GREAT, but they require tuning and manual setup that we didn't have the time for on a small Platform Operations team. We have worked closely with Metricly to expand on their cost analysis capabilities, and plan to use them going forward.

Incentivized

• Allowed individual teams to better their cloud architecture for cost efficiency
• Save on cloud investment

Incentivized

• We were able to decrease AWS costs with its predictive analytics by 20% YOY.

Incentivized