CloudFix vs OpenCost

CloudFix identifies potential AWS cost savings and can apply changes after a customer approves them. Its product lists more than 110 finders and 53 automated fixers across more than 30 AWS services. Finders analyze Cost and Usage Reports, CloudWatch metrics, and resource metadata; the company says they do not access data in customer data stores. CloudFix connects through least-privilege IAM roles created with CloudFormation, without agents or stored credentials. Approved fixes run in the customer’s AWS account as Systems Manager Automation runbooks. Activity is recorded in the customer’s CloudTrail, with each fix execution logged. The Trust Center states that CloudFix is SOC 2 Type 2 audited, uses TLS 1.2+ in transit and AES-256 at rest, and lists a 99.5% per-quarter uptime SLA for the dashboard and API. The free tier includes a scan, savings by category, and full resource details for 30 days. Paid plans are aimed at different annual AWS spend levels; subscriptions are processed through AWS Marketplace with monthly or annual billing. Higher tiers add support, optimization reviews, integrations, and other services. CloudFix supports cost allocation, rightsizing guidance, and commitment management, but does not offer budget alerts.

OpenCost is a vendor-neutral open source project for measuring and allocating Kubernetes and cloud infrastructure costs. It breaks down costs in real time to Kubernetes concepts and containers for showback, chargeback, and reporting. Allocation covers CPU, GPU, memory, load balancers, and persistent volumes, and it can monitor cloud resources outside Kubernetes. The included web UI visualizes Kubernetes allocations and related cloud costs. Its API provides real-time and historical Kubernetes cost reports using on-demand list prices and cloud provider cost and usage reports. Listed cloud providers include Alibaba, AWS, GCP, Microsoft Azure, Open Telekom Cloud, Oracle Cloud Infrastructure, OVHcloud, Scaleway, and STACKIT. Metrics and visualization integrations include Prometheus, Cortex, Thanos, Victoria Metrics, Grafana, and Grafana Cloud. OpenCost requires a Kubernetes cluster and Prometheus; Helm is recommended for full functionality. Cloud costs appear when provider billing data becomes available, usually several hours to 24 hours later, and on-demand pricing is not reconciled against billed actual costs. Cloud costs are not supported for on-premises clusters. OpenCost is free under Apache 2.0.