Backed byY

Autonomous AI-native security audits.

Winfunc combines SAST, DAST, IaC, and SCA into one AI-native security audit that finds real vulnerabilities, proves impact, and helps teams ship fixes.

View findings

For teams shipping code that can't fail quietly · For companies where security is part of the product · For engineers who want proof before they merge

Finds real 0-days and P0s in minutes — see for yourself

Finds what other AI scanners miss — hear from our customers

Found real vulnerabilities in

AnthropicBetter AuthBraveBunCal.comGoogleGumroadHoppscotchKastleMicrosoftThe New York TimesNVIDIASentrySupabaseAnthropicBetter AuthBraveBunCal.comGoogleGumroadHoppscotchKastleMicrosoftThe New York TimesNVIDIASentrySupabase

How it works

From signal to fix.

The flow is simple on purpose: find the bug, prove it, hand engineering something they can use.

01

See where the real risk sits.

Winfunc reads the codebase as a system. That keeps attention on reachable issues and cuts out a lot of scanner junk.

Find

02

Show how the bug actually breaks.

Each finding comes with the exploit path, the setup, and the reason it matters. Engineering doesn't have to guess what makes it real.

Prove

03

Hand off fixes people can merge.

Patch guidance stays close to the code path that caused the issue, so teams spend less time translating generic advice into safe changes.

Fix

Evidence

Show the proof.

These views answer the questions teams ask in real reviews: what broke, how it broke, and what to change.

Proof that ends the argument fast.

Exploit verification

Proof that ends the argument fast.

The report shows the exploit path, the blast radius, and the next move. That gives engineering, security, and leadership the same picture.

Follow the bug through the system.

Data-flow analysis

Follow the bug through the system.

You can trace input from entry point to sink, with the surrounding business logic still intact. That's where the expensive bugs usually hide.

Fixes that respect the code around them.

Patch delivery

Fixes that respect the code around them.

The point is simple: move from bug found to patch reviewed and shipped faster.

Selected findings

Public cases with real detail.

The archive shows the kinds of bugs Winfunc finds and how the work gets written up.

View all findings

What customers said

“Winfunc surfaced exploitable issues our own engineering team still wanted to patch immediately.”

We have built security-sensitive systems before, and the initial run still delivered findings with real operational value. The difference is that the output is evidence-led, not noisy.

Dennis, Co-Founder & CEO, Surge

Dennis

Co-Founder & CEO, Surge

YC F24

“The agent found complex bypasses other tools missed, then made verification straightforward.”

The strongest part of the experience is the proof. The report, reproduction path, and remediation guidance are aligned enough that engineering can move fast with confidence.

Noah, Co-Founder & CEO, Scout

Noah

Co-Founder & CEO, Scout

YC W25

“The onboarding was fast, the scan was deep, and the team understood the return on engineering time.”

For security work to be adopted it has to be both easy to start and worth the effort. Winfunc delivered both for our team on the first pass.

Ram, Co-Founder, Sei

Ram

Co-Founder, Sei

YC W22

“Winfunc offers a great user experience for discovering and researching potential security issues.”

For a company like us where security is the top priority, having a platform like Winfunc to catch these issues early before they impact the broader ecosystem is a huge plus. A very well-thought-out product.

Bereket Engida, Founder, Better Auth

Bereket Engida

Founder, Better Auth

YC X25

Research

Notes from the lab.

Write-ups, disclosures, and technical thinking from the team.

All research

FAQ

Common questions.

Winfunc uses a combination of on-the-fly generated tree-sitter queries, language servers, and LLM-powered analysis to ingest codebase context with high accuracy. We support all major programming languages.

We have demonstrated this by finding vulnerabilities in the old HackerNews codebase written in Arc, a dialect of Lisp with no parsers in the wild.

Next

Start with the work.

Book a call, request an audit, or read the public findings first.

View findings