Built by people who have spent their careers in endpoint management

Why we built Patchblox

On July 19, 2024, a faulty update from a security vendor crashed about 8.5 million Windows devices. Flights were grounded, and hospitals and banks were disrupted. One insurer estimated the direct losses for the US Fortune 500 alone at $5.4 billion.

It wasn't a story about one vendor. Any update from any vendor can fail that way, and eventually one will. What struck me was how many organizations had no way to stage an update, watch what it did on a small group of machines, and stop it before it reached everything else. After more than thirty years of building tools in this space, that told me the tools still weren't doing their job.

There was a second lesson. The software that patches and configures your endpoints is the most privileged software most companies run. It can change every device you own, which makes it a target, and attackers know it.

So we built Patchblox around two ideas. Know the real state of every endpoint, with evidence rather than a status flag, and change it deliberately: in stages, with health checks and a way to stop. And build the platform so a compromise is hard and contained: a certificate authority for each customer, signed scripts and tasks, agents that only connect outbound, no standing write access to your Microsoft tenant, and the option to run all of it in your own environment.

Dave Gayler Co-founder, CEO and CTO