CloudCull is an "Investor-Grade" autonomous governance framework designed to detect and eliminate GPU waste across AWS, Azure, and Google Cloud Platform. By 2026, it is the standard for multi-cloud cost optimization.
Startups and AI companies lose thousands of dollars every month because expensive GPU instances are left running idle. Manual tagging and spreadsheets are not enough to stop this bleeding.
CloudCull is not a dashboard; it is an Execution-First Sniper Agent. It proactively scans your multi-cloud environment, uses Multi-Model Intelligence (Claude/Gemini/Llama) to classify instance state, and provides a Kill-Switch to stop waste immediately.
CloudCull follows a robust, CLI-first automation flow designed for deep integration into DevOps pipelines.
graph LR
Trigger["Cron / GitHub Action"] --> Probe["Probe: Multi-Cloud SDKs"]
Probe --> Analyzer["Analyzer: Multi-Model AI"]
Analyzer -- "Decision: Zombie Identified" --> UI["UI: Approval Notification"]
UI -- "Approve" --> Execute["Execution: Boto3/SDK Terminate"]
- � High-Fidelity Brain: Pluggable AI (Claude 3.5, Gemini 1.5, Llama 3) for intelligent classification.
- 📡 Sniper Console: A technical Vite + React dashboard with AI Reasoning Callouts, Live Terminal Logs, and One-Tap Kill Actions.
- 👤 Identity Layer: Finds exactly who launched the instance for high-stakes accountability.
- 🛠️ IaC-Driven Remediation: Generates
terraform state rmplans instead of raw, risky deletions.
Note
CloudCull is a CLI-First Tool. The dashboard is a passive visualization layer.
git clone https://github.com/daretechie/cloudcull.git
cd cloudcull
uv syncuv run python main.py --simulated --dry-runTo run a real-world audit and trigger the automated remediation bundle:
uv run python main.py --region us-east-1 --active-opsCaution
--active-ops will generate remediation.sh and prompt for execution. Use with high-stakes environments after dry-run verification.
CloudCull is container-ready for consistent execution.
# Build & Run
docker build -t cloudcull .
docker run --env-file .env cloudcull --simulated --dry-rundocker-compose upTo enable the live dashboard, you must manually activate GitHub Pages in your repository settings:
- Go to Settings > Pages.
- Under Build and deployment > Source, select GitHub Actions.
- Architecture & System Design
- Design Principles & Rationale (Why we chose CLI-First & GitOps)
- Deployment Guide
- Developer Setup
- Dashboard Guide
- Operations Guide
This project is licensed under the MIT License.
