---
type: analysis
slug: research-vercel-s-v-is-a-slack-router-over-specialist-agents-not-a-product-you-can-buy
title: "Vercel’s @v is a Slack router over specialist agents, not a product you can buy"
description: "Official blogs, a Ship session, and Guillermo Rauch’s own interviews show @v as Vercel’s internal Slack orchestrator. Customers get the pattern through eve and the Agent Stack, not a turnkey agent named @v."
published_at: 2026-11-08T03:00:00.000Z
topics: ["agents","routing","design","research"]
source_urls: ["https://vercel.com/blog/introducing-eve","https://vercel.com/go/how-vercel-built-a-super-agent-with-eve","https://www.youtube.com/watch?v=HQXi4snP36I","https://vercel.com/kb/guide/marketing-team-eve","https://www.linkedin.com/posts/rauchg_we-built-an-agent-that-powers-our-companys-activity-7490034361271144449-ctEp","https://vercel.com/blog/anyone-can-build-agents-but-it-takes-a-platform-to-run-them","https://vercel.com/blog/vercel-ship-2026-recap","https://eve.dev/","https://www.theregister.com/devops/2026/06/19/vercel-debuts-eve-open-source-agent-framework-tries-to-fix-shadow-ai-with-passport/5258726","https://thenewstack.io/vercel-launches-eve-an-open-source-framework-that-treats-agents-as-directories/","https://techcrunch.com/2026/07/06/vercel-ceo-guillermo-rauch-on-the-fight-to-split-off-models-from-agents/","https://vercel.com/ship/sf/session/superintelligence-at-work","https://vercel.com/blog/vercel-for-enterprise-apps-and-agents","https://rss.com/podcasts/a-new-vibe/"]
author: "Andrey Reshetnikov"
author_profile: https://newruntime.com/owner-profile.md
---
Vercel CEO Guillermo Rauch used LinkedIn to say the company had built @v, an internal agent that now sits in day-to-day work, grows in Slack interactions and token use, keeps per-user memory and schedules, and is both powered by and the design basis for eve. He contrasted that with plugging in a vendor Slack bot: if agents become how companies run, control of source, runtime, data, and tokens matters. The newsroom flagged the item because the basket held only that post, with no docs page, no mechanism, and a real risk of mixing @v up with Vercel’s public marketing-team eve template.

That gap can be closed. Vercel’s June 17, 2026 eve launch post names V as the Slack routing agent in front of more than a hundred production specialists. A Ship 2026 San Francisco session and the October 15 recap describe how the company built v in Slack, grounded in internal data and secured by Connect and Passport. Rauch gave the same account in a recorded interview: employees type @V, and an orchestrator delegates. Independent coverage of eve’s launch repeated the internal routing-agent claim, and TechCrunch quoted Rauch calling the internal run-the-company agent one of two killer apps of agents. For builders, this is an operating-model signal about topology and ownership, not a new chatbot brand.

## What we checked

- **What does @v actually do inside Vercel, and is there a public primary source beyond LinkedIn?** confirmed. @v, also written V or v, is a Slack-native orchestrator: employees mention it, and it routes work to specialists such as d0 for warehouse questions, content and support agents, coding tools, and v0. Primary sources now include Vercel’s June 17, 2026 eve launch post, a Ship SF session page, the October 15, 2026 Ship recap, and a recorded Rauch interview, not only the LinkedIn post. [1][12][7][3][5]
- **Is this distinct from the already processed Eve marketing-team template?** confirmed. Yes. The marketing-team eve guide is a customer template: one Slack lead routes to five marketing specialists (product, content, social, SEO, email) with Notion, Typefully, and Resend. @v is Vercel’s company-wide operations agent spanning finance, comms, docs, marketing, engineering, and analytics, and Rauch says it both runs on and helped design eve. [4][5][1]
- **Vercel is selling a turnkey product named @v that customers can buy.** refuted. No public product, pricing page, or SKU named @v appears in the official materials opened here. Ship SF frames v as intelligence you cannot buy: a superagent grounded in Vercel’s data and guardrails. What Vercel ships is eve plus Connect, Passport, Sandbox, Workflows, and AI Gateway so other companies can build their own equivalent. [12][8][1][13]
- **@v is a Slack front-door router over specialist agents rather than one undifferentiated model.** confirmed. The eve blog says everything goes to V in Slack first, which selects the agent that can answer. Rauch’s interview calls V the orchestrating agent and a router, analogous to a Jarvis UX over hundreds of internal tools, with a dedicated company agent distinct from the customer-facing @vercel assistant. [1][3][2]

## What we found

