Guillermo Rauch
@rauchg
@vercel CEO
Guillermo Rauch, CEO of Vercel, is a leading voice in AI, DevTools, and startups. With over 440K followers, he shares insights on cutting-edge technology and product development, offering brands a direct connection to a highly engaged and influential tech audience.
The @vercel team is always listening and engaging with customers on @x. We shape the product as a result of these conversations. Vercel gives us the velocity to ship, X gives us a nonstop stream of user feedback. Thanks @simhskal & @riyvir!
Vercel AI Gateway now supports video generation. Grok Imagine Video & Image are 🆓 until tomorrow. We used @v0 to create an open source Creative Studio powered by @xai Grok. Create images, videos, or make your own design tool! https://v0-grokstudio.vercel.app – it's quite fast. Some cool technical tidbits: ▪️ Vercel Workflows for reliable generation Video generation can take long. Users might restart their browsers or their wifi / LTE might drop. We smooth over that automatically. ▪️ Instant vector search Try searching the public generations. Now back to me. We used @mixedbreadai to index the content visually, so you can search 𝚋𝚕𝚊𝚌𝚔 𝚏𝚎𝚕𝚒𝚗𝚎 and get a cat (try it!) ▪️ Vercel AI Gateway All existing and future Grok models are accessible via our gateway without extra setup. When you deploy to Vercel, you get access to hundreds of models with a single account and unified billing It's obviously built with @nextjs (RSC). Open it in v0 to make it your own! h/t @estebansuarez for shipping this.
https://vercel.com/kb/guide/migrate-to-vercel-from-cloudflare
We've identified, responsibly disclosed, and confirmed 2 critical, 2 high, 2 medium, 1 low security vulnerabilities in Cloudflare's vibe-coded framework Vinext. We believe the security of the internet is the highest priority, especially in the age of AI. Vibe coding is a useful tool, especially when used responsibly. Our security research and framework teams are extending their help and expertise to Cloudflare in the interest of the public internet's security.
Glimpse of a world of fully generative interfaces. AI → JSON → UI: http://github.com/vercel-labs/json-render https://x.com/ctatedev/status/2011589295862395238/video/1
Almost every SaaS app inside Vercel has now been replaced with a generated app or agent interface, deployed on Vercel. Support, sales, marketing, PM, HR, dataviz, even design and video workflows. It’s shocking. The SaaSpocalypse is both understated and overstated. Over because the key systems of record and storage are still there (Salesforce, Snowflake, etc.) Understated because the software we are generating is more beautiful, personalized, and crucially, fits our business problems better. We struggled for years to represent the health of a Vercel customer properly inside Salesforce. Too much data (trillions of consumption data points), the ontology of Vercel was a mismatch to the built-in assumptions, and the resulting UI was bizarre. We generated what we needed instead. When you don’t need a UI, you just ask an agent with natural language. We’ve also been moving off legacy systems with poor, slow, outdated, and inconsistent APIs, as well as just dropping abstraction down to more traditional databases. UI is a function 𝑓 of data (always has been), and that 𝑓 is increasingly becoming the LLM.
In love with this aesthetic http://skills.sh https://x.com/rauchg/status/2013662530502078573/photo/1
A Vercel user reported an issue that sounded extremely scary. An unknown GitHub OSS codebase being deployed to their team. We, of course, took the report extremely seriously and began an investigation. Security and infra engineering engaged. Turns out Opus 4.6 *hallucinated a public repository ID* and used our API to deploy it. Luckily for this user, the repository was harmless and random. The JSON payload looked like this: "𝚐𝚒𝚝𝚂𝚘𝚞𝚛𝚌𝚎": { "𝚝𝚢𝚙𝚎": "𝚐𝚒𝚝𝚑𝚞𝚋", "𝚛𝚎𝚙𝚘𝙸𝚍": "𝟿𝟷𝟹𝟿𝟹𝟿𝟺𝟶𝟷", // ⚠️ 𝚑𝚊𝚕𝚕𝚞𝚌𝚒𝚗𝚊𝚝𝚎𝚍 "𝚛𝚎𝚏": "𝚖𝚊𝚒𝚗" } When the user asked the agent to explain the failure, it confessed: The agent never looked up the GitHub repo ID via the GitHub API. There are zero GitHub API calls in the session before the first rogue deployment. The number 913939401 appears for the first time at line 877 — the agent fabricated it entirely. The agent knew the correct project ID (prj_▒▒▒▒▒▒) and project name (▒▒▒▒▒▒) but invented a plausible-looking numeric repo ID rather than looking it up. Some takeaways: ▪️ Even the smartest models have bizarre failure modes that are very different from ours. Humans make lots of mistakes, but certainly not make up a random repo id. ▪️ Powerful APIs create additional risks for agents. The API exist to import and deploy legitimate code, but not if the agent decides to hallucinate what code to deploy! ▪️ Thus, it's likely the agent would have had better results had it not decided to use the API and stuck with CLI or MCP. This reinforces our commitment to make Vercel the most secure platform for agentic engineering. Through deeper integrations with tools like Claude Code and additional guardrails, we're confident security and privacy will be upheld. Note: the repo id above is randomized for privacy reasons.
We're introducing 𝚜𝚔𝚒𝚕𝚕𝚜 – the "npm" of AI skills. Excited to see an open, agent-agnostic ecosystem of skills flourish. To get started, try: ▲ ~/ npx skills i vercel-labs/agent-skills https://x.com/rauchg/status/2012345679721771474/photo/1
Incidentally this is why I like @xai’s mission to “understand the universe”. I want AI to make us super geniuses not super idiots 😂