fleet/articles/robotics-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

2.2 KiB
Raw Permalink Blame History

Robotics company unifies Mac, Windows, Linux, and Android devices

A robotics company managing specialized hardware like industrial-grade tablets in excavators alongside traditional developer desktops required a tool that could handle the complexity of Linux workstations and diverse hardware.

At a glance

  • Endpoints: 117 (Mac, Windows, Linux, Android).
  • Primary requirement: multi-platform management and GitOps workflows.
  • Key integrations: osquery, Tailscale, and Google Credential Provider.
  • Previous solution: limited manual management for Linux.

The challenge

Before Fleet, Linux desktops were a significant "blind spot". High configuration complexity and Nvidia driver conflicts made it nearly impossible to scale or manage these devices effectively. The team needed a way to manage WiFi profiles and kiosk configurations across a varied fleet.

The solution

Fleet met the requirement for a single point of truth across macOS, Windows, and Linux. The team implemented GitOps workflows and used Fleets open-source transparency to build confidence in the reliability of their stack.

The results

  • Google Auth on Windows: The team automated the deployment of the Google Credential Provider for Windows, removing the need for Active Directory dependencies.
  • Real-time network access: By integrating host vitals with Tailscale, the team now makes real-time network access decisions based on device health.
  • Proactive IT: Cross-platform automation and policy checks have allowed the team to shift from reactive troubleshooting to proactive management.