Vercel CEO Guillermo Rauch on the fight to split off models from agents 46%

By Russell Brandom0%

7/6/2026, 7:49:10 PM

BS Summary: This article contains 31 faulty reasoning types, including False Dilemma, Attempt to Sell a Product or Service, and Hasty Generalization, with Self-Serving Bias as the most egregious example at 13.5% saturation with 143 hits. Analysis detected 1,703 faulty-reasoning hits from 1,058 analyzed words, generating a BS Score of 48.3% and a BS Rank of 46% (11,818 of 21,886 articles). This article is better (less manipulative) than 54.00% of the article peer group.

Known for its cloud infrastructure that allows developers to deploy agents without managing servers, Vercel has quietly become one of the most central companies in AI software. 
The company currently sees 6 million deployments a day, half of them triggered by coding agents, and more than 1 trillion tokens flow through the company’s AI gateway daily. 
After the company's ShipNYC conference last week, we sat down with Vercel CEO Guillermo Rauch for his take on this moment in AI, and how platform companies like Vercel end up competing with major labs. 
Here’s a lightly edited transcript. 
**It feels like there’s a different energy in the community this year, fewer pilot programs and more focus on how to make things work well in practice. 
I’m sure you’ve seen that a lot with clients, but I’m curious what that journey has looked like within Vercel. 
** 
Last year was about prototyping. 
The sky’s the limit, unleash the agents, everyone can build, and so on. 
We did that, and we learned a lot because we had hundreds of agents organically developed and deployed within the company, and then you started getting into the realities of agents in production, and some of the challenges. 
The biggest lesson for me was the home-run use cases, the two killer apps of agents. 
One is the coding agent, of course. 
That’s driving a lot of the token utilization in the world, but when you produce so much software, you need somewhere to put it. 
The second killer app of agents is the internal agent that helps you run the company. 
The challenge there is, how do you securely access data? 
How do you audit what the agent is doing? 
How do you get a trail of all of the tool calls and access controls that the agent had to incur in order to get a job done? 
To solve that, we came up with this framework called Eve, where you can lay out an agents’ instructions and skills in natural language. 
And another tool is Vercel Sandbox, where you put the agent in a little cage. 
It can have the freedom still to express its intelligence, but then you can apply policy on what data it can access and what data can leave the sandbox. 
**What sort of problems does that help you avoid? 
** 
For [the] sandbox, the biggest advantage is data control. 
A real risk of AI that I always think about is, when you get a coding IDE like Devin or Cursor, if you’re in the wrong setting, they may train on your entire codebase. 
I remember talking to the president of Airbus about this. 
You have decades of wealth of very specific C++ code for aerospace engineering. 
Someone comes in and installs the wrong developer tool and boom, all the code goes out to the cloud for training. 
**I’m curious to hear more about that second killer use case. 
We all know about coding agents, but what does an internal corporate agent look like in practice? 
** 
So, there’s a sales rep sitting out there [in Vercel’s office]. 
She works on install base. 
Her job is to grow existing accounts. 
The bottleneck for people like her has not been her creativity, intelligence, ability to build relationships, it’s been data. 
“I don’t understand what accounts are growing faster. 
Give me the five accounts that have added the most seats in the last two weeks, so that I can prioritize my work.” 
She couldn’t ask that question in the past. 
She needed to wait until a Q1 project for a new sales dashboard completed. 
We were in that bottleneck for years at Vercel, and it was really frustrating because on the R&D side, we’re the fastest-moving company in the world. 
But on the sales engine, the Salesforce engineering [side], I was so incompetent. 
I had never opened Salesforce in my life when I started. 
Now I feel like I can actually have impact across the entire company, because Eve can be used for our customer-facing agents and can be used to improve productivity. 
Same technology, it’s just APIs. 
Agents are forcing companies to open up, and that will have dramatic long-term implications. 
So many of these SaaS giants build their entire kingdoms on trapping your data, and that’s incompatible with agents. 
**How do you see client relationships with the big AI labs changing? 
** 
Last year there were a lot of people picking one lab partner  saying they would build everything on OpenAI or Anthropic. 
Now they're saying, I understand how this all works  model, harness, data platform, sandbox, gateway  every piece is plug and play. 
You can use OpenAI, you can use Anthropic, or you can use Gemini. 
We're seeing a lot of growth of Gemini, even though it's not on the news as much, because people are optimizing for production now. 
The reality is, when you're optimizing for production, you start looking at a price/performance, and Gemini models have awesome price/performance characteristics. 
You also bring in open models, so DeepSeek and GLM-5.2 are taking off. 
The data doesn't lie. 
**There are places where you’re in direct competition with the labs too, right? 
Just the other week, OpenAI released a new set of tools that publish directly to the web without having to leave the OpenAI enclave. 
** 
It’s a natural next step for them to host little websites. 
And it’s a great opening for us, because now people will think of ChatGPT as a tool for making websites. 
And then if they keep asking the model questions about web hosting, the model recommends us. 
But you’re right, as the models or platforms add more capabilities, they come in direct competition with the infrastructure platforms that already exist. 
I really think at this point we're deciding on whether the model and the agent are going to be coupled. 
Do you get all your intelligence from one place? 
Or do you get a module or a library or a building block from one provider, and then you build on top of it. 
That’s more like software engineering has always been, and that’s really what we’re bringing to market. 
We're going to be the AWS of this generation, so obviously we're fighting for a world of open protocols. 
Article reasoning-pattern comparisonThis article: 8.8%Russell Brandom: 7.1%TechCrunch: 3.0%Confirmation Bias8.8%This article: 0.0%Russell Brandom: 0.6%TechCrunch: 1.4%Anchoring Bias0.0%This article: 7.5%Russell Brandom: 3.6%TechCrunch: 3.5%Availability Heuristic7.5%This article: 1.0%Russell Brandom: 0.9%TechCrunch: 1.1%Representativeness Heuristic1.0%This article: 2.6%Russell Brandom: 1.9%TechCrunch: 0.6%Hindsight Bias2.6%This article: 9.9%Russell Brandom: 6.5%TechCrunch: 2.5%Overconfidence Bias9.9%This article: 0.0%Russell Brandom: 2.7%TechCrunch: 4.8%Framing Effect0.0%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.6%Loss Aversion0.0%This article: 1.5%Russell Brandom: 1.5%TechCrunch: 0.6%Status Quo Bias1.5%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.2%Sunk Cost Effect0.0%This article: 9.2%Russell Brandom: 7.3%TechCrunch: 4.9%Optimism Bias9.2%This article: 0.0%Russell Brandom: 0.7%TechCrunch: 1.3%Pessimism Bias0.0%This article: 8.2%Russell Brandom: 1.9%TechCrunch: 5.0%Negativity Bias8.2%This article: 13.5%Russell Brandom: 4.9%TechCrunch: 2.1%Self-Serving Bias13.5%This article: 1.8%Russell Brandom: 0.3%TechCrunch: 0.5%Fundamental Attribution Error1.8%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.1%Actor-Observer Bias0.0%This article: 1.6%Russell Brandom: 0.3%TechCrunch: 0.6%In-Group Bias1.6%This article: 0.0%Russell Brandom: 0.3%TechCrunch: 0.3%Out-Group Homogeneity Bias0.0%This article: 2.6%Russell Brandom: 1.1%TechCrunch: 3.5%Halo Effect2.6%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.1%Horn Effect0.0%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.0%Dunning-Kruger Effect0.0%This article: 4.5%Russell Brandom: 3.7%TechCrunch: 2.3%Recency Bias4.5%This article: 1.7%Russell Brandom: 0.3%TechCrunch: 0.3%Primacy Effect1.7%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.1%Blind-Spot Bias0.0%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.3%Ad Hominem0.0%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.6%Straw Man0.0%This article: 2.6%Russell Brandom: 1.5%TechCrunch: 4.4%Appeal to Authority2.6%This article: 13.3%Russell Brandom: 2.4%TechCrunch: 1.7%False Dilemma13.3%This article: 2.0%Russell Brandom: 1.4%TechCrunch: 0.7%Slippery Slope2.0%This article: 1.8%Russell Brandom: 0.8%TechCrunch: 0.2%Circular Reasoning1.8%This article: 12.7%Russell Brandom: 11.9%TechCrunch: 6.0%Hasty Generalization12.7%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.2%Red Herring0.0%This article: 1.2%Russell Brandom: 0.8%TechCrunch: 1.1%Bandwagon1.2%This article: 6.1%Russell Brandom: 1.6%TechCrunch: 2.2%Appeal to Emotion6.1%This article: 3.9%Russell Brandom: 1.1%TechCrunch: 0.6%Begging the Question3.9%This article: 5.1%Russell Brandom: 3.2%TechCrunch: 2.9%Post Hoc (False Cause)5.1%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.1%Tu Quoque0.0%This article: 0.0%Russell Brandom: 0.8%TechCrunch: 0.5%Burden of Proof0.0%This article: 1.0%Russell Brandom: 0.9%TechCrunch: 0.2%Appeal to Nature1.0%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.3%Composition/Division0.0%This article: 10.1%Russell Brandom: 2.9%TechCrunch: 2.4%Anecdotal10.1%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.1%No True Scotsman0.0%This article: 0.5%Russell Brandom: 3.8%TechCrunch: 2.0%Ambiguity (Equivocation)0.5%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.0%Gambler’s Fallacy0.0%This article: 0.0%Russell Brandom: 0.3%TechCrunch: 0.2%Middle Ground0.0%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.0%Personal Incredulity0.0%This article: 2.3%Russell Brandom: 0.8%TechCrunch: 0.1%Special Pleading2.3%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.1%Genetic Fallacy0.0%This article: 0.0%Russell Brandom: 0.9%TechCrunch: 2.0%Unattributed Quote0.0%This article: 2.2%Russell Brandom: 1.1%TechCrunch: 0.7%Quote-first Misdirection2.2%This article: 5.1%Russell Brandom: 4.0%TechCrunch: 4.6%Biased Writer Voice5.1%This article: 3.6%Russell Brandom: 0.6%TechCrunch: 0.8%Indoctrination3.6%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.1%Politically Left Leaning Bias0.0%This article: 0.0%Russell Brandom: 0.0%TechCrunch: 0.1%Politically Right Leaning Bias0.0%This article: 13.1%Russell Brandom: 6.8%TechCrunch: 4.9%Attempt to Sell a Product or S…13.1%

