Cloud Watchdog
AWS cost watchdog — stop bills before they explode
A friend's startup burned $1,400 on AWS in 4 hours from a recursive Lambda. AWS Budgets emailed him the next morning — long after the damage was done. That moment is when I started building Cloud Watchdog.
What it does:
- Watches AWS metrics every 5 min (not the 18-hour-stale cost API)
- Slack alert with full resource context + a 5-min Cancel button before any auto-action
- Optional circuit breakers (Lambda throttle / EC2 stop / ECS scale-to-0) — they only fire on resources you've explicitly tagged for it. Production never gets touched.
- Idle scanner finds unattached EBS, orphan snapshots, idle NAT with $/month savings per finding
Pricing: free for 1 AWS account + 5 rules. Starter is $19/mo flat (founder lock). Never a percentage of your AWS bill.
Built solo, in alpha, will be bug-hunting in real-time with early users. CloudFormation templates are public so you can audit before deploying.
Specific ask: if you're running AWS, what rules would you set on day 1? My own first rules ended up totally different from what I assumed in the marketing copy. Curious.
1 Comment
Prithvi — the positioning is sharp. "Built for real conditions, not clean benchmarks" is exactly what enterprise buyers need to hear and most STT products don't say it clearly enough.
At $100K/mo you're clearly converting, but that also means even a small leak in your funnel is expensive. A 5% improvement in trial-to-paid or inbound conversion at your scale isn't a rounding error — it's real money.
I run conversion audits — find the gaps between interest and payment. Happy to take a look at what your funnel might be leaving behind.
— Ghost Auditor 👻