Changes: - Unpublished a case study (I will be reopening a Draft PR to add it) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Style** * Updated styling for case study quote author images * **Chores** * Removed Proton case study from customer stories navigation menu and featured stories section on the customers page <!-- end of auto-generated comment: release notes by coderabbit.ai -->
This commit is contained in:
Eric
@@ -1,95 +0,0 @@
|
||||
# How Proton manages devices with the same privacy and security standards it promises its users
|
||||
|
||||
Proton chose Fleet to bring its privacy-first, security-first values to device management.
|
||||
|
||||
## The challenge: living the values behind the curtain
|
||||
|
||||
Proton is the company behind Proton Mail, Proton VPN, Proton Drive, and Proton Calendar. Every product is end-to-end encrypted. No one at Proton - not even Proton itself - can read your data. That promise is the foundation of a brand trusted by over 100 million users worldwide.
|
||||
|
||||
But a promise that strong creates an obligation internally. If Proton tells the world their data is private, the devices Proton employees use every day need to meet the same standard. Endpoint security is not optional for a company whose entire value proposition depends on trust.
|
||||
|
||||
<div purpose="attribution-quote">
|
||||
|
||||
We tell users no one can access their data, not even us. The same standard has to apply to how we manage our own devices, and Fleet is a platform we can actually verify. When your business depends on trust, that matters.
|
||||
|
||||
**Andy Yen**
|
||||
|
||||
CEO and Founder of Proton
|
||||
|
||||
</div>
|
||||
|
||||
Proton's engineering team runs primarily on Linux, with Mac and Windows also in the fleet. Before Fleet, the picture was fragmented. Kandji handled Mac. Omnissa Workspace ONE handled Windows. And Linux - the platform most of the engineering team depends on - had no formal management solution at all. Proton had limited visibility into encryption status, software inventory, and hardware health across its Linux endpoints.
|
||||
|
||||
For a privacy-first company, that gap was a liability. Not just operationally, but reputationally. Proton needed a single device management platform that could unify all three operating systems, deliver real security controls, and do it in a way that aligned with the transparency and privacy values Proton stands for.
|
||||
|
||||
## Why Fleet: transparency that earns trust
|
||||
|
||||
Proton evaluated Fleet against the same criteria they apply to their own products: Is it transparent? Is it secure? Can we verify what it does?
|
||||
|
||||
Fleet's open-source architecture answered all three. The source code is public. Policies are managed as code through GitOps, which means every change is reviewed, versioned, and auditable. There is no black box. For a company built on the principle that users should never have to take a vendor's word on trust, Fleet's model was a natural fit.
|
||||
|
||||
<div purpose="attribution-quote">
|
||||
|
||||
We tell users to verify, not just trust. Fleet lets us manage security policies the way we build software: versioned, peer-reviewed, auditable.
|
||||
|
||||
**Andy Yen**
|
||||
|
||||
CEO and Founder of Proton
|
||||
|
||||
</div>
|
||||
|
||||
Proton's engineers are security-conscious and privacy-focused, as they should be. They expect to understand how a tool works before they accept it on their machines. Fleet's transparency turned what is normally the hardest part of MDM adoption - getting engineers to opt in - into a straightforward conversation. The code is there. The policies are visible. There is nothing hidden.
|
||||
|
||||
Fleet also delivered something Proton could not find elsewhere: genuine cross-platform support. One agent, one console, one set of policies across Linux, Mac, and Windows. No separate tools. No fragmented visibility. One source of truth for every device in the organization.
|
||||
|
||||
## The outcome: one platform, one standard
|
||||
|
||||
Proton originally approached Fleet to solve the Linux management gap. Within weeks, the value was clear enough that Proton's CEO made the decision to consolidate all platforms under Fleet, replacing Kandji on Mac and Omnissa Workspace ONE on Windows.
|
||||
|
||||
With Fleet, Proton now has:
|
||||
|
||||
<div purpose="checklist">
|
||||
|
||||
Full device visibility across Linux, Mac, and Windows from a single console.
|
||||
|
||||
Encryption status monitoring across every endpoint - critical for a company built on E2E encryption.
|
||||
|
||||
GitOps-based policy management with full audit trails, matching the transparency Proton delivers to its own users.
|
||||
|
||||
Software inventory and hardware health data that was previously invisible on Linux.
|
||||
|
||||
A single agent replacing three separate tools, reducing complexity and eliminating gaps.
|
||||
|
||||
</div>
|
||||
|
||||
The consolidation was not just about efficiency. It was about consistency. Proton now manages every employee device to the same privacy and security standard that it promises its users. The internal operation matches the external brand.
|
||||
|
||||
## Looking ahead
|
||||
|
||||
Proton continues to expand its use of Fleet across the organization. As the team grows and the product suite evolves, Fleet provides the foundation for Proton to scale device management without compromising on the values that define the brand.
|
||||
|
||||
For Proton, this was never just about finding a better MDM. It was about finding a partner that understands what it means to put privacy and security first - not just in what you sell, but in how you operate.
|
||||
|
||||
|
||||
<meta name="category" value="case study">
|
||||
<meta name="companyLogoFilename" value="logo-proton-99x32@2x.png">
|
||||
<meta name="articleTitle" value="How Proton manages devices with the same privacy and security standards it promises its users">
|
||||
<meta name="description" value="Proton replaced three separate device management tools with Fleet, gaining unified visibility and security across Linux, Mac, and Windows.">
|
||||
|
||||
|
||||
<meta name="publishedOn" value="2026-04-20">
|
||||
<meta name="authorGitHubUsername" value="n/a">
|
||||
<meta name="authorFullName" value="Fleetdm">
|
||||
|
||||
<meta name="quoteContent" value="“We tell users no one can access their data, not even us. The same standard has to apply to how we manage our own devices, and Fleet is a platform we can actually verify. When your business depends on trust, that matters.”">
|
||||
<meta name="quoteAuthorImageFilename" value="andy-yen-120x120@2x.png">
|
||||
<meta name="quoteAuthorName" value="Andy Yen">
|
||||
<meta name="quoteAuthorJobTitle" value="CEO and Founder of Proton">
|
||||
|
||||
<meta name="companyName" value="Proton">
|
||||
<meta name="companyInfo" value="Proton is a privacy technology company behind Proton Mail, Proton VPN, Proton Drive, and Proton Calendar. Every product is end-to-end encrypted, trusted by over 100 million users worldwide.">
|
||||
<meta name="companyInfoLineTwo" value="Headquartered in Geneva, Switzerland, Proton's mission is to build an internet where privacy is the default.">
|
||||
|
||||
<meta name="summaryChallenge" value="Proton's engineering team ran primarily on Linux, with Mac and Windows also in the fleet. Before Fleet, Kandji handled Mac, Omnissa Workspace ONE handled Windows, and Linux — the platform most engineers depend on — had no formal management solution at all.">
|
||||
<meta name="summarySolution" value="Fleet provided Proton with a single agent, one console, and one set of policies across Linux, Mac, and Windows. Fleet's open-source architecture and GitOps-based policy management aligned directly with Proton's own transparency and security values.">
|
||||
<meta name="summaryKeyResults" value="Unified device visibility across Linux, Mac, and Windows from a single console; Encryption status monitoring across every endpoint; GitOps-based policy management with full audit trails; Software inventory and hardware health data previously invisible on Linux; Single agent replacing three separate tools">
|
||||
BIN
Binary file not shown.
|
Before Width: | Height: | Size: 62 KiB |
BIN
Binary file not shown.
|
Before Width: | Height: | Size: 3.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1.0 KiB |
@@ -84,7 +84,6 @@
|
||||
margin-right: 24px;
|
||||
img {
|
||||
height: 120px;
|
||||
border-radius: 50%;
|
||||
}
|
||||
}
|
||||
[purpose='quote-text'] {
|
||||
|
||||
-9
@@ -84,15 +84,6 @@
|
||||
<p>Faire keeps Macs secure with CIS benchmarks using Fleet</p>
|
||||
</div>
|
||||
</a>
|
||||
<a href="/case-study/proton" purpose="case-study-link" v-if="thisPage.url !== '/case-study/proton'">
|
||||
<div purpose="link-image">
|
||||
<img alt="Proton" src="/images/nav-icon-proton-40x40@2x.png">
|
||||
</div>
|
||||
<div purpose="link-text">
|
||||
<p><strong>Proton</strong></p>
|
||||
<p>Proton manages devices with the same privacy and security standards it promises its users</p>
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
<div purpose="edit-link">
|
||||
<a purpose="sidebar-link" :href="'https://github.com/fleetdm/fleet/edit/main/articles/'+thisPage.sectionRelativeRepoPath"> <img src="/images/icon-edit-16x16@2x.png" alt="Suggest an edit">Suggest an edit</a>
|
||||
|
||||
Vendored
-5
@@ -144,11 +144,6 @@
|
||||
<p>Thumbtack migrates more than 90% of Macs with no IT intervention.</p>
|
||||
<a href="/case-study/thumbtack">Read their story</a>
|
||||
</div>
|
||||
<div purpose="article-card" @click="clickGotoCaseStudyLink('/case-study/proton', $event)">
|
||||
<img alt="Proton logo" src="/images/logo-proton-99x32@2x.png">
|
||||
<p>Proton manages devices with the same privacy and security standards it promises its users.</p>
|
||||
<a href="/case-study/proton">Read their story</a>
|
||||
</div>
|
||||
<% /* Automatically created cards for anonymous case studies */%>
|
||||
<% for(let article of initalCaseStudyLinksToShow) { %>
|
||||
<div purpose="article-card" @click="clickGotoCaseStudyLink('<%- article.url %>', $event)">
|
||||
|
||||
Reference in New Issue
Block a user