Andrew McCarron

Andrew McCarron

Founder @ Koalr. Deploy risk scoring.
All activity
Andrew McCarronstarted a discussion

Launched today. Koalr β€” deployment risk scoring for every PR, before it merges

Hey everyone β€” Andrew here, founder of Koalr. We just launched. Koalr scores every pull request 0–100 for production risk before it ships. It uses 36 research based signals β€” things like file change blast radius, author expertise drift, CODEOWNERS violations, CI history, and time-of-week patterns β€” to flag risky deploys before they become 2am incidents. It connects to GitHub in minutes, no code...

Koalr is the Deployment Intelligenceβ„’ Platform β€” we score every one of your PR's 0–100 using 36 research validated signals before you merge. Predict & prevent production incidents before they happen.
Koalr
KoalrPredict deployment failures before your PR merges!
Andrew McCarronstarted a discussion

I'm Andrew, founder of Koalr β€” AMA about what actually predicts production failures

Hey PH πŸ‘‹ I'm Andrew, founder of Koalr β€” a deployment intelligence platform that scores every PR 0–100 for production risk before it merges. The idea came from 20 years in IT consulting and delivery. I've sat in more post-incident reviews than I can count, and the pattern is almost always the same: someone merged something on a Friday, nobody flagged it, and the team spent the weekend...

Andrew McCarronstarted a discussion

What signals do you actually check before merging a high-stakes PR?

Most teams have an informal mental checklist β€” PR size, who wrote it, whether tests passed, time of day. But it's rarely written down, and it varies by person. Curious what signals matter most to your team before you merge something you're nervous about. Is it coverage? CODEOWNERS sign-off? Who's on call? Something else entirely?