ruben.galindo@directsalespty:~$ cat why_i_started_testing_proton_en.log
FIELD NOTE: This is not a lab report. It's the personal context behind one.
[DISCLOSURE]: This post contains Proton affiliate links. Directsales PTY may earn a commission if you subscribe through them, at no extra cost to you. As always, that relationship doesn't change what I write here.
I've been using Proton Mail and Proton Drive personally since April — not as a test, not as research, just as my own daily email and backup. No client work, no lab environment. Just me, deciding I wanted my own communication encrypted end-to-end, and my own backups outside the usual providers.
A few months in, the pattern that got my attention wasn't a feature. It was the absence of friction. No degraded experience for the sake of privacy. No compromises I had to explain away to myself.
That's when the question shifted from personal to professional: does this hold up outside a personal-use context — under the conditions a business actually needs?
Personal use and enterprise deployment are not the same test. My own daily use tells me Proton works well for one person, one inbox, one Drive. It tells me nothing about domain-wide DKIM/DMARC alignment across a client's infrastructure, or how Proton Drive behaves under sustained sync load, or whether hardware-key MFA holds up against real session-hijacking attempts.
So that's what I started testing — formally, in an isolated lab environment, treating Proton for Business the same way I'd treat any tool before recommending it to a client: with evidence, not enthusiasm.
The results of that testing are here:
- Cryptographic Evaluation of Proton for Business — EN
- Evaluación Criptográfica de Proton para Negocios — ES
Both are still open evaluations, not conclusions. I'm not there yet, and I won't pretend to be.
What I can say today, from months of personal use, is simpler: it earned the right to be tested seriously. That's not nothing. It's also not a recommendation — not yet.
First we see. Then we decide.