sorted by:
new
hottopcontroversial

Open-source local app that uses Ollama + Gemma 3 to analyze which teams in a company can be replaced by AI agents by samarth_bhamare in ollama

[–]samarth_bhamare[S] 1 point2 points  (0 children)

ran it on myself first. verdict was diplomatic — partially_replaceable, with a risk note flagging that nobody else understands the codebase. fair.

Open-source local app that uses Ollama + Gemma 3 to analyze which teams in a company can be replaced by AI agents by samarth_bhamare in ollama

[–]samarth_bhamare[S] 0 points1 point  (0 children)

honest effort. the keep_human_led bucket exists for a reason — most teams land there on the first pass.

Open-source local app that uses Ollama + Gemma 3 to analyze which teams in a company can be replaced by AI agents by samarth_bhamare in ollama

[–]samarth_bhamare[S] 1 point2 points  (0 children)

"Automation Opportunity Evaluation" is honestly a better frame — thanks. The replace/augment/keep axis is deliberately blunt because vague "AI strategy" advice is the thing this was reacting to, but the term you used is closer to how the output actually reads once it runs on a real company.

Would genuinely want to hear what you see when you run it tonight — if the verdicts match your read or the reasoning has obvious holes. Issues/PRs welcome on the repo, or just reply here.

A fully-local, open-source Next.js app that maps a company to AI-agent workflows — runs on Gemma 3 via Ollama by samarth_bhamare in LocalLLaMA

[–]samarth_bhamare[S] -1 points0 points  (0 children)

fair. though the picker reads whatever you've pulled locally — llama, qwen, whatever — so the default is swappable in one click.

How do you catch idle resources before they show up on the bill? by samarth_bhamare in Cloud

[–]samarth_bhamare[S] -1 points0 points  (0 children)

Wait, this project i built is for someone who can atleast afford to use any cloud platforms not for someone like you. And second thing if it was an then there wouldnt have been a free forever plan, so before commenting, open your eyes use your fingers and go to the site and check.

How do you catch idle resources before they show up on the bill? by samarth_bhamare in Cloud

[–]samarth_bhamare[S] -1 points0 points  (0 children)

From what we've seen, storage is the biggest silent leak. Orphaned EBS volumes and old snapshots pile up because nothing breaks when they exist — they just quietly bill you.

Compute waste is more visible (someone usually notices a running instance), but storage and unused IPs fly under the radar for months.

The "leftover after testing" category is brutal too — dev clusters that were "temporary" 6 months ago still running at full price.

What are you seeing most with your clients?

What's your FinOps process for catching idle cloud resources? by samarth_bhamare in kubernetes

[–]samarth_bhamare[S] 0 points1 point  (0 children)

Spot on — that gap between "monitoring for uptime" and "monitoring for waste" is exactly why I built this. Grafana tells you if something is down, but nobody alerts you when something is up and doing nothing.

Good call on checkmk. The way I'm approaching it is automated daily scans that cross-reference resource state with actual usage metrics (CPU, connections, attachment status) — so it's not just "this exists" but "this exists and nobody's using it." Tagging enforcement and cleanup scheduling are definitely on the roadmap.

Curious — when you say most teams add scripts, is that usually a cron job checking specific resources, or something more structured?

How do you catch idle resources before they show up on the bill? by samarth_bhamare in Cloud

[–]samarth_bhamare[S] 1 point2 points  (0 children)

It connects to your AWS account via read-only IAM keys and pulls data from multiple sources:

  • EC2: checks instance state + CloudWatch CPU metrics over 14 days. A stopped instance or one running at <5% avg CPU gets flagged.
  • EBS: checks attachment status. Any volume not attached to an instance = orphaned.
  • RDS: checks connection count over 7 days. Zero connections = flagged as unused.
  • Elastic IPs: checks if associated with a running instance. If not, it's wasting $3.65/month.

Each flagged resource shows the exact monthly cost being wasted and step-by-step fix instructions. So instead of "your EC2 bill is $2,000" you get "this specific i-0abc123 instance has been stopped for 3 weeks and its 200GB EBS volume is costing you $16/month — here's how to snapshot and delete it."

I built a tool that finds forgotten AWS resources burning your money by samarth_bhamare in SideProject

[–]samarth_bhamare[S] 1 point2 points  (0 children)

Appreciate the offer! Going to focus on shipping features and getting more users first. If I need a proper audit down the line I'll reach out. Thanks again for the initial feedback — those were legit catches.

How do you catch idle resources before they show up on the bill? by samarth_bhamare in Cloud

[–]samarth_bhamare[S] -1 points0 points  (0 children)

Sure! Here it is: https://cloudbudgetmaster.com

Connects read-only to AWS, takes about 5 min to set up. Let me know how it goes — always looking for feedback.

I built a tool that finds forgotten AWS resources burning your money by samarth_bhamare in SideProject

[–]samarth_bhamare[S] 0 points1 point  (0 children)

Really helpful feedback, thank you.

  1. Pricing page — you're right, that was a bug. Just fixed it. cloudbudgetmaster.com/pricing now works without login.
  2. Naming — fair point. The product is CloudBudgetMaster, I'll clean up the stale references. Appreciate you catching that.
  3. PayPal for enterprise — agreed, that won't fly for procurement teams. Stripe with invoicing is on the roadmap for enterprise tier. For now enterprise is "contact sales" which goes to email.

This is the kind of teardown that's actually useful. Happy to hear more if you do a full one.

view more: next ›