fleet/articles/open-source-technology-company.md
Eric b1ea2121da
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.1 KiB
Raw Blame History

Open-source technology company scales endpoint management with Fleet

A global technology company built around open-source software manages a large fleet of devices across macOS, Windows, and Linux. Its environment includes complex internal infrastructure and container platforms that require reliable scaling.

Fleet helps the company align endpoint management with the same open infrastructure principles it uses across the rest of its business.

At a glance

  • Industry: Open-source technology

  • Devices managed: ~20,000 devices

  • Primary requirements: Self-hosting, horizontal scaling, container platform support

  • Previous challenge: Enrollment consistency and large-scale migration complexity

The challenge

Before Fleet, the company faced challenges with enrollment consistency and infrastructure complexity.

Moving from legacy device management to a modern platform required a system that could handle large-scale rollout and run reliably inside its existing container-based infrastructure.

The team needed a platform that could scale horizontally and fit naturally into its OpenShift-based environment.

The evaluation criteria

The team focused on three requirements:

  1. Self-hosting
    Run device management on the company-controlled infrastructure.

  2. Horizontal scaling
    Support 20,000+ devices reliably.

  3. Container platform support
    Work well with OpenShift and related internal platforms.

The solution

Fleet gave the team a platform that matched its open-source culture and infrastructure model.

The company used Fleet to manage endpoints on the same OpenShift clusters that supported other internal systems. It also used scheduled osquery queries and webhooks to automate user-to-host mapping, which reduced manual record keeping.

The open-source model was an important fit because it aligned with the companys engineering values and security review process.

The results

Fleet helps the team scale endpoint management more consistently.

  • Steady large-scale migration: Thousands of devices have already been migrated.

  • Better enrollment visibility: Real-time monitoring helps the team catch and fix migration issues sooner.

  • Stronger infrastructure alignment: Endpoint management now fits more naturally into the companys existing stack.

Why they recommend Fleet

For this company, the biggest benefit was scalable infrastructure alignment. Fleet supported large-scale, cross-platform device management in a transparent, customizable, and consistent way with how the team already worked.