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

3.7 KiB

Raw Blame History

Technology platform manages 15,000 iPads with Fleet

A global technology company operates a platform that connects consumers with local businesses. Its ecosystem includes a large network of devices used by employees and partner businesses.

To support this infrastructure, the company manages a massive mobile fleet of iPads alongside its corporate macOS devices.

As the fleet grows, the team needs a more scalable way to manage devices using automation and version-controlled workflows.

At a glance

Industry: Technology platform services
Devices managed: ~15,000 iPads plus corporate macOS devices
Primary requirements: GitOps workflows, API-first management, Apple Business Manager integration
Previous challenge: Manual enrollment processes and limited automation

The challenge

Managing 15,000 mobile devices introduces operational complexity.

The company relies on tools such as Workspace ONE and Jamf. These systems depend heavily on graphical interfaces and manual configuration processes.

Device enrollment and configuration require significant manual effort. Configuration changes lack peer review and version control, which makes collaboration difficult.

The team wants to manage devices using the same engineering practices they use for software development.

The evaluation criteria

Fleet must meet three key requirements:

GitOps workflows
Integrate with GitHub Enterprise for version-controlled device management.
Apple Business Manager integration
Seamlessly manage large numbers of iPads.
API-first management
Allow automation of all device management tasks.

The solution

Fleet allows the company to treat device management like software development.

Device configurations live in version-controlled repositories. Changes go through peer review before deployment.

Fleet’s API powers several automated workflows. For example, device names synchronize automatically with the company’s inventory system, ensuring records remain accurate without manual updates.

Fleet also integrates with Apple Business Manager to automate provisioning of new devices.

A flexible migration strategy

Migration speed varied by device type.

Some device cohorts transitioned in as little as 17 days. macOS systems moved through user-initiated enrollment, while iPads underwent a clean provisioning process.

This approach allowed the organization to expand Fleet adoption without disrupting operations.

The results

Fleet introduced version control and peer review into device management workflows.

Instead of relying on manual configuration through graphical interfaces, teams collaborated on device policies through code.

This approach reduced configuration errors and improved operational reliability.

Fleet also provided a unified platform for managing devices, allowing the IT team to operate efficiently despite the scale of the fleet.

Their recommendation focuses on alignment with modern engineering practices.

Organizations that already rely on version control and CI/CD workflows extend those same practices to device management with Fleet.

3.7 KiB Raw Blame History Unescape Escape