Skip to main content

The open-source toolkit

FinOps Guardian

Find unused resources. Understand where your cloud budget goes.

Open sourceMIT license

What it does

FinOps Guardian checks AWS and Google Cloud for idle resources and opportunities to reduce costs. Terraform modules deploy scheduled functions that send findings to Slack or email. Review the reports and use dry-run mode before enabling AWS resource cleanup.

What’s included

AWS Resource Cleanup

Automated Lambda-based tool that identifies and removes unused AWS infrastructure across multiple regions.

  • Scans EC2, EBS, EIPs, ALBs, RDS, EKS, Kinesis, MSK, OpenSearch
  • Operates across 7+ configurable AWS regions
  • Dry-run mode for safe evaluation before deletion
  • Scheduled nightly via CloudWatch Events

GCP FinOps Recommender

Uses Google Cloud’s Recommender API to find idle resources and sizing recommendations.

  • Detects 10 recommender types: idle VMs, disks, IPs, SQL
  • Right-sizing for VM instances and Managed Instance Groups
  • Organization-level and project-level scanning
  • Cost impact metrics with configurable thresholds

Slack and email reports

Send scan results and estimated cost impact to your team’s Slack channel or email.

  • Slack integration with cost impact details
  • Email reports via AWS SES
  • Configurable alert thresholds
  • Audit logs for scan and cleanup activity

Getting it running

01

Deploy with Terraform

Use the provided Terraform modules to deploy FinOps Guardian in your AWS and GCP environments.

02

Automated Scanning

Serverless functions run on schedule, scanning your cloud accounts for idle and underutilized resources.

03

Review Recommendations

Receive Slack notifications and email reports with cost-saving opportunities and their estimated impact.

04

Review cleanup actions

Use dry-run mode to preview cleanup actions, then enable automated resource removal when ready.

What it helps with

Find savings to review

See which resources may be unused and estimate the potential savings before making changes.

Scheduled checks

Scans run on a schedule using Lambda and Cloud Functions. Configure the scope and review results as part of your cost checks.

A view across both clouds

Use the AWS scanner and Google Cloud recommender modules for the environments you run.

Review before cleanup

Use dry-run reports and resource exclusions to check the cleanup scope before enabling removal.

Built with

Python 3.12 Terraform AWS Lambda GCP Cloud Functions Slack API AWS SES CloudWatch Cloud Scheduler

A few things you might be wondering

What cloud providers does FinOps Guardian support?
FinOps Guardian supports both Amazon Web Services (AWS) and Google Cloud Platform (GCP), providing unified cost optimization across both environments.
Is FinOps Guardian free to use?
The code is free under the MIT license. You deploy it in your own accounts and pay the cloud provider for the resources it uses.
How does FinOps Guardian detect idle resources?
On AWS, it checks resource usage and attachment status through AWS APIs. On Google Cloud, it reads Recommender API findings for VMs, disks, IPs, and databases.
Can I try it without deleting anything?
Yes. The AWS cleanup tool has a dry-run mode that reports proposed removals without deleting resources. Review those results before enabling cleanup.
What programming language is FinOps Guardian written in?
FinOps Guardian is written in Python 3.12. The GCP module has 92% test coverage with pytest.

A good place to start

Run FinOps Guardian in your environment.

Start with the repository’s setup guide. If you’d like help adapting it to your environment, talk to us about what you need.