1058 words analyzed.

Speakers

1speaker72%attributed speech298writer words
Voice mapSelect a segment to jump to its words
Guillermo Rauch • 13 words • 0.0% coverageWriter's voice • 27 words • 100.0% coverageWriter's voice • 29 words • 0.0% coverageWriter's voice • 35 words • 0.0% coverageWriter's voice • 5 words • 0.0% coverageWriter's voice • 27 words • 100.0% coverageWriter's voice • 20 words • 0.0% coverageWriter's voice • 1 words • 0.0% coverageGuillermo Rauch • 5 words • 0.0% coverageGuillermo Rauch • 13 words • 0.0% coverageGuillermo Rauch • 38 words • 0.0% coverageGuillermo Rauch • 16 words • 0.0% coverageGuillermo Rauch • 7 words • 0.0% coverageGuillermo Rauch • 24 words • 0.0% coverageGuillermo Rauch • 16 words • 0.0% coverageGuillermo Rauch • 10 words • 0.0% coverageGuillermo Rauch • 9 words • 0.0% coverageGuillermo Rauch • 28 words • 0.0% coverageGuillermo Rauch • 24 words • 100.0% coverageGuillermo Rauch • 15 words • 100.0% coverageGuillermo Rauch • 29 words • 0.0% coverageWriter's voice • 9 words • 0.0% coverageWriter's voice • 1 words • 0.0% coverageGuillermo Rauch • 9 words • 0.0% coverageGuillermo Rauch • 34 words • 0.0% coverageGuillermo Rauch • 10 words • 0.0% coverageGuillermo Rauch • 13 words • 0.0% coverageGuillermo Rauch • 21 words • 0.0% coverageWriter's voice • 11 words • 0.0% coverageWriter's voice • 17 words • 0.0% coverageWriter's voice • 1 words • 0.0% coverageGuillermo Rauch • 11 words • 0.0% coverageGuillermo Rauch • 5 words • 0.0% coverageGuillermo Rauch • 7 words • 0.0% coverageGuillermo Rauch • 19 words • 0.0% coverageWriter's voice • 8 words • 0.0% coverageWriter's voice • 23 words • 100.0% coverageGuillermo Rauch • 8 words • 0.0% coverageGuillermo Rauch • 14 words • 0.0% coverageGuillermo Rauch • 26 words • 0.0% coverageGuillermo Rauch • 13 words • 0.0% coverageGuillermo Rauch • 11 words • 0.0% coverageGuillermo Rauch • 29 words • 100.0% coverageGuillermo Rauch • 5 words • 0.0% coverageGuillermo Rauch • 14 words • 0.0% coverageGuillermo Rauch • 19 words • 100.0% coverageWriter's voice • 12 words • 0.0% coverageWriter's voice • 1 words • 0.0% coverageGuillermo Rauch • 22 words • 0.0% coverageGuillermo Rauch • 23 words • 0.0% coverageGuillermo Rauch • 13 words • 0.0% coverageGuillermo Rauch • 24 words • 0.0% coverageGuillermo Rauch • 21 words • 0.0% coverageGuillermo Rauch • 13 words • 0.0% coverageGuillermo Rauch • 4 words • 0.0% coverageWriter's voice • 13 words • 0.0% coverageWriter's voice • 24 words • 0.0% coverageWriter's voice • 1 words • 0.0% coverageGuillermo Rauch • 11 words • 0.0% coverageGuillermo Rauch • 20 words • 100.0% coverageGuillermo Rauch • 16 words • 100.0% coverageGuillermo Rauch • 23 words • 0.0% coverageGuillermo Rauch • 20 words • 0.0% coverageWriter's voice • 9 words • 0.0% coverageWriter's voice • 24 words • 0.0% coverageGuillermo Rauch • 16 words • 100.0% coverageGuillermo Rauch • 19 words • 100.0% coverage
Selected voice

Guillermo Rauch

86%flagged-word coverage
760 attributed words100% of attributed speech80% writer coverage
0%10.0%20.0%Attempt to Sell a Product +18.3 ptsWriter: 0.0%Guillermo Rauch: 18.3%18.3%Biased Writer Voice-18.1 ptsWriter: 18.1%Guillermo Rauch: 0.0%0.0%Quote-first Misdirection-7.7 ptsWriter: 7.7%Guillermo Rauch: 0.0%0.0%Indoctrination+5.0 ptsWriter: 0.0%Guillermo Rauch: 5.0%5.0%

Attribution is sentence-level. Pattern percentages are calculated only from words assigned to that voice.

Loading…
Loading…
Loading…
Loading…

Analysis

Hover over highlighted words in the article to view the associated bias or fallacy analysis.