mirror of
https://github.com/fleetdm/fleet
synced 2026-04-21 21:47:20 +00:00
b1ea2121da
Closes https://github.com/fleetdm/fleet/issues/41798 Changes: - Added an "About Fleet" section to the case study article template page. - Removed the "About Fleet" sections from case study articles. FYI @irenareedy: After this change is merged, you will not need to include an "About Fleet" section on new case study articles.
69 lines
No EOL
3.2 KiB
Markdown
69 lines
No EOL
3.2 KiB
Markdown
# Data platform company cuts $5–6M in hardware costs with API-driven device management
|
||
|
||
A global data platform company supports a large workforce across macOS, Windows, Linux, iOS, and Android. With device count matching its workforce, the team needed a scalable way to manage hardware, security, and compliance.
|
||
|
||
Fleet helps the company manage devices through APIs and stream endpoint telemetry directly into its own data platform.
|
||
|
||
## At a glance
|
||
|
||
* **Industry:** Data cloud technology
|
||
|
||
* **Devices managed:** ~10,000-11,000 devices
|
||
|
||
* **Primary requirements:** API and GitOps support, multi-OS management, real-time data streaming
|
||
|
||
* **Previous challenge:** Legacy tools were expensive and did not support Linux and BYOD well
|
||
|
||
## The challenge
|
||
|
||
Before Fleet, the company relied on tools that worked well for macOS but did not support Linux, Android, and BYOD with the same depth.
|
||
|
||
The team also wanted to move away from expensive licensing models and manual UI-driven workflows. Linux devices and BYOD systems were especially hard to manage, which limited visibility across the environment.
|
||
|
||
## The evaluation criteria
|
||
|
||
The team focused on three priorities:
|
||
|
||
1. **API and GitOps support**
|
||
Remove manual operations and manage workflows through code.
|
||
|
||
2. **Multi-OS management**
|
||
Support macOS, iOS, Android, Windows, and Linux from one platform.
|
||
|
||
3. **Real-time data streaming**
|
||
Send endpoint telemetry directly into the company’s internal data platform.
|
||
|
||
## The solution
|
||
|
||
Fleet provided the team with a platform that aligns with its API-first engineering model.
|
||
|
||
The company uses Fleet for asynchronous file verification and streams endpoint telemetry directly into its internal data environment. This allows security teams to query, model, and act on endpoint data within minutes.
|
||
|
||
Fleet inventory data also helps the company make better hardware decisions, including identifying overprovisioned devices and improving refresh planning.
|
||
|
||
## The results
|
||
|
||
Fleet improved both operational efficiency and cost control.
|
||
|
||
* **Major hardware savings:** Fleet data helped identify opportunities that saved an estimated $5-6 million in hardware costs.
|
||
|
||
* **Better multi-OS visibility:** Linux and BYOD systems now fit into the broader management strategy.
|
||
|
||
* **Faster security analysis:** Streaming telemetry shortens the gap between data collection and response.
|
||
|
||
## Why they recommend Fleet
|
||
|
||
For this company, the biggest benefit is API-driven efficiency.
|
||
|
||
Fleet gives the team one platform for automation, cross-platform management, and real-time endpoint data.
|
||
|
||
|
||
<meta name="articleTitle" value="Data platform company uses Fleet to cut costs and improve visibility">
|
||
<meta name="authorFullName" value="Irena Reedy">
|
||
<meta name="authorGitHubUsername" value="irenareedy">
|
||
<meta name="category" value="case study">
|
||
<meta name="publishedOn" value="2026-03-18">
|
||
<meta name="description" value="This data platform company uses Fleet to cut costs and improve visibility across macOS, Windows, Linux, and mobile devices.">
|
||
<meta name="useBasicArticleTemplate" value="true">
|
||
<meta name="cardTitleForCustomersPage" value="Data platform">
|
||
<meta name="cardBodyForCustomersPage" value="Data platform company cuts $5–6M in hardware costs with API-driven device management."> |