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.
2.2 KiB
IT service provider scales to 8,000+ devices with GitOps
As an "IT-as-a-Service" provider, managing over 8,000 laptops across 120 SME customers. They needed a centralized, multi-tenant solution that prioritized automation and GitOps workflows to make IT accessible to non-technical external clients.
At a glance
-
Endpoints: 8,000+ laptops across 120 customers.
-
Primary requirement: GitOps-first infrastructure and multi-tenancy.
-
Key integrations: GitOps, Multi-MDM connections per customer.
-
Previous solution: ManageEngine.
The challenge
Before Fleet, they used ManageEngine but found that application management was not scaling to meet their needs. Managing Linux servers and remote laptops was significantly less effective, as they lacked the granular visibility and control necessary to manage these effectively across varied customer environments.
The solution
They chose Fleet for its deep integration with automated workflows and the ability to support Mac, Windows, and Linux from a single interface. The open-source transparency allowed them to audit and adjust agent flows to ensure the stack met their specific security and operational standards.
The results
-
Cost savings: the migration allowed them to avoid the renewal of over 3,000 ManageEngine licenses, resulting in significant cost avoidance.
-
Automated deployments: using labels in GitOps, they automated the assignment of policies and scripts, enabling seamless software deployment across thousands of devices.
-
Operational clarity: exposing device information in an understandable way built better trust between the IT service team and improved troubleshooting speed.