Proactive Security for the Code Gen Era

Generated code is the new normal. Google reports that 90% of developers now use AI code-gen products. Cursor’s revenue recently surpassed $2 billion ARR. And after Claude Code’s early 2026 updates, something shifted in the cultural consciousness: everyone realized that they too could now make their own products, websites, and even companies in a weekend. Successful coders used to write 100 lines of code a day. Now, they write 8,000 lines an hour. This isn’t prediction; it’s the world as we live in it now. 

But while code creation has fundamentally changed, security has not. Code review processes were built for a world where people wrote code slowly. That model collapses when code volume increases 100 times or more, compounded by the unreliability of AI-generated code. The faster code is written, the more bugs, errors, and vulnerabilities are introduced. 

The code review process is now the bottleneck to the code-gen productivity explosion. And it’s not just shipping faster that’s at stake; as enterprises increase both models in use and security surfaces, it’s become a question of whether they can safely adopt AI-native development at all.

We’ve led Corridor’s Series A because we believe they’re building the missing layer for this new era: a security and management system designed specifically for code generation. And they're doing it in a way that fundamentally reimagines where in the development process security actually lives.

A New Paradigm: Agentic Coding Security Management (ACSM)

Corridor's approach is what the team calls Agentic Coding Security Management, or ACSM. Instead of finding and fixing vulnerabilities after they've been written, ACSM prevents them at the source: during the code generation process itself. By integrating directly with AI code generation tools like Cursor and Claude Code, Corridor embeds seamless guardrails into development rather than adding friction after the fact. 

Security teams, meanwhile, get real-time visibility into code quality across every coding agent their organization uses. No more waiting for a review cycle. No more hoping the scan catches something before it ships. Security can finally move at the speed of development.

‍Beyond Security and the Multi-Model Management Problem

As the top-performing models change monthly, the best results increasingly come from switching between them. Data indicates that most enterprises are adopting multiple models at once, sometimes even dozens. Developers want flexibility and the ability to cherry-pick the best tools. Enterprises, meanwhile, need standardization, policy enforcement, and visibility, particularly as more and more teams spin up products using code gen. And right now, there's no good answer for how organizations actually govern code quality when their teams are working across Cursor, Claude Code, Lovable, and whatever ships next quarter.

Corridor is that answer. It makes AI code generation enterprise-ready: secure, consistent, and manageable at scale. And its product is already supercharging some of the most forward-thinking and productive teams, including those at Sublime Security and Pylon. 

Security hasn’t kept pace. And the stakes are only rising. Because it’s not just productivity gains at risk; generated code also increases the volume of bugs, errors, and security issues. 

A Team Built for the Moment

At Felicis, we look for teams that spike across dimensions, and pair technical depth and with business instinct. The Corridor team is an incredible example of this. 

Jack Cable, Corridor's founder and CEO, is a genuine legend in the security world. Before founding Corridor, he served as a Senior Technical Advisor at CISA, and is also a well-known white hat hacker. (My favorite fact about Jack is that he's flown for free on United for the better part of a decade after finding and reporting vulnerabilities in their system.) Jack brings the rare combination of hands-on technical depth and real-world policy experience that's invaluable when you're trying to change how an industry thinks about risk.

Ashwin Ramaswami, Corridor’s CTO, is widely regarded in the Stanford community and beyond as a technical prodigy with extraordinary depth in systems and AI. Ashwin has been coding since the age of 9 and has served as a prolific open source contributor, legal scholar, and architect of fast-growing startup infrastructure.

And then there's Alex Stamos, who joined the team full-time before the Series A and after personally investing in the seed round. Former Chief Security Officer at Facebook and SentinelOne, and now a CS lecturer at Stanford, Alex worked on research with both Jack and Ashwin. After seeing their work and how they thought about security, he felt compelled to join them. (Alex is also a venture partner at Felicis.) 

Making “Shift Left” a Reality

"Shift left" — the goal of making security proactive earlier in the development process— has been the security industry's dream for years. Until now, it’s remained mostly aspirational. But Corridor’s making that dream a reality. 

By embedding security and quality management directly into code generation, Corridor doesn't burden or slow developers. It superpowers them. This is the future of product development, and we’re incredibly excited to support the team building it.