Guillermo Rauch

Some interesting machine & agent Vercel traffic stats.

• Across the entire Vercel network, 58.18% traffic is bot-originated (last 30d). This was 32% in Jan 2024.

• 60%+ of deployments on Vercel are now agentic, up from ~3% in Jan 2026.

• Up to 83% of pageviews are now coming from agents to Vercel's own documentation sites. The % reliably increases the more we optimize content for them.

I expect 'direct' human internet traffic to basically become a rounding error in coming years. The web will thrive, but it will be built for and by agents.

It's incredible to watch a new kind of economy be born. Agents purchasing infrastructure products and services. We've been shocked by how often they buy from our marketplace via our CLI already. We're now extending this to domains.

Agents can now go full stack, from idea to online business, with a banger domain name 😁

Few things more enjoyable in work and life than discovering new talent. Seeing greatness in people, sometimes even before they fully see it themselves.

One thing the engineering community will (re)discover is that every program can be ① hardened (edge cases squashed, inputs tightened, errors handled) and ② optimized (profiled, benchmarked, rewritten) basically ad infinitum.

There are real costs in every direction: time, attention, opportunity. You can literally explore input spaces that will never be hit or optimize performance of something that will never be used ("you have no users".) Even in an infinite token world, you need to know when to stop and what tradeoffs to accept. Agents will happily drill no matter what.

gm from the best city in the world

“Thinking fast and s̶l̶o̶w̶ a bit less fast under a confidence threshold.”

A very simple feature that I think will be extremely impactful for at-scale AI decision-making.

At this rate AI will get us GTA 7 before GTA 6

Introducing gdp-ts: Ghosts of Departed Proofs for TypeScript.

gdp-ts is a library, linter and AI skill for safer API design. Under this contract, sensitive functions require 'proofs' that the caller performed an authorization check.

The typechecker verifies these proofs at compile time, preventing your team and agents from shipping catastrophic security (and other kinds of) bugs.

While these patterns have existed for quite some time, especially in ecosystems like Haskell, ① human code review and ② cognitive and syntactic overhead made these solutions niche.

The situation is now inverted. Agents are writing more code than we can review, and they *thrive* in tight loops with hard constraints that would frustrate us. We see this with the rise of Rust, borrow checker, code aesthetics debate and all.

The README and examples model a real-world Vercel API product constraint: changing the password on a Project requires a proof of a certain role + a certain entitlement. Thanks to Matt Noonan and Ollie Charles for their research in this space.

github.com/rauchg/gdp-ts

It’s hard to fathom fx.sh getting even faster, but it’s now… much faster 😂

As models speed up (as with Astra 𝚞𝚕𝚝𝚛𝚊𝚏𝚊𝚜𝚝), harness overhead matters more and more.

Next release will feature even better performance for session storage and retrieval, and a big unlock for cloud durability in libfx.

DHH is fundamentally right about Rust. For context, Vercel has been undergoing a Rust-ification (carcinization, technically 🦀) for a while.

One of the first projects we migrated was Turborepo, from Go to Rust¹. The migration completed, but the RoI was actually quite controversial internally.

While Rust was in our eyes better for low-level OS access, something crucial for a build system like Turbo, the human migration costs were very sustantive.

Go is very fast. It's beautifully designed. It's easy to iterate on. We were very conflicted about the migration, because it was *humans* writing the code, *even if we knew Rust was a better choice*.

The calculus has now changed. What's "best for humans" is no longer necessarily "best for business".

FWIW, it's also quite unlikely that Rust is the end-all-be-all toolchain. I'm quite certain there's greener pasture ahead, because Rust itself was designed before the 'supersonic tsunami' of agents hit.

¹ https​://vercel.com/blog/how-turborepo-is-porting-from-go-to-rust

Working on a new little project. The 𝚁𝙴𝙰𝙳𝙼𝙴 is fully written by hand, because it's for human consumption. The documentation internals are AI English, because they're for agents.

This little rule of thumb can make the world better. Blogs, tweets, READMEs: human communication. It's not even about "em dashes" or lack thereof. It's that it's the story-telling moment where you want to connect with other humans through their words.

Summer is finally here! 🌞⛱️

Security will become a larger and larger function in software companies. Security is verification engineering (eg: “my code is probably memory-safe”), as well as capital allocation (“what surface should I throw most tokens at?”)

For startups, it’s a challenge and opportunity. As the world’s paranoia grows given ever-more-sophisticated AI adversaries, how can you trust a 2-person-and-a-dog company?

But conversely, given the dire state of global cybersecurity and increasing reliance on centralization, as always, there’re vast areas that small teams can now disrupt that I’m excited to invest in.

AI will make everything free, including itself. The last domino to fall will be free energy, which is humanity’s final frontier.

We’ve confirmed a KVM 0day through our Vercel Sandbox bounty program. Affecting the industry’s gold standard solution for Linux virtualization.

2026 is wild! Thankful to Paulos and other researchers helping us make the most secure sandbox for agents. Full writeup coming.

Wonderful writeup on Jev + Python

Amazing. Love to see the muse.ai team ship so fast ▲

SvelteKit 3 is a wonder. Congrats to the team. So excited for Async Svelte & Remote Functions to cook.

I built a tiny app, it built & deployed in 15 seconds end-to-end, it’s instant, and fx + opus figured it all out effortlessly.
svelte.dev/blog/sveltekit…

The future is verification-engineering.
Proofs, (e2e) tests, benchmarks, linters…

Some tests will be deterministic, some agentic. This looks great.

The @MicrosoftAI team is training excellent models.
Excited to bring them to @vercel, day zero.