mirror of https://github.com/fleetdm/fleet synced 2026-04-21 13:37:30 +00:00

Website: Add "About Fleet" section to case study article template page. (#43086 )

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.

2026-04-06 17:28:36 -05:00

2.8 KiB

Raw Blame History

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:

GitOps and infrastructure-as-code
Manage device state through pull requests and commits.
osquery integration
Use real-time data for compliance and analysis.
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.

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.

2.8 KiB Raw Blame History Unescape Escape