Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-04-21 13:37:30 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 91
fleet/articles/fintech-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.6 KiB
Raw Blame History

Fintech company manages a global remote workforce with Fleet

A fintech company builds payment infrastructure that allows developers to integrate real-time Bitcoin transactions into games and applications.

The company operates as a remote-first organization with employees working across multiple countries and networks. Managing devices in this environment requires a system that maintains visibility regardless of location.

At a glance

  • Industry: Fintech and gaming payments infrastructure

  • Devices managed: Distributed fleet across macOS, Windows, and Linux

  • Primary requirements: GitOps workflows, cross-platform management, osquery visibility

  • Previous challenge: Limited visibility for devices outside corporate VPNs

The challenge

Because the company operates remotely, many devices do not remain connected to a central VPN.

Devices outside the VPN create visibility gaps for the IT team. Without a persistent connection to the management platform, security teams cannot reliably monitor system state.

The organization needs a platform that maintains visibility across devices regardless of network location.

The evaluation criteria

Fleet must support these three key capabilities:

  1. GitOps workflows
    Manage device configuration through version-controlled repositories.

  2. osquery integration
    Provide deep system insights through structured queries.

  3. Cross-platform management
    Maintain unified control across macOS, Windows, and Linux.

The solution

Fleet provides a lightweight connection that maintains visibility across devices regardless of the network environment.

Security teams run scheduled queries and stream telemetry data to monitor the health and compliance of remote systems.

Fleet also supports policy automation. The team builds workflows that trigger automated remediation via the API when devices fall out of compliance.

The open development process also aligns with the company’s engineering culture. Access to engineering discussions and issue tracking provides transparency into the platform’s roadmap.

A gradual rollout

The company adopted Fleet through a phased rollout.

New team members were onboarded directly into Fleet as the organization grew. This allowed the team to explore features while gradually expanding coverage.

The results: unified visibility for a remote workforce

Fleet provided a centralized platform for managing a globally distributed workforce.

Security teams gained immediate insight into device state through scheduled queries and telemetry streaming. Remote devices remained visible even when they were not connected to corporate networks.

Operational complexity also decreased. Instead of managing multiple tools for different operating systems, the team operated from a single platform.

Why they recommend Fleet

Their recommendation focuses on unified endpoint management.

Fleet allows organizations to manage macOS, Windows, and Linux devices through a single API while maintaining strong visibility across distributed networks.