f19cc81772
Closes: https://github.com/fleetdm/fleet/issues/41799 Changes: - Added support for a new required meta tag for anonymous case study articles: `cardTitleForCustomersPage`. The value of this meta tag is used as the title of the automatically generated card link for the article on the /customers page. - Added support for a new meta tag for anonymous case study articles: `cardBodyForCustomersPage`. If provided, the card link for the article will use this value for the body text, if not provided, the card link will display the `articleTitle` meta tag value. - Updated the /customers page to automatically create card links for case study articles that have `useBasicArticleTemplate` and `cardTitleForCustomersPage` meta tags.
3.8 KiB
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:
-
Self-hosting
Run device management on the company-controlled infrastructure. -
Horizontal scaling
Support 20,000+ devices reliably. -
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 company’s 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 company’s 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.
About Fleet
Fleet is the single endpoint management platform for macOS, iOS, Android, Windows, Linux, ChromeOS, and cloud infrastructure. Trusted by over 1,300 organizations, Fleet empowers IT and security teams to accelerate productivity, build verifiable trust, and optimize costs.
By bringing infrastructure-as-code (IaC) practices to device management, Fleet ensures endpoints remain secure and operational, freeing engineering teams to focus on strategic initiatives.
Fleet offers total deployment flexibility: on-premises, air-gapped, container-native (Docker and Kubernetes), or cloud-agnostic (AWS, Azure, GCP, DigitalOcean). Organizations can also choose fully managed SaaS via Fleet Cloud, ensuring complete control over data residency and legal jurisdiction.