Will Agents Surpass Humans? with Vercel CEO Guillermo Rauch | 🟡🔴🔵 MTS Live

Yeah, to give you an idea, that figure was 3% 6 months ago. It's now more than half. So more than 50% of deployments to Vercel are being made by coding agents, which is insane. It seems like the agents are far surpassing humans. When we look at the data for who's browsing the web, over 70% of traffic to vercel.com on the logged out side is agents. So agents are truly taking over both on the production side and the consumption side, which is obviously really good news for anyone that's in the infrastructure business.

Thank you for having me. It's exciting to be here.

Yeah, to give you an idea, that figure was 3% 6 months ago. It's now more than half. So more than 50% of deployments to Vercel are being made by coding agents, which is insane. It seems like the agents are far surpassing humans, and we don't see this only on the code production side. When we look at the data for who's browsing the web, since we started out with Next.js, a framework for building for the web, we have a lot of data on who's visiting the web, who's using the web. Over 70% of traffic to vercel.com on the logged out side is agents. So agents are truly taking over both on the production side and the consumption side, which is obviously really good news for anyone that's in the infrastructure business.

Yeah, so you mentioned I created Next.js. It was about 10 years ago. It was a bright sunny morning and I realized that building for the web was still too difficult. And there were things like Wix, Squarespace, WordPress. You could publish to the web, but if you wanted to create something that's truly production grade, truly great, it was really hard still. Even with the gift of the cloud and all of the things that were happening, open source software, it was too hard. So Next.js was kind of an overnight success. I had been thinking about it for many, many years, and I had been programming front ends for at that point like over 10 years. But I saw that opportunity: can I bring simplicity? Can I emphasize developer experience, not just infrastructure prowess? And now, 10 years later, we're seeing the same exact opportunity. Eve is what we call Next.js for agents. There's a need to create agents. Obviously every enterprise you talk to, every individual, every startup, they want to create agents. And the options are quite insufficient, I would say. You can marry yourself to a model provider, but you guys were just talking about today, a new model dropped, GLM, amazing price performance, open source. And so we wanted to create a framework for building agents that was truly production grade, really easy to use, and gave freedom back to developers and enterprises. That's kind of what we stand for.

Yeah, on the coding agent side, I think we're seeing a massive proliferation of software being built and we can get into the pros and cons. I think it's mostly positive. Anytime a technology gets democratized, it's better for the world, period. I'm anti-gatekeeping. No, it's only real engineering if it comes from Silicon Valley. No, let's democratize software building for everybody in the world. That's what Vercel was created for. So I'm all for it. But I'll tell you, enterprises are petrified and they're still making a lot of mistakes. They're seeing a massive proliferation of shadow IT where you pick up cloud code and then you want to deploy, you want to build. Do they have the infrastructure that goes really well with those coding agents that can absorb all of this new-found deployment power? And so that's kind of what we announced today with our enterprise apps and agents platform, where no matter what coding agent you're using, there's a Vercel plugin and there's a secure platform not exposed to the internet that you can pair with a coding agent. And that dovetails into the other concern that people have: is all of this juice vis-a-vis token spend worth the squeeze vis-a-vis what are we getting in return? Are we getting high-quality products? Are we making customers happy? On one hand, if you're just wasting tokens and you're not shipping software, you're probably doing it wrong. That's why this conference is called Vercel Ship. We want to give you a deployment platform which gives you a baseline: I'm spending tokens and able to ship code. The other consideration is quality. Coding agents are good at adding, adding, adding, adding. Every engineer knows sometimes the best ships, the best patches, the best software releases are all about simplification. They're all about abstraction. They're about deleting code rather than adding code. So there are still shortcomings in the models. They're a really powerful hammer that sees everything as a nail and they follow what you ask and they follow what you say. And they're starting to lightly push back more. I do a lot of what you can call vibe coding or agentic engineering myself. I want to really test the models as they come out. GLM looks great in benchmarks. I also want to find my own personal conviction on how good models are. One of the things I've been noticing about recent models is that they really push back more and they're better architects. I'm super hopeful that we will continue down this path of increasing quality. Everything that you could say a model cannot do, I would add an asterisk there and say, look, I also didn't think models would be operating at a level of principal or super senior engineer today. And lo and behold, they're getting there.

