{
  "schema_version": 1,
  "kind": "product",
  "title": "FinOps Guardian",
  "description": "Find idle AWS and Google Cloud resources with FinOps Guardian. Scheduled scans, Slack reports, and dry-run AWS cleanup. Open-source code on GitHub.",
  "url": "https://cloudon-one.com/products/finops-guardian",
  "markdown_url": "https://cloudon-one.com/products/finops-guardian.md",
  "json_url": "https://cloudon-one.com/products/finops-guardian.json",
  "language": "en",
  "author": {
    "type": "Organization",
    "name": "CloudOn",
    "url": "https://cloudon-one.com/"
  },
  "rights_url": "https://cloudon-one.com/terms",
  "indexable": true,
  "headings": [
    {
      "level": 2,
      "text": "What it does"
    },
    {
      "level": 2,
      "text": "What’s included",
      "id": "features-heading",
      "url": "https://cloudon-one.com/products/finops-guardian#features-heading"
    },
    {
      "level": 3,
      "text": "AWS Resource Cleanup"
    },
    {
      "level": 3,
      "text": "GCP FinOps Recommender"
    },
    {
      "level": 3,
      "text": "Slack and email reports"
    },
    {
      "level": 2,
      "text": "Getting it running",
      "id": "how-heading",
      "url": "https://cloudon-one.com/products/finops-guardian#how-heading"
    },
    {
      "level": 3,
      "text": "Deploy with Terraform"
    },
    {
      "level": 3,
      "text": "Automated Scanning"
    },
    {
      "level": 3,
      "text": "Review Recommendations"
    },
    {
      "level": 3,
      "text": "Review cleanup actions"
    },
    {
      "level": 2,
      "text": "What it helps with",
      "id": "benefits-heading",
      "url": "https://cloudon-one.com/products/finops-guardian#benefits-heading"
    },
    {
      "level": 3,
      "text": "Find savings to review"
    },
    {
      "level": 3,
      "text": "Scheduled checks"
    },
    {
      "level": 3,
      "text": "A view across both clouds"
    },
    {
      "level": 3,
      "text": "Review before cleanup"
    },
    {
      "level": 2,
      "text": "Built with",
      "id": "tech-heading",
      "url": "https://cloudon-one.com/products/finops-guardian#tech-heading"
    },
    {
      "level": 2,
      "text": "A few things you might be wondering",
      "id": "faq-heading",
      "url": "https://cloudon-one.com/products/finops-guardian#faq-heading"
    },
    {
      "level": 2,
      "text": "From the blog",
      "id": "blog-heading",
      "url": "https://cloudon-one.com/products/finops-guardian#blog-heading"
    },
    {
      "level": 3,
      "text": "Finding idle Google Cloud resources with FinOps Guardian"
    },
    {
      "level": 3,
      "text": "Finding unused AWS resources with FinOps Guardian"
    },
    {
      "level": 2,
      "text": "Other CloudOn Tools",
      "id": "related-heading",
      "url": "https://cloudon-one.com/products/finops-guardian#related-heading"
    },
    {
      "level": 3,
      "text": "Multi-Cloud Runway"
    },
    {
      "level": 3,
      "text": "KubeLaunch"
    },
    {
      "level": 3,
      "text": "SecureOps"
    },
    {
      "level": 2,
      "text": "Run FinOps Guardian in your environment."
    }
  ],
  "code_repository": "https://github.com/cloudon-one/FinOps-Guardian",
  "code_license": "MIT",
  "content_markdown": "---\ntitle: FinOps Guardian\ndescription: Find idle AWS and Google Cloud resources with FinOps Guardian. Scheduled scans, Slack reports, and dry-run AWS cleanup. Open-source code on GitHub.\nurl: https://cloudon-one.com/products/finops-guardian\nauthor: CloudOn\nlanguage: en\nrights_url: https://cloudon-one.com/terms\ncode_repository: https://github.com/cloudon-one/FinOps-Guardian\ncode_license: MIT\n---\n\nThe open-source toolkit\n\n# FinOps Guardian\n\nFind unused resources. Understand where your cloud budget goes.\n\nOpen source MIT license \n\n[View on GitHub](https://github.com/cloudon-one/FinOps-Guardian) [Get a hand setting it up](https://cloudon-one.com/contact)\n\n## What it does\n\nFinOps 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.\n\n## What’s included\n\n### AWS Resource Cleanup\n\nAutomated Lambda-based tool that identifies and removes unused AWS infrastructure across multiple regions.\n\n-   Scans EC2, EBS, EIPs, ALBs, RDS, EKS, Kinesis, MSK, OpenSearch \n-   Operates across 7+ configurable AWS regions \n-   Dry-run mode for safe evaluation before deletion \n-   Scheduled nightly via CloudWatch Events \n\n### GCP FinOps Recommender\n\nUses Google Cloud’s Recommender API to find idle resources and sizing recommendations.\n\n-   Detects 10 recommender types: idle VMs, disks, IPs, SQL \n-   Right-sizing for VM instances and Managed Instance Groups \n-   Organization-level and project-level scanning \n-   Cost impact metrics with configurable thresholds \n\n### Slack and email reports\n\nSend scan results and estimated cost impact to your team’s Slack channel or email.\n\n-   Slack integration with cost impact details \n-   Email reports via AWS SES \n-   Configurable alert thresholds \n-   Audit logs for scan and cleanup activity \n\n## Getting it running\n\n01\n\n### Deploy with Terraform\n\nUse the provided Terraform modules to deploy FinOps Guardian in your AWS and GCP environments.\n\n02\n\n### Automated Scanning\n\nServerless functions run on schedule, scanning your cloud accounts for idle and underutilized resources.\n\n03\n\n### Review Recommendations\n\nReceive Slack notifications and email reports with cost-saving opportunities and their estimated impact.\n\n04\n\n### Review cleanup actions\n\nUse dry-run mode to preview cleanup actions, then enable automated resource removal when ready.\n\n## What it helps with\n\n### Find savings to review\n\nSee which resources may be unused and estimate the potential savings before making changes.\n\n### Scheduled checks\n\nScans run on a schedule using Lambda and Cloud Functions. Configure the scope and review results as part of your cost checks.\n\n### A view across both clouds\n\nUse the AWS scanner and Google Cloud recommender modules for the environments you run.\n\n### Review before cleanup\n\nUse dry-run reports and resource exclusions to check the cleanup scope before enabling removal.\n\n## Built with\n\nPython 3.12  Terraform  AWS Lambda  GCP Cloud Functions  Slack API  AWS SES  CloudWatch  Cloud Scheduler \n\n## A few things you might be wondering\n\nWhat cloud providers does FinOps Guardian support? \n\nFinOps Guardian supports both Amazon Web Services (AWS) and Google Cloud Platform (GCP), providing unified cost optimization across both environments.\n\nIs FinOps Guardian free to use? \n\nThe code is free under the MIT license. You deploy it in your own accounts and pay the cloud provider for the resources it uses.\n\nHow does FinOps Guardian detect idle resources? \n\nOn 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.\n\nCan I try it without deleting anything? \n\nYes. The AWS cleanup tool has a dry-run mode that reports proposed removals without deleting resources. Review those results before enabling cleanup.\n\nWhat programming language is FinOps Guardian written in? \n\nFinOps Guardian is written in Python 3.12. The GCP module has 92% test coverage with pytest.\n\n## From the blog\n\n[13 Jan 2025\n\n### Finding idle Google Cloud resources with FinOps Guardian\n\nUse Google Cloud’s Recommender API to find idle resources and sizing recommendations, then send the findings to Slack.\n\nGCP FinOps Cost Optimization \n\nRead the article](https://cloudon-one.com/blog/cut-gcp-costs-finops-guard) [10 Jan 2025\n\n### Finding unused AWS resources with FinOps Guardian\n\nSet up scheduled AWS resource checks, review idle resources across regions, and test cleanup actions with dry-run reports.\n\nAWS FinOps Cost Optimization \n\nRead the article ](https://cloudon-one.com/blog/slash-aws-costs-finops-guardian)\n\n## Other CloudOn Tools\n\n[\n\nCloud foundations \n\n### Multi-Cloud Runway\n\nMulti-Cloud Runway provides Terraform and Terragrunt templates for cloud accounts, projects, networking, access, and security monitoring. Use the AWS or Google Cloud modules independently and adapt the structure to how your organization works.\n\nExplore the tool  Open source \n\n](https://cloudon-one.com/products/multi-cloud-runway)[\n\nKubernetes \n\n### KubeLaunch\n\nKubeLaunch brings together Terraform and Terragrunt configurations for AWS EKS, application delivery, security, and monitoring. It includes Argo CD, Kyverno, Falco, Istio, and Kubecost, with component settings you can adapt to your workloads.\n\nExplore the tool  Open source \n\n](https://cloudon-one.com/products/kubelaunch)[\n\nCode security \n\n### SecureOps\n\nSecureOps brings Gitleaks, Trivy, and OSV-Scanner into a GitHub Actions workflow. It scans for exposed secrets, vulnerable dependencies, and infrastructure configuration issues. Read findings in pull request comments or export JSON, HTML, and SARIF reports.\n\nExplore the tool  Open source \n\n](https://cloudon-one.com/products/secureops)\n\nA good place to start\n\n## Run FinOps Guardian in your environment.\n\nStart with the repository’s setup guide. If you’d like help adapting it to your environment, talk to us about what you need.\n\n[View on GitHub](https://github.com/cloudon-one/FinOps-Guardian) [Talk to an engineer](https://cloudon-one.com/contact)\n",
  "content_sha256": "6ae367eddd15cf618b383ca3b1c253feae435028c031c4361fc555428420f0b1"
}
