Viktor.comAn AI coworker that actually does the work
Promoted
AWS Cost Guard
Stop wasting 40% of your AWS spend — in minutes
32 followers
Stop wasting 40% of your AWS spend — in minutes
32 followers
Identify wasted AWS spend and oversized resources with one-click AI analysis.
Hey Product Hunt 👋
I'm Guido, solo-founder of **AWS Cost Guard** — the simplest way to uncover wasted AWS spend using AI.
💸 My real-life experience:
I've been working with AWS for over 13 years. It's an incredible platform — powerful, flexible, full of possibilities.
But that same power comes with a hidden side effect: over time, you test, duplicate, over-provision, change strategies… and forget.
Little things that seem harmless — $10 here, $100 there, a few idle volumes, old snapshots, or oversized instances — quietly pile up.
Month after month, they turn into massive recurring costs.
That’s why I built **AWS Cost Guard** — first for myself, and now for anyone facing the same invisible waste.
I wanted to make cloud optimization effortless — no agents, no scripts, no consulting calls.
In just 3 simple steps, you get an intelligent, secure analysis of your AWS infrastructure and a list of *concrete saving opportunities*.
1️⃣ Copy a read-only IAM policy
2️⃣ Create a new AWS user with minimal permissions
3️⃣ Connect & Analyze — AI does the rest
⚙️ What you’ll get:
- Full analysis of unused or oversized AWS resources
- Actionable saving recommendations (by % and $)
- Secure, read-only connection — zero risk to your infra
- Dashboard with estimated total savings
💬 Why now?
Leading global consulting firms (KPMG, McKinsey, Flexera) estimate that **30–40% of all cloud spend is wasted** every year.
I wanted to build something that brings those savings *within reach of every company*, not just those who can afford enterprise consultants.
💡 **My sustainability model:**
AWS Cost Guard doesn’t rely on subscriptions or hidden fees.
Instead, I ask for a *one-time contribution equal to 10%* of the **monthly savings identified** by your AI audit.
If you save $1,000, you invest $100 — and that’s it.
🎁 **Launch offer:**
For this Product Hunt launch, the **first 50 users** can use a special coupon to get their *first AI audit at 90% off*.
The coupon to apply at checkout is: PHNOAWSWASTE — once the 200 uses are gone, they’re gone.
I’d love to hear your thoughts:
👉 What’s your biggest cloud cost challenge right now?
👉 How do you currently track unused AWS resources?
I’ll be here all day to answer, brainstorm, and learn from your experiences. 🙌
— Guido
Solo-Founder, AWS Cost Guard
Really interesting approach. Does AWS Cost Guard use CloudWatch metrics for EC2 rightsizing recommendations, or do you rely only on configuration data (instance type, size, etc.)? Does it take into consideration AWS resources utilization ?
@new_user___2962025ea2425ebda32b62f thanks man! Yep we definitely take into consideration AWS resource utilization, mostly memory and CPU consumption/activity!
In what way does this go beyond Compute Optimizer / Cost Explorer? They give right-size tips already, so what’s the “plus” with Cost Guard?
@alessio_de_pinto well, AWS gives you lots of details, that I finds confusing more than often. WIth AWS Cost Guard I wanted to turn that into clear, low-risk actions and explains the “Others” blob that commonly is shown in the Cost reports of AWS. Less confusion, fewer over-aggressive recs, more savings you can actually ship.
Super interesting idea, Guido. Quick question — how safe is the AWS connection? I’m always a bit cautious about third-party audits.
@karen_d3 Great question — security is top priority! 🔒
The tool uses read-only IAM permissions (you can verify the policy before connecting). Your AWS credentials are encrypted at rest using AES-256-GCM and never stored in plain text.
This means that AWS Cost Guard cannot perform any write operations — just analyze your resources via AWS APIs. Other than that, you stay in full control: revoke access anytime by deleting the IAM user from your AWS console.
Well done. First pass was quick and packed with detail. Quick check: does the audit only surface idle resources, or will it also call out over-provisioned environments?
@giodomy Hey! Thanks! 🙏 Glad you tried it.
The audit goes much deeper than just spotting idle instances. We analyze:
Compute:
EC2 rightsizing via CloudWatch CPU metrics (catches over-provisioned instances)
Reserved Instance & Spot opportunities
Instance type optimization
Storage:
EBS: unattached volumes, excessive snapshots
S3: lifecycle gaps, versioning waste
AMI: old custom images, AWS Backup over-retention
Database (RDS):
Over-provisioned instances (low CPU/connections)
gp2→gp3 migration savings
Snapshot retention issues
Networking:
Idle Load Balancers & NAT Gateways
All findings include savings estimates and actionable recommendations. The system uses actual CloudWatch metrics to detect waste—not just guesswork! 📊
I’ve done a few AWS cost reviews myself—every time there are “forgotten” RDS snapshots and zombie volumes lurking around. Love that this tool basically does that hunting for you.
@mmorselli1 thanks! Yeah that's the reason why behind this tool! If you spot any improvement while using the tool for your pupose, reach out to me!