- Inside Vercel, @v is the Slack handle for an orchestrator, not a single specialist. The eve launch post says the company runs more than a hundred production agents and that employees send work to V first so it can pick the agent that can answer. A Ship demo landing page shows V routing a business question to d0 for analysis, then to v0 for a visualization, on eve plus AI Gateway, Workflows, and Sandbox. In interview, Rauch says anyone at Vercel can @V in Slack for content, customer data, site changes, coding-agent delegation, or production queries, and that V is distinct from the customer-facing @vercel assistant. [1][2][3]
- The public marketing-team template is a narrower cousin, not @v itself. Vercel’s knowledge-base guide describes one lead that briefs exactly one of five marketing specialists, with irreversible Resend and Typefully actions paused for Slack approval. @v is described as company-wide operations: LinkedIn lists finance, comms, docs, marketing, engineering, and business analytics, plus per-user memory, workflows, and schedules. Treating the template as the internal agent would understate the router-and-fleet design Vercel actually runs. [4][5]
- The specialist behind much of the load is d0, not V acting alone. The eve post calls d0 the most-used internal tool, handling more than 30,000 warehouse questions a month in Slack, with each query scoped to the asker’s permissions. An earlier February 9, 2026 platform post says one person built d0 in a few weeks on 20 percent time using Sandbox, Fluid compute, and AI Gateway. The Ship 2026 recap adds that Abhi Sivasailam said 45 percent of d0’s questions now come from other agents rather than people, which is consistent with a superagent sending work downstream. [1][6][7]
- Vercel’s commercial move is to extract the harness, not to sell @v. eve.dev describes a filesystem-first, Apache-2.0 framework, currently in beta, that runs on Vercel or a team’s own infrastructure, with durable sessions, sandboxes, approvals, subagents, channels, and schedules. The Register quoted CTO Malte Ubl that builders put files in the right places and the framework orchestrates the lifecycle, and that Vercel is committed to making eve work off-platform even though deploy-to-Vercel is the default. The New Stack, covering launch day, reported more than 100 internal agents including a Slack data agent used tens of thousands of times a month and a routing agent that directs questions. TechCrunch’s July 6, 2026 interview with Rauch named coding agents and the internal company agent as the two killer apps, with eve and Sandbox as the response to audit, access, and data-exfiltration ris [8][9][10][11]
- Identity and short-lived credentials are part of the @v story, not an afterthought. The Ship SF session says v is governed by Vercel guardrails and secured end to end by Connect and Passport, then placed in Slack. The June 16, 2026 Enterprise Apps and Agents post says Passport puts internal apps and agents behind the company IdP by default, and Connect issues per-task credentials for systems such as Slack, GitHub, Snowflake, Salesforce, and Linear instead of long-lived env secrets. The October 15 recap says Matt Lewis of Vercel and Mala Neti of Slack walked through that design, and that Connect is generally available. Rauch’s LinkedIn ownership line (source to runtime to data to token) is the same thesis in plainer words: a vendor Slack bot is their agent, not yours. [12][13][7][5]

## What it means

Builders should copy the topology, not the brand. The useful pattern is one employee-facing front door in the chat system people already use, a router that delegates to permission-scoped specialists, durable execution with human approval on irreversible writes, and identity that follows the human rather than a shared bot token. Vercel’s marketing-team template is a good first slice of that pattern for one function; @v is the company-scale version, and eve is the extracted shape. Do not wait for a lab to ship “your company’s agent.” Rauch’s point, echoed in TechCrunch, is that the run-the-company agent is now a killer app, and the durable advantage is the skills, tools, evals, and data access you own.

Treat vendor chat integrations as prototypes. If finance, customer data, or production systems are in scope, you need traces, scoped credentials, sandboxing, and a contribution path so teams add capabilities without spawning a second fleet. Vercel’s own numbers for d0 and agent-to-agent traffic show the router becomes real load, not a demo. What remains marketing is the claim that every job already runs through @v and that usage is growing exponentially: those are CEO statements without an independent usage report.

## Still open

- No independent measurement was found of @v’s daily users, token spend, error rate, or how often it acts in finance and comms without a human.
- The precise human-in-the-loop policy for @v on irreversible actions is not published the way the marketing-team template publishes Resend and Typefully gates.
- Rauch said a V team exists and that hundreds of millions of dollars of revenue depend on the well-being of this agent; those claims were not corroborated in filings or a detailed architecture doc.
- How fully eve can be self-hosted in production, versus defaulting to Vercel’s Agent Stack, is still a moving target between the June 2026 launch coverage and today’s eve.dev beta language.

## Sources

1. [Introducing eve](https://vercel.com/blog/introducing-eve) (primary)
2. [How Vercel Built a Superagent with eve](https://vercel.com/go/how-vercel-built-a-super-agent-with-eve) (primary)
3. [The AI Agent Every Company is About to Build | Vercel CEO Guillermo Rauch](https://www.youtube.com/watch?v=HQXi4snP36I)
4. [Run a marketing team from Slack with eve](https://vercel.com/kb/guide/marketing-team-eve) (primary)
5. [We built an agent that powers our company's internal operations called @v (Guillermo Rauch)](https://www.linkedin.com/posts/rauchg_we-built-an-agent-that-powers-our-companys-activity-7490034361271144449-ctEp) (primary)
6. [Anyone can build agents, but it takes a platform to run them](https://vercel.com/blog/anyone-can-build-agents-but-it-takes-a-platform-to-run-them) (primary)
7. [Vercel Ship 2026 recap](https://vercel.com/blog/vercel-ship-2026-recap) (primary)
8. [eve](https://eve.dev/) (primary)
9. [Vercel debuts eve open source agent framework, tries to fix shadow AI with Passport](https://www.theregister.com/devops/2026/06/19/vercel-debuts-eve-open-source-agent-framework-tries-to-fix-shadow-ai-with-passport/5258726)
10. [Vercel launches eve, an open-source framework that treats agents as directories](https://thenewstack.io/vercel-launches-eve-an-open-source-framework-that-treats-agents-as-directories/)
11. [Vercel CEO Guillermo Rauch on the fight to split off models from agents](https://techcrunch.com/2026/07/06/vercel-ceo-guillermo-rauch-on-the-fight-to-split-off-models-from-agents/)
12. [Superintelligence at Work: How Vercel Built v in Slack | Ship 26 | San Francisco](https://vercel.com/ship/sf/session/superintelligence-at-work) (primary)
13. [Vercel for Enterprise Apps and Agents](https://vercel.com/blog/vercel-for-enterprise-apps-and-agents) (primary)
14. [Agent Native | They Built an AI God Agent for 1,000 Employees](https://rss.com/podcasts/a-new-vibe/)

Author: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Agents](https://newruntime.com/topics/agents.md): Explore the agents topic hub.
- collection: [Analysis](https://newruntime.com/analysis.json): Open the latest authorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)