mirror of
https://github.com/fleetdm/fleet
synced 2026-04-21 13:37:30 +00:00
Remove six case studies from customers page and social proof handbook (#43352)
## Summary - Removes six anonymous case studies that are no longer needed: open-source-software-company, interactive-entertainment-company, financial-technology-company, open-source-organization, global-saas-company, and online-marketplace. - Deletes the 6 article markdown files from `articles/`, which automatically removes them from the dynamically-rendered customers page (`fleetdm.com/customers`). - Removes 7 references to these case studies from `handbook/marketing/fleet-social-proof.md`. - Removes 3 redirect routes from `website/config/routes.js` that pointed to the now-deleted case studies. ## Changes | File | Change | |------|--------| | `articles/financial-technology-company.md` | Deleted | | `articles/global-saas-company.md` | Deleted | | `articles/interactive-entertainment-company.md` | Deleted | | `articles/online-marketplace.md` | Deleted | | `articles/open-source-organization.md` | Deleted | | `articles/open-source-software-company.md` | Deleted | | `handbook/marketing/fleet-social-proof.md` | Removed 7 table rows referencing the 6 case studies | | `website/config/routes.js` | Removed 3 redirect rules for deleted case studies | --- Built for [Irena Reedy](https://fleetdm.slack.com/archives/D0APYC9R9SL/p1775761161561979) by [Kilo for Slack](https://kilo.ai/features/slack-integration) Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
This commit is contained in:
parent
54d8a2ac0a
commit
cff7036f1b
8 changed files with 1 additions and 377 deletions
|
|
@ -1,34 +0,0 @@
|
|||
# Financial technology company manages 15,000 devices with GitOps
|
||||
|
||||
A financial technology company managing a massive environment of roughly 15,000 endpoints required a solution that could keep up with their product velocity and integrate seamlessly with their "configuration as code" philosophy.
|
||||
|
||||
## At a glance
|
||||
|
||||
- **Endpoints:** ~11,000 Mac, ~864 Windows, ~3,000 Linux.
|
||||
- **Primary requirement:** GitOps workflows and high-quality API.
|
||||
- **Key integrations:** Salt-based config management, Digicert, and SIEM.
|
||||
- **Previous solution:** Workspace ONE.
|
||||
|
||||
## The Challenge
|
||||
|
||||
The team’s primary frustration with Workspace One was its inconsistency, particularly with delays in shipping configuration profiles and poor API quality. Linux servers also remained a silo, requiring separate scripting and tooling because of limited MDM support.
|
||||
|
||||
## The Solution
|
||||
|
||||
The team prioritized GitOps workflows and API compatibility to align with their existing Salt-based configuration management. Fleet’s public issue tracking and open communication provided the transparency needed to trust the platform's development cycle.
|
||||
|
||||
## The Results
|
||||
|
||||
- **Rapid migration:** The team planned a migration of 250 hosts per day to minimize disruption.
|
||||
- **MDM proxy:** They developed an MDM proxy to replicate Salt proxy minion workflows, enabling true configuration-as-code.
|
||||
- **Security pipeline:** Integrating Fleet with their SIEM via a Firehose pipeline enhanced threat detection and compliance monitoring.
|
||||
|
||||
|
||||
<meta name="articleTitle" value="Financial technology company manages 15,000 devices with GitOps">
|
||||
<meta name="authorFullName" value="Irena Reedy">
|
||||
<meta name="authorGitHubUsername" value="irenareedy">
|
||||
<meta name="category" value="case study">
|
||||
<meta name="publishedOn" value="2026-02-22">
|
||||
<meta name="description" value="A financial technology company manages a massive environment of roughly 15,000 endpoints.">
|
||||
<meta name="useBasicArticleTemplate" value="true">
|
||||
<meta name="cardTitleForCustomersPage" value="Financial technology company">
|
||||
|
|
@ -1,81 +0,0 @@
|
|||
# Global SaaS company modernizes device management with Fleet
|
||||
|
||||
A global SaaS company builds software that helps businesses manage marketing, sales, and customer service. Its platform supports thousands of employees and engineers worldwide.
|
||||
|
||||
To support that workforce, the company manages more than 10,000 devices across macOS, Windows, and Linux. As their engineering culture matured, they needed device management that matched the same automation and transparency standards used across the rest of their infrastructure.
|
||||
|
||||
## At a glance
|
||||
|
||||
* **Industry:** SaaS and software engineering
|
||||
|
||||
* **Devices managed:** 10,300+ devices (about 9,000 macOS, 1,300 Windows, and Linux engineering systems)
|
||||
|
||||
* **Primary requirements:** GitOps automation, real-time device visibility, precise policy targeting
|
||||
|
||||
* **Previous challenge:** Slow inventory updates and limited automation from legacy tooling
|
||||
|
||||
## The challenge
|
||||
|
||||
The team previously relied on Jamf for macOS management.
|
||||
|
||||
Over time, the platform became difficult to operate at scale. Inventory updates were slow, real-time visibility was limited, and the interface relied heavily on point-and-click workflows. These limitations made it harder for the team to automate configuration management and maintain up-to-date device data.
|
||||
|
||||
Linux systems were another challenge. Engineering servers and remote Linux workstations were largely unmanaged and invisible to the IT team.
|
||||
|
||||
The company needed a system that could manage devices with the same engineering-first approach they use to build software.
|
||||
|
||||
## Evaluation criteria
|
||||
|
||||
During their evaluation, Fleet needed to meet three requirements:
|
||||
|
||||
1. **GitOps and automation:** Device configurations needed to be managed through code, with version control and peer review.
|
||||
|
||||
2. **osquery integration:** The team required deep, SQL-based visibility into device state for compliance and security monitoring.
|
||||
|
||||
3. **Policy scoping and labeling:** With more than 10,000 devices, the team needed precise ways to target policies and queries across different groups.
|
||||
|
||||
They also wanted a single system that could manage macOS, Windows, and Linux rather than separate tools for each platform.
|
||||
|
||||
## The solution
|
||||
|
||||
Using Fleet, they now manage device policies and labels through GitOps workflows. Configuration changes are tracked in version control and applied automatically across the fleet.
|
||||
|
||||
The Fleet API enables deeper automation. The team runs custom queries to generate real-time compliance and inventory reports, something that was difficult with slower inventory cycles in their previous system.
|
||||
|
||||
Fleet also allowed them to bring Linux systems into standard device management for the first time. Engineering servers and remote Linux users are now visible and monitored alongside macOS and Windows devices.
|
||||
|
||||
### A careful migration at a global scale
|
||||
|
||||
Migrating more than 10,000 devices required a deliberate rollout.
|
||||
|
||||
The team took a phased approach over several weeks and months, prioritizing stability and communication with employees. Despite the scale, the transition created very little disruption.
|
||||
|
||||
Support tickets during the rollout remained low, demonstrating that large device fleets can migrate smoothly when the process is carefully planned.
|
||||
|
||||
## The results
|
||||
|
||||
The most immediate improvement has been real-time device visibility.
|
||||
|
||||
Fleet allows the team to query devices instantly and enforce compliance policies as soon as devices check in. Security teams no longer rely on stale inventory data when investigating vulnerabilities.
|
||||
|
||||
The platform also enables more precise device management. Labels and scoped policies allow the team to apply configurations to specific subsets of devices across their global fleet.
|
||||
|
||||
By consolidating tooling and moving away from Jamf’s pricing structure, the company also reduced licensing costs and redirected those resources into security automation.
|
||||
|
||||
### Why they recommend Fleet
|
||||
|
||||
For leaders evaluating device management platforms, their advice focuses on two themes: scalability and collaboration.
|
||||
|
||||
Fleet scales to tens of thousands of devices while maintaining a transparent development process. The open-source model allows teams to collaborate directly with the maintainers and ensure the platform evolves alongside their infrastructure.
|
||||
|
||||
Combined with GitOps workflows, Fleet enables device management that feels consistent with modern engineering practices.
|
||||
|
||||
|
||||
<meta name="articleTitle" value="Global SaaS company modernizes device management with Fleet">
|
||||
<meta name="authorFullName" value="Irena Reedy">
|
||||
<meta name="authorGitHubUsername" value="irenareedy">
|
||||
<meta name="category" value="case study">
|
||||
<meta name="publishedOn" value="2026-03-03">
|
||||
<meta name="description" value="How a global SaaS company manages 10,000+ devices with Fleet, using GitOps automation and real-time visibility across macOS, Windows, and Linux.">
|
||||
<meta name="useBasicArticleTemplate" value="true">
|
||||
<meta name="cardTitleForCustomersPage" value="Global SaaS company">
|
||||
|
|
@ -1,77 +0,0 @@
|
|||
# Leading interactive entertainment company adopts Fleet for MDM
|
||||
|
||||
<div purpose="attribution-quote">
|
||||
|
||||
We wanted an open-source MDM to easily use configuration-as-code, deliver the best possible experience for our employees, and make security happy.
|
||||
|
||||
**- Lead Client Platform Engineer**
|
||||
</div>
|
||||
|
||||
## Challenge
|
||||
|
||||
They were facing challenges in managing their devices across multiple platforms. Their previous solution lacked integration with their configuration management tool, Puppet, and did not align with their preferred Infrastructure-as-Code (IaC) workflows. Additionally, performance issues with their interim solution necessitated finding an alternative before undergoing another full migration. They required a scalable, cross-platform MDM solution with a clear migration path, enhanced visibility, and automation capabilities.
|
||||
|
||||
## Solution
|
||||
|
||||
Fleet’s open-source platform enables a declarative approach alongside robust API and webhook support. Through seamless [automations](https://fleetdm.com/guides/automations#host-status-automations), integration with existing systems, and support for multiple operating systems, they eliminated the need for inefficient manual workflows and extensive customizations.
|
||||
|
||||
## Results
|
||||
|
||||
<div purpose="checklist">
|
||||
|
||||
Visibility into every endpoint and dynamic host segmentation.
|
||||
|
||||
Introduced new infrastructure as code workflows.
|
||||
|
||||
Unified device management across macOS and Windows.
|
||||
|
||||
Smooth and seamless migration.
|
||||
</div>
|
||||
|
||||
By switching to Fleet, they continue to manage their devices through automated MDM workflows that support thousands of devices. Capabilities like automated device enrollment, dynamic host segmentation, real-time reporting, and assisted migration allowed them to enforce security settings without overly restricting endpoints or their users.
|
||||
|
||||
|
||||
## Their story
|
||||
|
||||
The global leader in interactive entertainment and software development manages an extensive fleet of devices supporting game development, publishing, and operations. To overcome the challenges of scalability and customization, they partnered with Fleet early on to help contribute to Fleet’s MDM roadmap, resulting in a solution tailored for cross-platform enterprise teams.
|
||||
|
||||
A few key factors drove the decision to switch to Fleet. They needed compatibility across macOS and Windows, integrations with existing tools like [Puppet](https://en.wikipedia.org/wiki/Puppet_(software)), and effortless scaling to thousands of devices.
|
||||
|
||||
With Fleet, they achieved this through:
|
||||
|
||||
- Next-gen change management
|
||||
- Real-time insights through definitive data
|
||||
- Eliminating tool overlap
|
||||
- Dedicated support and a seamless migration
|
||||
|
||||
### Next-gen change management
|
||||
|
||||
Fleet is open-source, allowing engineering teams to audit, customize, and extend the platform as needed alongside [infrastructure-as-code workflows](https://github.com/fleetdm/fleet-gitops). This makes device management more agile and automated while reducing errors through peer review.
|
||||
|
||||
### Real-time reporting and definitive data
|
||||
|
||||
Fleet allowed the company to run live [reports](https://fleetdm.com/guides/queries), dynamically segment hosts, and gain real-time insights across their entire fleet. This capability enhanced incident response and ensured critical policies and configurations were consistently enforced through Fleet’s double-check [verification](https://fleetdm.com/guides/custom-os-settings#os-settings-status).
|
||||
|
||||
### Eliminate tool overlap
|
||||
|
||||
They were able to replace multiple tools and consolidate the management of thousands of macOS and Windows devices into a single platform. Fleet’s open [API](https://fleetdm.com/docs/rest-api/rest-api) and CLI tools also allowed them to build custom integrations with their existing systems and support flexible [logging pipelines](https://fleetdm.com/guides/log-destinations), like AWS and GCP.
|
||||
|
||||
### Best-in-class support
|
||||
|
||||
Fleet provides timely issue resolutions, guidance, and ensures a smooth transition with minimal disruption. [Migrations](https://fleetdm.com/guides/mdm-migration#basic-article) are directly assisted by Fleet’s best-in-class [support](https://fleetdm.com/support) teams and built-in [migration tools](https://github.com/fleetdm/fleet/tree/main/tools/mdm/migration).
|
||||
|
||||
|
||||
## Conclusion
|
||||
|
||||
By switching to Fleet, it solved their critical challenges in device management, including integration with existing tools, cross-platform compatibility, and scalability. Fleet's Infrastructure-as-Code workflows, real-time reporting, and automation eliminated manual inefficiencies and consolidated tools. With Fleet, the company improved visibility, enforced security policies, and managed thousands of devices without performance impacts. The smooth migration process and dedicated support made Fleet a practical, long-term solution for their complex, enterprise-level needs.
|
||||
|
||||
<call-to-action></call-to-action>
|
||||
|
||||
<meta name="category" value="case study">
|
||||
<meta name="authorGitHubUsername" value="Drew-P-drawers">
|
||||
<meta name="authorFullName" value="Andrew Baker">
|
||||
<meta name="publishedOn" value="2024-12-23">
|
||||
<meta name="articleTitle" value="Leading interactive entertainment company adopts Fleet for MDM">
|
||||
<meta name="description" value="Leading interactive entertainment company adopts Fleet for MDM">
|
||||
<meta name="useBasicArticleTemplate" value="true">
|
||||
<meta name="cardTitleForCustomersPage" value="Interactive entertainment company">
|
||||
|
|
@ -1,73 +0,0 @@
|
|||
# Online marketplace simplifies multi-OS device management with Fleet
|
||||
|
||||
A major online marketplace operates one of the largest peer-to-peer platforms in Europe. Its engineering teams rely on a mix of macOS, Windows, and Linux laptops to build and maintain the platform.
|
||||
|
||||
Managing these devices efficiently becomes difficult with traditional device management tools.
|
||||
|
||||
Fleet introduces a simpler and more scalable approach.
|
||||
|
||||
## At a glance
|
||||
|
||||
* **Industry:** Online marketplaces
|
||||
|
||||
* **Devices managed:** ~1,500 laptops across macOS, Windows, and Linux
|
||||
|
||||
* **Primary requirements:** Multi-OS support, GitOps workflows, scalable management
|
||||
|
||||
* **Previous challenge:** Complex device management workflows
|
||||
|
||||
## The challenge
|
||||
|
||||
The company previously relied on Workspace ONE for device management.
|
||||
|
||||
However, the platform’s complexity made it difficult to manage devices efficiently. Applying consistent policies across different operating systems required significant manual effort.
|
||||
|
||||
Linux laptops presented an even larger challenge because they were not enrolled in the previous management system.
|
||||
|
||||
The team wanted a simpler platform that aligned better with how their engineers work.
|
||||
|
||||
## The evaluation criteria
|
||||
|
||||
The team prioritized three capabilities:
|
||||
|
||||
1. **Cross-platform device management**
|
||||
Manage macOS, Windows, and Linux devices from one platform.
|
||||
|
||||
2. **GitOps configuration management**
|
||||
Store and manage policies in GitHub repositories.
|
||||
|
||||
3. **Scalable infrastructure**
|
||||
Deploy a system that could grow with the organization.
|
||||
|
||||
## The solution
|
||||
|
||||
Fleet allowed the team to move device management into Git-based workflows.
|
||||
|
||||
Policies were defined in repositories and automatically deployed via CI/CD pipelines. This approach eliminated the manual configuration work required by traditional device management tools.
|
||||
|
||||
Fleet also provided visibility across all operating systems, including Linux laptops that were previously unmanaged.
|
||||
|
||||
## The results
|
||||
|
||||
Fleet simplified device management across the company’s entire laptop fleet.
|
||||
|
||||
* **Unified device visibility:** IT teams now manage macOS, Windows, and Linux devices from a single platform.
|
||||
|
||||
* **GitOps automation:** Policy changes are managed through code instead of manual UI configuration.
|
||||
|
||||
* **Faster troubleshooting:** Device telemetry helps teams quickly diagnose and resolve issues.
|
||||
|
||||
## Why Fleet
|
||||
|
||||
Fleet offers a modern approach to device management. For this organization, that means simpler workflows, better automation, and consistent visibility across every device.
|
||||
|
||||
|
||||
<meta name="articleTitle" value="Online marketplace simplifies multi-OS device management with Fleet">
|
||||
<meta name="authorFullName" value="Irena Reedy">
|
||||
<meta name="authorGitHubUsername" value="irenareedy">
|
||||
<meta name="category" value="case study">
|
||||
<meta name="publishedOn" value="2026-03-14">
|
||||
<meta name="description" value="An online marketplace replaces complex device tools with Fleet, gaining unified visibility across macOS, Windows, and Linux.">
|
||||
<meta name="useBasicArticleTemplate" value="true">
|
||||
<meta name="cardTitleForCustomersPage" value="Online marketplace">
|
||||
<meta name="cardBodyForCustomersPage" value="An online marketplace replaces complex device tools.">
|
||||
|
|
@ -1,34 +0,0 @@
|
|||
# Open-source organization manages 1,556 devices with real-time compliance
|
||||
|
||||
A global open-source software organization managing a fleet of over 1,500 devices required a solution that respected privacy and offered equal depth for Mac, Windows, and Linux.
|
||||
|
||||
## At a glance
|
||||
|
||||
- **Endpoints:** 1,556 (Mac, Windows, and Linux).
|
||||
- **Primary requirement:** True multi-OS support and open-source core.
|
||||
- **Key integrations:** Splunk and Google BigQuery.
|
||||
- **Previous solution:** Legacy tools that treated Linux as a "second-class citizen".
|
||||
|
||||
## The challenge:
|
||||
|
||||
The team lacked a unified solution for remote wipe and deep logging across their diverse OS environment. Linux servers and BYOD units were major blind spots with limited compliance visibility.
|
||||
|
||||
## The solution
|
||||
|
||||
Fleet’s open-source nature aligned with their organizational values, easing cultural acceptance and reducing pushback on MDM adoption. They used GitOps and osquery to implement real-time compliance checks as code.
|
||||
|
||||
## The results
|
||||
|
||||
- **Minutes vs. days:** Response times to new vulnerabilities shifted from days to minutes through real-time visibility and targeted patching.
|
||||
- **Automated reporting:** The team uses the API to programmatically track fleet-maintained app versions and patch compliance.
|
||||
- **Unified ecosystem:** Streaming telemetry into Splunk and BigQuery allowed them to correlate endpoint events with broader infrastructure logs.
|
||||
|
||||
|
||||
<meta name="articleTitle" value="Open-source organization manages 1,556 devices with real-time compliance">
|
||||
<meta name="authorFullName" value="Irena Reedy">
|
||||
<meta name="authorGitHubUsername" value="irenareedy">
|
||||
<meta name="category" value="case study">
|
||||
<meta name="publishedOn" value="2026-02-22">
|
||||
<meta name="description" value="Open-source org manages 1,556 devices with equal Mac, Windows, and Linux support, real-time compliance, and unified threat visibility.">
|
||||
<meta name="useBasicArticleTemplate" value="true">
|
||||
<meta name="cardTitleForCustomersPage" value="Open-source organization">
|
||||
|
|
@ -1,68 +0,0 @@
|
|||
# Open-source software company closes the Linux gap in device management with Fleet
|
||||
|
||||
A global open-source software company manages Windows, macOS, and Linux at scale. Linux is central to its business, but existing tools didn’t support it with the same depth as macOS and Windows.
|
||||
|
||||
Fleet helps the company adopt Linux as part of a unified endpoint strategy while supporting strict security and audit requirements.
|
||||
|
||||
## At a glance
|
||||
|
||||
* **Industry:** Open-source software
|
||||
|
||||
* **Devices managed:** ~5,100 devices across Windows, macOS, and Linux
|
||||
|
||||
* **Primary requirements:** Self-hosting, GitOps, visibility into their devices
|
||||
|
||||
* **Previous challenge:** Weak Linux support in existing tools
|
||||
|
||||
## The challenge
|
||||
|
||||
Before Fleet, the company used tools such as Jamf and Intune for macOS and Windows.
|
||||
|
||||
That left Linux as a major gap. For an organization built around Linux and open-source software, that disconnect created both technical and operational friction.
|
||||
|
||||
The team needed a platform that could handle Linux seriously, support self-hosting, and align with compliance requirements such as Common Criteria certification and security audits.
|
||||
|
||||
## The evaluation criteria
|
||||
|
||||
The team focused on three requirements:
|
||||
|
||||
1. **Self-hosted deployment**
|
||||
Maintain control for security and compliance.
|
||||
|
||||
2. **GitOps workflows**
|
||||
Manage policy and software through code.
|
||||
|
||||
3. **osquery integration**
|
||||
Collect detailed data for compliance and security monitoring.
|
||||
|
||||
## The solution
|
||||
|
||||
Fleet gave the team a way to manage Windows, macOS, and Linux through one platform.
|
||||
|
||||
The company uses GitOps workflows to automate software management and keep endpoint configuration aligned with security policy. Migration moved quickly, starting with user acceptance testing and progressing to broad rollout within weeks.
|
||||
|
||||
Fleet’s open-source model was a strong fit for the company’s culture and technical standards.
|
||||
|
||||
## The results
|
||||
|
||||
Fleet helped the team close Linux gaps and simplify management across operating systems.
|
||||
|
||||
* **Fast rollout:** From testing to broad rollout in just a matter of weeks
|
||||
|
||||
* **Better Linux coverage:** Linux devices now align with macOS and Windows management.
|
||||
|
||||
* **Simpler operations:** One platform reduces administrative complexity for a global workforce.
|
||||
|
||||
## Why they recommend Fleet
|
||||
|
||||
Fleet lets the team manage Linux, macOS, and Windows in one place, while staying aligned with its open-source and compliance requirements.
|
||||
|
||||
|
||||
<meta name="articleTitle" value="Open-source software company closes the Linux gap in device management with Fleet">
|
||||
<meta name="authorFullName" value="Irena Reedy">
|
||||
<meta name="authorGitHubUsername" value="irenareedy">
|
||||
<meta name="category" value="case study">
|
||||
<meta name="publishedOn" value="2026-03-18">
|
||||
<meta name="description" value="An open-source software company uses Fleet to unify device management and improve Linux visibility.">
|
||||
<meta name="useBasicArticleTemplate" value="true">
|
||||
<meta name="cardTitleForCustomersPage" value="Open-source software company">
|
||||
|
|
@ -21,7 +21,6 @@ Champion stories and case studies showing real customers achieving real outcomes
|
|||
|
||||
| Story | Mac | Windows | Linux | Date |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| [Financial technology company manages 15,000 devices with GitOps](https://fleetdm.com/case-study/financial-technology-company) | ✓ | ✓ | ✓ | 2026‑02‑22 |
|
||||
| [Financial services platform manages 6,000+ hosts with continuous compliance visibility](https://fleetdm.com/case-study/financial-services-platform) | ✓ | ✓ | ✓ | 2026‑02‑22 |
|
||||
| [Fintech company manages a global remote workforce with Fleet](https://fleetdm.com/articles/fintech-company) | ✓ | ✓ | ✓ | 2026‑03‑14 |
|
||||
| [Fintech company strengthens infrastructure visibility with Fleet](https://fleetdm.com/articles/fintech-company-strengthens-infrastructure-visibility) | ✓ | ✓ | ✓ | 2026‑03‑14 |
|
||||
|
|
@ -37,8 +36,6 @@ Champion stories and case studies showing real customers achieving real outcomes
|
|||
| [Workspace software company consolidates Kandji and Intune across 1,465 devices](https://fleetdm.com/case-study/workspace-software-company) | ✓ | ✓ | | 2026‑02‑22 |
|
||||
| [Communications platform unifies device management across 3,000 devices](https://fleetdm.com/case-study/communications-platform) | ✓ | ✓ | ✓ | 2026‑02‑22 |
|
||||
| [Global technology platform improves vulnerability intelligence with Fleet](https://fleetdm.com/articles/global-technology-platform) | ✓ | ✓ | ✓ | 2026‑03‑03 |
|
||||
| [Online marketplace simplifies multi-OS device management with Fleet](https://fleetdm.com/articles/online-marketplace) | ✓ | ✓ | ✓ | 2026‑03‑14 |
|
||||
| [Global SaaS company modernizes device management with Fleet](https://fleetdm.com/case-study/global-saas-company) | ✓ | ✓ | ✓ | 2026‑03‑03 |
|
||||
| [Cloud-based data leader chooses Fleet for orchestration](https://fleetdm.com/case-study/cloud-data-platform) | ✓ | ✓ | ✓ | 2024‑12‑20 |
|
||||
| [How a global workforce management company achieved compliance and clarity with Fleet](https://fleetdm.com/case-study/global-workforce-management-company) | ✓ | ✓ | ✓ | 2024‑12‑17 |
|
||||
| [Global collaboration platform consolidates device management with Fleet](https://fleetdm.com/case-study/collaboration-platform) | ✓ | ✓ | ✓ | 2024‑06‑01 |
|
||||
|
|
@ -66,14 +63,12 @@ Champion stories and case studies showing real customers achieving real outcomes
|
|||
| [IT platform provider automates patching across thousands of Mac, Windows, and Linux devices](https://fleetdm.com/case-study/it-platform-provider) | IT / MSP | ✓ | ✓ | ✓ | 2026‑02‑22 |
|
||||
| [Enforcing security policies in minutes across a regulated healthcare environment](https://fleetdm.com/case-study/healthcare-technology-organization) | Healthcare | ✓ | ✓ | ✓ | 2026‑02‑22 |
|
||||
| [Robotics company unifies Mac, Windows, Linux, and Android devices](https://fleetdm.com/case-study/robotics-company) | Robotics / Hardware | ✓ | ✓ | ✓ | 2026‑02‑22 |
|
||||
| [Open-source organization manages 1,556 devices with real-time compliance](https://fleetdm.com/case-study/open-source-organization) | Open Source / Nonprofit | ✓ | ✓ | ✓ | 2026‑02‑22 |
|
||||
| [Journalism nonprofit manages Mac and Linux devices with GitOps](https://fleetdm.com/case-study/journalism-nonprofit) | Media / Journalism | ✓ | | ✓ | 2026‑02‑22 |
|
||||
| [Agritech producer replaces manual tracking across 273 devices](https://fleetdm.com/case-study/agritech-producer) | Agriculture / AgriTech | ✓ | ✓ | ✓ | 2026‑02‑23 |
|
||||
| [Cannabis technology company consolidates Jamf and Intune with Fleet](https://fleetdm.com/case-study/cannabis-technology-company) | Cannabis / Retail Tech | ✓ | ✓ | | 2026‑02‑22 |
|
||||
| [Gaming technology company runs GitOps-driven device management on-prem](https://fleetdm.com/case-study/gaming-technology-company) | Gaming / Entertainment | ✓ | ✓ | ✓ | 2026‑02‑22 |
|
||||
| [Gaming platform gains production visibility with Fleet](https://fleetdm.com/articles/gaming-platform) | Gaming / Entertainment | | | ✓ | 2026‑03‑04 |
|
||||
| [Global entertainment company manages thousands of devices with GitOps workflows](https://fleetdm.com/articles/global-entertainment-company) | Gaming / Entertainment | ✓ | ✓ | ✓ | 2026‑03‑14 |
|
||||
| [Leading interactive entertainment company adopts Fleet for MDM](https://fleetdm.com/case-study/interactive-entertainment-company) | Gaming / Entertainment | ✓ | ✓ | | 2024‑12‑23 |
|
||||
| [Large gaming company enhances server observability with Fleet](https://fleetdm.com/case-study/online-gaming-platform) | Gaming / Entertainment | | | ✓ | 2024‑12‑11 |
|
||||
| [Vehicle manufacturer transitions to Fleet for endpoint security](https://fleetdm.com/case-study/electric-vehicle-manufacturer) | Automotive / Manufacturing | ✓ | ✓ | ✓ | 2024‑12‑12 |
|
||||
| [EV manufacturer brings Linux workstations under centralized management with Fleet](https://fleetdm.com/case-study/ev-manufacturer) | Automotive / Manufacturing | | | ✓ | 2024‑06‑01 |
|
||||
|
|
@ -81,7 +76,6 @@ Champion stories and case studies showing real customers achieving real outcomes
|
|||
| [National research organization improves Linux automation with Fleet](https://fleetdm.com/articles/national-research-organization) | Research / Nonprofit | | | ✓ | 2026‑03‑14 |
|
||||
| [Technology platform manages 15,000 iPads with Fleet](https://fleetdm.com/articles/technology-platform) | Technology | | | | 2026‑03‑14 |
|
||||
| [Defense and engineering company improves visibility across Linux systems with Fleet](https://fleetdm.com/case-study/defense-and-engineering-company) | Defense / Engineering | | ✓ | ✓ | 2026‑04‑01 |
|
||||
| [Open-source software company closes the Linux gap in device management with Fleet](https://fleetdm.com/case-study/open-source-software-company) | Open Source / Software | ✓ | ✓ | ✓ | 2026‑03‑21 |
|
||||
| [IT services company builds zero-touch workflows with Fleet](https://fleetdm.com/case-study/it-service-company) | IT / MSP | ✓ | | | 2026‑03‑21 |
|
||||
| [National research lab scales host visibility with Fleet](https://fleetdm.com/case-study/national-research-lab) | Research / HPC | | | ✓ | 2026‑03‑14 |
|
||||
| [Cybersecurity company improves endpoint visibility with Fleet](https://fleetdm.com/case-study/cybersecurity-company) | Security | ✓ | ✓ | ✓ | 2026‑03‑14 |
|
||||
|
|
@ -98,7 +92,7 @@ Champion stories and case studies showing real customers achieving real outcomes
|
|||
| [Identity security company](https://fleetdm.com/case-study/identity-security-company) | Cybersecurity | ✓ | ✓ | | 2026‑03‑14 |
|
||||
| [Medical research institution](https://fleetdm.com/case-study/medical-research-institution) | Higher education | ✓ | ✓ | ✓ | 2026‑03‑14 |
|
||||
| [National research organization](https://fleetdm.com/case-study/national-research-organization) | Research and technology | ✓ | | ✓ | 2026‑03‑14 |
|
||||
| [Online marketplace](https://fleetdm.com/case-study/online-marketplace) | Oneline marketplace | ✓ | ✓ | ✓ | 2026‑03‑14 |
|
||||
|
||||
|
||||
|
||||
### Fleet customer testimonials
|
||||
|
|
|
|||
3
website/config/routes.js
vendored
3
website/config/routes.js
vendored
|
|
@ -919,16 +919,13 @@ module.exports.routes = {
|
|||
'GET /announcements/cannabis-technology-company': '/case-study/cannabis-technology-company',
|
||||
'GET /announcements/communications-services-sector-scaling-cross-platform-device-management-with-fleet': '/case-study/communications-platform',
|
||||
'GET /announcements/financial-services-platform': '/case-study/financial-services-platform',
|
||||
'GET /announcements/financial-technology-company': '/case-study/financial-technology-company',
|
||||
'GET /announcements/gaming-technology-company': '/case-study/gaming-technology-company',
|
||||
|
||||
'GET /announcements/global-workforce-management-company-achieves-compliance-and-clarity-with-fleet': '/case-study/global-workforce-management-company',
|
||||
'GET /announcements/healthcare.technology.organization': '/case-study/healthcare-technology-organization',
|
||||
'GET /announcements/interactive-entertainment-company-adopts-fleet-for-mdm': '/case-study/interactive-entertainment-company',
|
||||
'GET /announcements/all-in-one-it-platform-provider': '/case-study/it-platform-provider',
|
||||
'GET /announcements/scaling-IT-as-a-service-with-GitOps-first-management': '/case-study/it-service-provider',
|
||||
'GET /announcements/independent-journalism-nonprofit': '/case-study/journalism-nonprofit',
|
||||
'GET /announcements/open-source-software-organization': '/case-study/open-source-organization',
|
||||
'GET /announcements/robotics-company': '/case-study/robotics-company',
|
||||
'GET /announcements/modular-workspace-software-company': '/case-study/workspace-software-company',
|
||||
'GET /announcements/worldwide-security-and-authentication-platform-chooses-fleet-for-linux': '/case-study/worldwide-security-and-authentication-platform',
|
||||
|
|
|
|||
Loading…
Reference in a new issue