Key points
- CEO Andy Yen called a request for pentesting new code "bullshit and loser thinking".
- Staff were told AI usage could determine job retention before the plan was dropped.
- The incident highlights tension between speed and the careful processes users expect.
A Hacker News discussion with over sixty points summarises a report that Proton’s leadership is prioritising artificial intelligence adoption over traditional security checks. The conversation centres on an internal exchange where CEO Andy Yen dismissed an engineer’s request for time to pentest new code before shipping it.A privacy company’s boss told staff to use AI instead of checking code for security flaws.Proton’s CEO dismissed a pre-shipment pentesting request, urging AI coding adoption instead. Yen reportedly told the team to stop handcrafting code and use AI more, labelling the security concern as loser thinking. This interaction was shared within the company’s security Slack channel.
The figures
The Hacker News thread regarding this incident accumulated sixty-three points and nineteen comments. The discussion references an investigation by 404 Media into Proton’s internal push for AI.reported No specific version numbers or CVE identifiers are mentioned in the source material. The timeline is described as "this week" relative to the publication of the 404 Media report.
Behind the figures
The primary evidence comes from a blog post by Raed, which cites a 404 Media investigation.reported The author, a long-term Proton subscriber, interprets the leaked Slack messages as a shift in corporate culture. The Hacker News comments reflect community reaction to these claims. The figures represent engagement on the discussion platform rather than independent verification of the internal events.
What changes, what does not
The source material indicates that Proton’s leadership previously emphasised careful, slow shipping as a core value. The reported incident suggests a move towards faster release cycles driven by AI coding agents.reported However, the plan to tie AI usage to job retention was dropped after it leaked. The company’s fundamental service model remains unchanged, but the internal development process appears to be shifting.
What builders can do with it
Developers can observe how Proton’s leadership is integrating AI into its coding pipeline. The documented capability is the use of AI for writing code, replacing handcrafted methods. The limit is the CEO’s dismissal of a specific pentesting request. Builders can note that accountability for shipped code remains with human engineers, as the author states someone must review and test model output.
Why it matters
- Policy readers can see how privacy-focused firms balance security protocols with rapid AI adoption.
- The incident illustrates the risk of leadership dismissing security concerns in favour of speed.
- It highlights the potential for AI usage mandates to create internal culture conflicts.
- The dropped plan to tie jobs to AI use shows the volatility of such internal policies.
Topics: AI, privacy, Proton, security, software development
Updated
Then / now / next
Proton users valued the company’s careful, slow shipping process as a security feature.
Leadership is pushing for AI-driven speed, dismissing security pentesting requests.
Watch for further community reaction on Hacker News regarding the leaked communications.
Story timeline
- Then Proton users valued the company’s careful, slow shipping process as a security feature.
- 01 Nov 2026 It wasn't AI that flipped Proton's charge
- Now Leadership is pushing for AI-driven speed, dismissing security pentesting requests.
- Next Watch for further community reaction on Hacker News regarding the leaked communications.
The strongest doubt
Counterpoint from the sources
One employee on Reddit claimed Yen was fine with pentesting if it did not slow the pipeline, though the author views this as agreeing with the corporate line.
For readers
Policy
- Privacy firms face pressure to adopt AI, potentially altering security guarantees.
- Internal leadership attitudes towards security can impact user trust.
Developers
- AI coding tools are becoming the norm, requiring new review processes.
- Accountability for AI-generated code remains with human engineers.
Consumers
- Users pay for confidence in careful code development.
- Rapid AI adoption may compromise the security model they rely on.
Ask the article
Local keyword search of this article; no generated answers.Did this article give you the evidence you needed?
Your choice stays on this device. No public tally.Questions readers ask
Did Proton confirm the Slack messages?
The source material cites a 404 Media investigation and a blog post, not an official Proton confirmation.
Was the pentesting request denied?
The CEO called the request loser thinking and told the team to use AI instead.
Is Proton still using AI for coding?
The CEO told the team to stop handcrafting code and use AI more.
Connected stories
Reading receipt
- CEO Andy Yen called a request for pentesting new code "bullshit and loser thinking".
- Staff were told AI usage could determine job retention before the plan was dropped.
- The incident highlights tension between speed and the careful processes users expect.