How CloudSlasher Works: 5-Stage Deterministic Safety Pipeline
- Non-Invasive Tenancy Ingestion: Zero-agent, read-only IAM scan maps running topology across compute instances, storage volumes, databases, and network gateways.
- FOCUS 1.0 Lakehouse Analytics: Normalizes billing records with sub-25ms vectorized DuckDB queries to identify idle and oversized resources.
- Interactive What-If Modeling: Compound multi-vector cost simulator reveals immediate and 12-month runway savings.
- Targeted Terraform Synthesizer: Generates declarative, reviewable HCL patches with automatic companion rollback modules.
- 1-Click GitOps Pull Request: Dispatches non-destructive PRs to your GitHub repository with zero direct-write access to production main branches.
Cloud & Infrastructure Support Matrix
| Cloud Platform | Supported Resource Types | Detection Scope | Remediation Mechanism | Auto-Delete Risk |
|---|---|---|---|---|
| Oracle Cloud (OCI) | Compute VMs, Autonomous DB (ATP/ADW), Block Volumes, NAT Gateways, Ephemeral IPs | Idle shapes, Always Free Ampere A1.Flex migration, DB ECPU conversion, Lower Cost VPU tiering | Tested Terraform HCL + GitOps Pull Request | 0% Risk (Strictly Read-Only) |
| Amazon Web Services (AWS) | EC2, EBS Volumes, RDS, Application Load Balancers, NAT Gateways | Overprovisioned instances, unattached gp2/gp3 volumes, idle ALBs | OpenTofu / Terraform Remediation PR | 0% Risk (Strictly Read-Only) |
| Microsoft Azure | Azure VMs, Managed Disks, Azure SQL, Public IP addresses | Unused standard disks, idle VM rightsizing | Declarative HCL Remediation Patch | 0% Risk (Strictly Read-Only) |
| Google Cloud (GCP) | Compute Engine, Persistent Disks, Cloud SQL | Zonal SSD rightsizing, idle instances | Terraform GitOps PR | 0% Risk (Strictly Read-Only) |
| Kubernetes (EKS/AKS/GKE/OKE) | Worker nodes, pod resource limits vs requests, PV claims | Oversized node pools, runaway container allocations | K8s manifest / Helm HCL patch | 0% Risk (Strictly Read-Only) |
How CloudSlasher Compares with Infracost and Auto-Delete Tools
- CloudSlasher vs. Infracost: Infracost operates shift-left inside CI/CD to estimate proposed cost diffs on pull requests. CloudSlasher operates post-deployment on live fleets to discover active waste that was already provisioned. They complement each other: Infracost guards your pipeline, while CloudSlasher continuously remediates live estate waste.
- CloudSlasher vs. CAST AI / Finout: Many tools require intrusive daemon agents and execute automated terminations that can cause production outages. CloudSlasher is 100% non-invasive, uses zero persistent credentials, and exports reviewable Terraform pull requests with safety branches and companion rollbacks.