Update it-platform-provider.md (#44783)
This commit is contained in:
@@ -1,27 +1,47 @@
|
||||
# IT platform provider automates patching across thousands of Mac, Windows, and Linux devices
|
||||
|
||||
An all-in-one platform for identity, MDM, and procurement needed a programmable layer to serve as the "secret weapon" for their own automated services.
|
||||
An all-in-one platform for identity, MDM, and procurement needed a programmable layer to serve as the "secret weapon" for their own automated services. With thousands of cross-platform devices to keep patched and compliant — and a growing set of customer-facing automations to power — the team needed an API-first system to build on.
|
||||
|
||||
Fleet helped the company replace ManageEngine with a unified, GitOps-driven approach to patching and device telemetry across Mac, Windows, and Linux.
|
||||
|
||||
## At a glance
|
||||
|
||||
- **Endpoints:** thousands across managed accounts
|
||||
- **Primary requirement:** robust API and patch management automation.
|
||||
- **Key integrations:** Brew and Winget.
|
||||
- **Previous solution:** manual, "point-and-click" workflows.
|
||||
- **Endpoints:** thousands across managed accounts
|
||||
- **Primary requirement:** robust API and patch management automation
|
||||
- **Key integrations:** Brew and Winget
|
||||
- **Previous solution:** ManageEngine
|
||||
|
||||
## The challenge
|
||||
|
||||
Managing cross-platform patches and verifying device states in real-time was a significant hurdle before integrating Fleet.
|
||||
Before Fleet, the company relied on ManageEngine to handle cross-platform patches and verify device state. As the platform's automation ambitions grew, the team needed a more programmable foundation—one they could plug directly into the customer-facing services they were building, rather than a separate system to operate alongside them.
|
||||
|
||||
Managing cross-platform patches and verifying device state in real time across thousands of endpoints was a significant hurdle, especially when reliable, programmatic device data needed to feed automation downstream.
|
||||
|
||||
## The evaluation criteria
|
||||
|
||||
The team focused on three priorities:
|
||||
|
||||
1. **Robust, GitOps-friendly API** — Drive patching and configuration through version-controlled, programmatic changes.
|
||||
2. **Cross-platform package management** — Native integration with Brew and Winget to manage software consistently across Mac, Windows, and Linux.
|
||||
3. **Real-time device telemetry** — Verify device state instantly to power downstream automation and remediation.
|
||||
|
||||
## The solution
|
||||
|
||||
They chose Fleet for its deep GitOps integration, allowing them to build their own automation and patching logic on a secure, auditable foundation. They utilize a unified system to manage Mac, Windows, and Linux via tools like Brew and Winget.
|
||||
Fleet gave the team a programmable layer they could build on. Its deep GitOps integration allowed the company to develop its own automation and patching logic on a secure, auditable foundation, while a unified system manages Mac, Windows, and Linux through tools like Brew and Winget.
|
||||
|
||||
By using Fleet's API, the team drives patching and device verification programmatically, making real-time device state a first-class input to their internal automation pipelines rather than something that has to be polled or manually chased down.
|
||||
|
||||
## The results
|
||||
|
||||
- **Automated app patching:** Using the API, they programmatically updates fleet-maintained apps via GitOps.
|
||||
- **Consolidated stack:** Consolidation allowed them to replace 4+ legacy tools with one system, reducing vendor sprawl.
|
||||
- **AI-driven insights:** Real-time telemetry is fed into their own orchestration engine to proactively detect and remediate issues.
|
||||
Fleet improved automation, consolidation, and operational efficiency.
|
||||
|
||||
- **Automated app patching:** Using the API, the team programmatically updates Fleet-maintained apps via GitOps.
|
||||
- **Consolidated stack:** Replaced 4+ legacy tools with one system, reducing vendor sprawl.
|
||||
- **Real-time device telemetry:** Live device data is available to the team's internal systems for proactive monitoring and remediation across the fleet.
|
||||
|
||||
## Why Fleet
|
||||
|
||||
For this company, the key advantage is having a programmable, API-first platform they can wire directly into their own services. Fleet provides the GitOps foundation and cross-platform telemetry needed to deliver automated patching and device verification at the scale their customers expect.
|
||||
|
||||
|
||||
<meta name="articleTitle" value="IT platform provider automates patching across thousands of Mac, Windows, and Linux devices">
|
||||
@@ -31,4 +51,4 @@ They chose Fleet for its deep GitOps integration, allowing them to build their o
|
||||
<meta name="publishedOn" value="2026-02-22">
|
||||
<meta name="description" value="An IT platform provider used Fleet and GitOps to automate patching, unify Mac, Windows, and Linux, and replace legacy tools.">
|
||||
<meta name="useBasicArticleTemplate" value="true">
|
||||
<meta name="cardTitleForCustomersPage" value="IT platform provider">
|
||||
<meta name="cardTitleForCustomersPage" value="IT platform provider">
|
||||
|
||||
Reference in New Issue
Block a user