Claws
Claws to get you started
Watch vendor status pages
-
Watches your stack vendors' status pages every 15 minutes -
Maps each incident to your surface area and suppresses the irrelevant ones -
Hands over a ready-made customer-facing acknowledgement -
Drops resolved incidents and stays silent when nothing affects you
Digest known issues
-
Builds a daily known-issues digest from ticket patterns, vendor status, and the open-issue file -
Updates each ETA from engineering status notes in the drive -
Removes resolved issues automatically so the digest stays current -
Flags what is ready to publish to a public known-issues page
Draft incident follow-ups
-
Reads the incident log and builds a per-customer follow-up brief each evening -
Drafts the impact acknowledgement, remediation, and any applicable SLA credit -
Deprioritizes customers who already acknowledged it and escalates the un-updated -
Sends nothing to customers; the team reviews and sends
Probe endpoint uptime
-
Probes your public endpoints every five minutes for availability and latency -
Learns the normal pattern and pages only on real deviation -
Requires a deviation to persist before escalating, then notes recoveries -
Keeps a full record for the monthly uptime recap
Watch dependency bug trackers
-
Reads public issue trackers for your dependencies and vendor services -
Matches issues against your stack and the versions you rely on -
Elevates issues climbing in attention or with a fix in flight -
Sends nothing when no stack-relevant issue is moving
Watch vendor status incidents
-
Polls each vendor's public status feed every 15 minutes for new and updated incidents -
Maps each incident to your regions, services, and dependencies and suppresses the rest -
Escalates anything touching your production right away -
Keeps a full incident history that feeds the SLA credit claw each billing cycle
Draft SLA credit requests
-
Computes the SLA credit you are owed each month from contract terms and incident history -
Drafts the credit-request mail per vendor with incidents, durations, and percentages -
Runs once on the first business day of each month and gates itself the rest -
Asks for credits most vendors never surface unless prompted
Watch weather disruptions
-
Watches weather for your offices, key vendor data centers, and operational hubs -
Surfaces only events that would actually disrupt operations -
Carries the operational decision your playbook calls for per event class -
Pages on imminent threats to production-path locations
Track vendor SLA usage
-
Watches every vendor status page in your stack every 15 minutes -
Computes running SLA utilization per vendor per billing cycle against your contract terms -
Pages early when a vendor approaches breach so you can request proactive credits -
Stays silent on quiet days so alerts always mean something