I built a small open-source project called Watchy.
It monitors SaaS outages (starting with Slack + GitHub) inside your AWS account using CloudWatch.
Built for teams that want SaaS health visibility without another vendor.
https://t.co/urKUNBHPwQ
Watchy is live.
Open-source, AWS-native SaaS monitoring using CloudWatch.
• Slack + GitHub status & incidents
• Metrics, dashboards, alarms
• Serverless + CloudFormation
• Runs in your own AWS account
Deploy in ~2 minutes → https://t.co/B7Sp5iX9XT
@gustojs@kirodotdev I'm also using the Kiro IDE mostly, for daily workflows. I'm giving the CLI a shot more and more.
An AI agent-based GUI tends to be what I'm after the most. I want to a blend of AI chat/guidance experience while keeping code fully visible and editable in a large window.
SLA uptimes aren’t about precision, they’re about architecture.
• 99.9% ≈ 43 min / month
• 99.99% ≈ 4.3 min / month
• 99.999% ≈ 26 sec / month
Each extra “9” changes what your system must tolerate, not just how carefully you measure it.
One simple way to reduce your Amazon CloudWatch bill is to enable log retention.
Many customers use AWS services that write logs to log groups with retention set to "net expire".
At ~$0.03 per compressed GB, storing logs this way can add up to hidden costs.