97 optimization rules, run from your terminal or CI. Your credentials never leave your infrastructure, with an air-gapped option for regulated teams.
Try it without an account
# install the binary (macOS, Linux) curl -sSL https://releases.dragonfractal.com/install.sh | sh # scan a bundled example — no credentials, no sign-up cca demo
then, against your own account:cca scan --provider aws --all23 findings$4,832/mo
Windows, Docker, and the direct downloads are in the installation docs.
Built by an ex-AWS engineer, not a marketing team.
$ cca scan --provider aws
✓ Discovered 1,247 resources across 3 regions
✓ Analyzed against 97 optimization rules
✓ Found 23 optimization opportunities
Potential Monthly Savings: $4,832
Optimization Score: 72/100
Example output. Actual findings and savings vary by account.
Not heuristics and not a severity label — a named condition, with a known fix and a dollar figure attached.
Comprehensive cost analysis covering EC2, RDS, S3, and 40+ AWS services, plus Azure (BETA).
AWS fully supported. Azure BETA covers 14 of the 97 rules today — VM right-sizing, Reserved Instances, Hybrid Benefit, Azure SQL and Blob tiering — with broader coverage in progress. GCP is on the roadmap.
Integrate with your existing CI/CD pipeline or use the powerful CLI for ad-hoc scans.
A real result, verified in AWS Cost Explorer
$23,107 /year saved
We ran Cloud Cost Analyzer on a real production AWS account, then acted on the findings. Six fixes, zero production incidents, and the savings independently confirmed against AWS Cost Explorer billing data over three cycles.
Based on AWS Cost Explorer unblended costs in us-east-1, February to April 2026. Account anonymized.

I spent five years at AWS as a lead engineer on Amazon OpenSearch Serverless. Idle NAT gateways. gp2 volumes nobody ever migrated to gp3. Elastic IPs nobody released. CloudWatch log groups with no retention policy, growing forever. DynamoDB tables provisioned for traffic that never showed up. I kept seeing the same five leaks on account after account, and the billing console never called any of them out by name. CCA is the tool I wished existed: it names the leak, shows the math, and tells you exactly what to check.
The free plan is $0 forever and reports your full savings total. Paid plans name the resources and the exact fixes.
For individual developers
$0/forever
Air-gapped & self-hosted deployment is included with Enterprise and available standalone for regulated teams. Talk to us.
Yes. The CLI uses read-only AWS and Azure APIs. It never modifies resources, and no secrets, credentials, or application data are ever accessed.
Your credentials never leave your machine, and the scan itself uses read-only APIs. In the default managed mode, the CLI sends what it collected to our service for analysis: resource metadata (IDs, types, regions, tags, configuration), utilization metrics and cost records. It does not send your credentials. Our Privacy Policy describes how that data is handled. Enterprise adds an air-gapped mode that runs entirely offline, with nothing leaving your network.
Cost Explorer shows you what you already spent, broken out by service and tag. It was never built to tell you that one specific NAT gateway has been idle for three months, or that an Elastic IP has been unattached since April. The usage data that would prove that already exists in your account; Cost Explorer just doesn't connect it into a finding. CCA scans for the specific leak, names the resource, and shows the math. Most teams use both.
Yes. The Free plan is $0 forever and runs all 97 rules on up to 5,000 resources per scan, showing your total potential savings. Paid plans add per-finding detail (resource IDs and exact fixes), higher resource limits, and team features.
Under five minutes. Install the CLI, run a scan, and get a prioritized report. There are no agents to deploy and no cross-account role to set up.
AWS fully supported · Azure in BETA · GCP roadmap. 14 of the 97 rules carry Azure coverage today — VM right-sizing, Reserved Instances, Hybrid Benefit, Azure SQL (underutilized, serverless, zone-redundant non-prod), Blob cool tiering, and the generic idle/unattached rules. The remainder are AWS-only. GCP has no collector yet.