Cloud Cost Analyzer
A developer-first, read-only, safety-first cloud cost analyzer that scans cloud infrastructure (AWS and Azure, with GCP planned) for waste such as over- or suboptimally provisioned databases, idle resources, forgotten EBS snapshots, outdated/previous-gen instance types, and vestigial networking. Its primary mode of operation is a Rust CLI that developers can run on their workstation or in GitHub Actions, GitLab CI, Jenkins, etc., producing an actionable report/test to control costs while maintaining performance, without exposing credentials or access tokens.
What it addresses
Cloud accounts contain waste — over/suboptimally provisioned databases, idle resources, forgotten EBS snapshots, outdated/previous-gen instance types, and vestigial networking leading nowhere.
Shared over time
Each entry reflects what was shared on that date. Details may have changed since then.
Cloud Cost Analyzer
A developer-first, read-only, safety-first cloud cost analyzer that scans cloud infrastructure (AWS and Azure, with GCP planned) for waste such as over- or suboptimally provisioned databases, idle resources, forgotten EBS snapshots, outdated/previous-gen instance types, and vestigial networking. Its primary mode of operation is a Rust CLI that developers can run on their workstation or in GitHub Actions, GitLab CI, Jenkins, etc., producing an actionable report/test to control costs while maintaining performance, without exposing credentials or access tokens.
Problem: Cloud accounts contain waste — over/suboptimally provisioned databases, idle resources, forgotten EBS snapshots, outdated/previous-gen instance types, and vestigial networking leading nowhere.
Audience: A developer-first tool: developers run the Rust CLI themselves on their workstation or CI pipeline.
Posted by @jorelfermin · Original comment ↗
“I have been working on a developer first, read-only first, safety first, Cloud Cost Analyzer. I focus on analyzing cloud infra for waste.”