mirror of
https://github.com/fleetdm/fleet
synced 2026-05-24 09:28:54 +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.
63 lines
2.8 KiB
Markdown
63 lines
2.8 KiB
Markdown
# Design platform company adopts GitOps device management with Fleet
|
||
|
||
A design and collaboration platform company supports a distributed workforce of designers, engineers, and product teams. Its environment includes macOS devices, Linux development systems, and BYOD endpoints.
|
||
|
||
Fleet helps the company move toward a GitOps-first model for device management.
|
||
|
||
## At a glance
|
||
|
||
* **Industry:** Design and collaboration software
|
||
* **Devices managed:** ~2,500 macOS devices plus Linux and BYOD
|
||
* **Primary requirements:** GitOps workflows, osquery visibility, scalable migration
|
||
* **Previous challenge:** Rigid tools and fragmented multi-OS management
|
||
|
||
## The challenge
|
||
|
||
Before Fleet, the company relied on tools that were difficult to integrate with modern infrastructure workflows.
|
||
|
||
API limitations and complex configuration management made it hard to adopt an infrastructure-as-code approach. Managing multiple operating systems also required separate workflows, which added complexity.
|
||
|
||
The team wanted a more flexible system that aligned with its development practices.
|
||
|
||
## The evaluation criteria
|
||
|
||
The team focused on three priorities:
|
||
|
||
1. **GitOps and infrastructure-as-code**
|
||
Manage device state through pull requests and commits.
|
||
2. **osquery integration**
|
||
Use real-time data for compliance and analysis.
|
||
3. **Scalable migration**
|
||
Move thousands of devices without disruption.
|
||
|
||
## The solution
|
||
|
||
Fleet gave the team a platform that fits its engineering workflows.
|
||
|
||
The company now manages policies through GitOps and uses Fleet’s API to automate configuration. This replaces brittle workflows from previous tools with a more stable, code-driven system.
|
||
|
||
Fleet’s transparency also helps build trust with employees by clearly showing what data is collected and how devices are managed.
|
||
|
||
## The results
|
||
|
||
Fleet improved both scalability and developer experience.
|
||
|
||
* **Simpler workflows:** Device management now aligns with existing development practices.
|
||
* **Better visibility:** Real-time data improves monitoring and response.
|
||
* **Reduced tool sprawl:** Multiple tools are replaced with one platform.
|
||
|
||
## Why they recommend Fleet
|
||
|
||
For this company, the biggest benefit is GitOps-first management.
|
||
|
||
Fleet allows the team to manage devices the same way they build software, through code, automation, and real-time data.
|
||
|
||
|
||
<meta name="articleTitle" value="Design platform company adopts GitOps device management with Fleet">
|
||
<meta name="authorFullName" value="Irena Reedy">
|
||
<meta name="authorGitHubUsername" value="irenareedy">
|
||
<meta name="category" value="case study">
|
||
<meta name="publishedOn" value="2026-03-31">
|
||
<meta name="description" value="Fleet helps a design platform company manage devices through GitOps workflows and real-time visibility.">
|
||
<meta name="useBasicArticleTemplate" value="true">
|
||
<meta name="cardTitleForCustomersPage" value="Design platform">
|