fleet/articles/it-service-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

IT services company builds zero-touch workflows with Fleet

This IT services company provides endpoint management and security solutions for enterprise customers. As it expands its own environment, the team wants device management that is secure by default and easy to automate.

Fleet helps the company build zero-touch deployment workflows and manage device state through code.

At a glance

  • Industry: IT services and endpoint management

  • Devices managed: 100+ Windows devices, expanding to macOS and Linux

  • Primary requirements: Zero-touch deployment, GitOps workflows, osquery visibility

  • Previous challenge: Legacy tools could not support secure, automated deployments at scale

The challenge

Before Fleet, the company relied on legacy tools that were not built for zero-touch, secure laptop deployment.

The team needed better visibility into device state and a more automated way to manage credentials, policies, and user transitions. Existing tools relied on manual workflows, created friction, and could not support a secure-by-default model at scale.

The evaluation criteria

The team focused on three capabilities:

  1. Zero-touch deployment
    Automate device setup from the moment a machine is unboxed.

  2. GitOps workflows
    Manage device state programmatically rather than through manual UI actions.

  3. osquery integration
    Use deep system-level data to drive security workflows.

The solution

Fleet gave the team a platform for automated deployment, identity-aware workflows, and real-time visibility.

The company used the Fleet API to rotate Recovery Lock passwords, manage hidden admin accounts, and respond to identity changes without manual intervention. Integrations with Okta also helped automatically remove deactivated users, reducing the risk of leftover access on managed devices.

The open-source model was important because it allowed the team to inspect the code and verify behavior directly.

The results

Fleet gave the team a stronger foundation for secure deployment and lifecycle management.

  • Better zero-touch workflows: New devices can be set up with more consistency and less manual work.

  • Faster security response: Identity and device changes can trigger action quickly.

  • Simpler management: The team can centralize security policies across operating systems.

Why they recommend Fleet

For this company, the biggest benefit is zero-touch visibility. Fleet helps the team build automated workflows that are more secure, more scalable, and easier to verify.