Built by someone
who's been on-call.
Strake is built by Rob Newton — an SRE with 8+ years building and operating production infrastructure. The deploy gate is a pre-deploy safety check that tells your team whether it's safe to push. This isn't a tool built by someone who read about SRE. It's built by someone who's been paged at 3am.
Why Strake exists.
After years as an SRE at companies like FreightWaves, TextNow, and Pilot Flying J — managing large-scale Kubernetes clusters, implementing monitoring solutions, building CI/CD pipelines, and getting paged at 3am — I noticed the same pattern everywhere.
Teams without dedicated SREs were making deploy decisions based on gut feel and Slack messages. The tribal knowledge problem was real. The Notion runbook from 2021 was never opened. And every bad deploy started the same way: “I didn't think it was a risky change.”
Strake is the tool I wished I had on the other side — the deploy gate that tells your team whether it's safe to push, built by someone who knows what actually matters at 3am.
8+ years in the trenches.
Previously Staff SRE. Building the deploy gate I wished I had after 8 years of being the person who gets paged at 3am.
Managed large-scale Kubernetes clusters, all cloud infrastructure, Datadog, ArgoCD, GitHub Actions. Built CI/CD from scratch.
Implemented AppDynamics across the entire platform. Automated incident response strategies.
Major MySQL sharding rework. Terraformed all Datadog dashboards and monitors.
The gap no one fills.
Every incident management tool on the market assumes you already have SRE processes. PagerDuty, incident.io, FireHydrant, Rootly — they're built for teams with established practices.
But most engineering teams don't have that. They have an engineer who became the informal SRE, a Confluence page no one's opened in months, and a Slack channel called #deploy-questions.
Strake is built for those teams. Not to replace PagerDuty — to be the layer before it that prevents the page from ever happening. 43% of incidents are preceded by a recent deploy. Structured runbooks cut MTTR from 67 to 23 minutes. That's what a deploy gate does.
Want to talk about
deploy safety?
No sales script. No demo theater. Just a real conversation with the person building the tool.