Really, to your point, the running joke is, and I met so many people that do this, everyone turns on YOLO mode in their coding agents. And for good reason. There's also a lot of hype about loop engineering now and models are being trained on longer horizon tasks and they can do a lot by themselves. So people are naturally trusting them more. But you need a guardrail on the other side. For example, with Vercel's secure enterprise deployment platform, the guardrail that we put in is that by default we don't ship to the internet. We protect it with a technology called Vercel Passport. And we say, if you're logged in to your identity provider of choice, like a smaller startup might be Google Workspace, an enterprise might be Okta, we say, okay, you have to be logged in to appreciate your new vibe coding gem that you just put out. And so we created this sort of guardrail around what the coding agent can ship. You also brought up supply chain attacks. Just today Microsoft broke the news of a massive compromise of the JavaScript supply chain. So we're also working on a lot of what we call AI firewalls. When the agent runs compute, we put the agent in a sandbox and we limit what it can do. We say, hey agent, you're free to operate here, but you can only talk to the hostnames and to the subset of the internet that I allow you to talk to. Because the reality is that in order to get really good performance out of agents, you need to give them some power. You need to give them a computer. The metaphor that I use is: in any sort of modern job, the very first thing that happens after you get hired is you're given a computer. And the same thing is happening to agents. When you create an agent with Eve, we give it a sandbox. We give it a computer. But we have to put guardrails around that computer. We have to limit the network. We have to give the developer controls around what data can this agent access. Can this agent access all of the database? A great use case that people are excited about: data analytics. Will my agent be able to access the entirety of my data warehouse? Well, if it goes even slightly off the rails, you could have a massive breach or data compromise or privacy violation in your hands. And so we're basically weighing this consideration: here's the framework, really powerful, really easy to use, but here's the power to put guardrails around this thing.

Yeah. Starting with: it has to be cloud infrastructure. I think we're still in sort of early days of the internet where I was literally hosting my web pages out of my computer in Argentina. I would host my web server Apache, open it, hope that my ISP keeps my IP stable. When I see people using Open Claw and things like that, during the early days wild west, they're hosting it on their own computers. They're giving it full access or maybe they're getting a Mac mini and whatnot. Now we're entering this new phase of realizing: we have to think about security, we have to think about scalability, and very importantly, we have to think about cost efficiency. So one of the really cool attributes of Vercel Sandbox is that it's serverless. When the agent needs to think, it comes online. When the agent sets up a schedule for itself, it can come back to life. If the agent is not doing anything, it can go to sleep. And we even innovated in the pricing model. Vercel Sandbox only charges you for the actual compute. Because what happens a lot with agents is that they can think and think and think for a long time. I was reading some commentary on this new GLM model and someone was saying, wow, this model thinks for 15 minutes before it writes its first line of code. You heard that right. 15 minutes which is pure thinking happening in the GPU. In that case, the sandbox is sort of idling. Think about the economics of cloud infrastructure. This means that Vercel can create massively efficient infrastructure. It can pack a lot of sandboxes. We can have these massive agent swarms. We can enable enterprises to launch huge swaths of agents in parallel. And basically, you're enabling things that are simply not possible with your own computer. My prediction for the rest of 2026 is we're going to see this displacement of agents. We're going to see them graduate from your own computer into the cloud. They're going to parallelize. They're going to reproduce, for lack of a better word. Companies are going to get a lot more bang for their buck. And again, this means more power to the developer. The ability to scale yourself and sort of commandeer a team of agents will become even more of a reality.