About Us
The story of ThirdPatch
ThirdPatch was born out of a desire to create a third-party patching solution that actually works for MSPs.
MSPs need to meet many unique client requirements, and some of them conflict. A single global policy certainly won’t work, but convoluted approval structures aren’t ideal either—especially if they require a lot of maintenance.
We surveyed a group of MSPs as we were building ThirdPatch, and most providers in the industry just want to look at an endpoint and have it patch its third-party apps. Keeping browsers and other apps patched is important, but the industry consensus is that it should “just work” and not require a lot of maintenance (or unreliable software agents, or yet another portal for techs to log into).
We took all of this into account when building ThirdPatch. While we can’t deny the laws of physics (or computer science), the Pro version of ThirdPatch installs with one line of PowerShell, and it optionally can discover and patch the existing applications on a system. Designed to be RMM-neutral, ThirdPatch can be integrated with any RMM or management tool that can run shell commands.
Created by a former RMM admin who managed 10,000 endpoints, ThirdPatch is designed to do one thing well: seamlessly patch third-party applications.
What Makes ThirdPatch Different?
ThirdPatch is packaged-based, meaning it’s designed to create reusable Lego blocks of automation. Typically each client has their third party apps, along with the MSP base software. With ThirdPatch you can put packages in packages (just like physical boxes) and with a one-line command you can deploy or update all the associated software (everything from browsers to VPN clients to config files).
I’ve Never Used Packages Before. Is It Hard?
Not at all! We have playbooks and templates created, so you can be deploying software within minutes. We have great documentation, and it should be a matter of copy/paste/go — but we also have responsive support if you do need help.
How Does Custom Application Support Work?
A custom package will need to be made for the application. We provide templates; as long as the application has silent install parameters it can be deployed with ThirdPatch. This allows MSPs to deploy it in a centralized, automated fashion and leverage versioning and reporting as well.
