Find AWS waste from your terminal or your AI assistant.
cloudcostwise runs CloudWise's free waste checks on your own machine with your own read-only AWS credentials. No signup, no IAM role for a third party, and nothing is sent to CloudWise unless you choose to share a summary. It refuses any AWS call that isn't a read.
$ pipx install cloudcostwise$ cloudcostwise scan --profile my-profile
Or without installing: uvx cloudcostwise scan. Python 3.11+. See a sample scan first, or run uvx cloudcostwise scan --demo for sample findings with no AWS credentials.
- Read-only by design
- No signup
- Opt-in sharing only
- Open source (Apache-2.0)
$ cloudcostwise scan --regions us-east-1,us-west-2 --no-cost-explorer
scanning 2 region(s), 2 at a time ...
[1/2] us-west-2 0 finding(s) 8.3s
[2/2] us-east-1 54 finding(s) 45.3s
AWS account 123456789012 | regions: us-east-1, us-west-2
idle_dynamodb x1 $5.69/mo
us-east-1 DynamoDB table B $5.69/mo
dynamodb_no_autoscaling x1 $0.85/mo
us-east-1 DynamoDB table B $0.85/mo
s3_rapid_growth x1 $0.28/mo
us-east-1 S3 bucket D $0.28/mo
orphaned_ebs_snapshot x3 $0.15/mo
us-east-1 EBS snapshot B $0.05/mo
us-east-1 EBS snapshot A $0.05/mo
us-east-1 EBS snapshot C $0.05/mo
...
Estimated savings: $7.26/month
20 of 46 service checks run locally.A real, read-only scan of our own fixture account on 8 November 2026, across two regions; every finding comes from test resources we keep running for this purpose (cloudcostwise 0.1.19). The account ID is replaced with a placeholder. The Cost Explorer requests cover the RI and Savings Plans checks, one spend read for the score and, only when the S3 bucket-key check finds a bucket, one KMS spend read for the whole scan, which AWS bills at $0.01 per request: up to about $0.10 a scan, however many regions you scan. The CLI says so before it scans;
--no-cost-explorer skips them.20 of CloudWise's 46 detectors, covering 92 waste checks: the common, high-hit ones.
Every waste type it reports carries its validation level, from unit-tested to fired on a real AWS resource and silent on a healthy twin. See the evidence. Advisory findings are labelled and never added to a total. Browse every waste check.
- EC2
- Lambda
- SageMaker
- WorkSpaces
- Lightsail
- EBS
- S3
- EFS
- ECR
- RDS
- DynamoDB
- ElastiCache
- Elastic IPs, NAT gateways, load balancers
- VPC endpoints
- Dangling DNS records
- CloudWatch logs
- CloudWatch dashboards
- Security posture
- RI and Savings Plans opportunities
- Compute Optimizer
19 of its 56 proven checks flag waste that Trusted Advisor, Cost Optimization Hub and Compute Optimizer don't, and 13 more go further than the closest AWS check.
For idle EC2, RDS and NAT gateways, rightsizing and Savings Plans, AWS's tools cover the same ground: use them too. Checked against AWS's own lists of what each tool covers on 2026-10-11. The full table, with the closest AWS check for each.
Use it from Claude Code, Codex, Cursor, Kiro or Gemini CLI.
Then ask: "Where am I wasting money on AWS?" Four read-only tools: scan, list findings, explain a finding, fix guidance. Fixes come back as text for you to review; nothing is ever executed. The plugin and registry entries start it with uv, so install uv first.
$ /plugin marketplace add cloudwise-app/cloudcostwise$ /plugin install cloudcostwise@cloudcostwise
$ claude mcp add cloudcostwise -s user -e AWS_PROFILE=my-profile -- uvx cloudcostwise mcp
~/.codex/config.toml):$ [mcp_servers.cloudcostwise]$ command = "uvx"$ args = ["cloudcostwise", "mcp"]$ env = { AWS_PROFILE = "my-profile" }
$ gemini mcp add -s user cloudcostwise uvx cloudcostwise mcp
~/.kiro/settings/mcp.json):$ {$ "mcpServers": {$ "cloudcostwise": { "command": "uvx", "args": ["cloudcostwise", "mcp"] }$ }$ }
Nothing leaves your machine unless you share.
The CLI sends nothing to CloudWise unless you choose to share a summary, at the end of a scan or later with cloudcostwise share --last. Through an AI assistant, the findings go to that assistant like any tool output.
Permissions
ReadOnlyAccess is enough. The minimal policy (71 read actions) is in the repository. A check that lacks a permission reports its findings as missing, never as zero. EC2 instance prices come from the AWS Price List when the AWS credentials the scan uses, or failing that your default AWS credentials, allow pricing:GetProducts, and from built-in prices (adjusted by region) otherwise.
Open source under Apache-2.0: read the code on GitHub.
The partner build
All 46 detectors, one scan across every client account, and a client report under your firm's name. Runs on your machine like this tool.
What the hosted product adds
The other 26 detectors, 95 more waste checks (Glue, ECS, Step Functions, Backup, CloudFront, commitments and more), savings reconciled against your bill, history and alerts, and safe fixes you approve, with rollback. 23 more of its proven checks flag waste none of AWS's own tools do, across AWS Backup, AppSync, CloudFront, Elastic Beanstalk, FSx, Glue, KMS, Kinesis, Route 53, Step Functions.