{
  "schema_version": "1.0",
  "id": "archive:https://vercel.com/blog/vercel-ship-2026-recap",
  "slug": "vercel-ship-2026-recap-1w51v4r",
  "url": "https://feed7.dev/p/vercel-ship-2026-recap-1w51v4r",
  "title": "Vercel Ship 2026 recap",
  "why_included": "Vercel Ship 2026 in one read: the Agent Stack primitives, Vercel Connect for scoped agent credentials, the open-source eve agent framework, Dockerfile support, and Vercel Agent hitting public beta.",
  "summary": "**The gist** Ship 2026 (London, Berlin, New York) laid out Vercel's agent strategy: the **Agent Stack** — AI SDK, AI Gateway, Workflow SDK, Sandbox, Chat SDK — plus **Vercel Connect** (temporary, scoped credentials for agents reaching external systems), **eve**, an open-source agent framework built from markdown instructions and TypeScript tools in one directory, and **Vercel Agent** in public beta, which investigates production anomalies and opens pull requests instead of alerts. Dockerfile support, a container registry, Vercel Services, Passport, and BYOC on AWS rounded out the announcements.",
  "practical_implication": "**Why it matters** If you deploy on Vercel, the primitives you'd otherwise assemble yourself — **durable workflows**, **sandboxed execution**, model routing with failover — are converging into one stack, and **eve** is worth reading as a reference architecture even if you never adopt it.",
  "agent_context": "**The gist** Ship 2026 (London, Berlin, New York) laid out Vercel's agent strategy: the **Agent Stack** — AI SDK, AI Gateway, Workflow SDK, Sandbox, Chat SDK — plus **Vercel Connect** (temporary, scoped credentials for agents reaching external systems), **eve**, an open-source agent framework built from markdown instructions and TypeScript tools in one directory, and **Vercel Agent** in public beta, which investigates production anomalies and opens pull requests instead of alerts. Dockerfile support, a container registry, Vercel Services, Passport, and BYOC on AWS rounded out the announcements.\n\n**Why it matters** If you deploy on Vercel, the primitives you'd otherwise assemble yourself — **durable workflows**, **sandboxed execution**, model routing with failover — are converging into one stack, and **eve** is worth reading as a reference architecture even if you never adopt it.\n\n**Watch out** It's a **recap post** — vision-heavy, with self-reported case-study numbers. Maturity varies: much of the stack is GA, but **Vercel Agent** and Passport are public beta while Security Dashboard and BYOC are private beta.",
  "source": {
    "name": "Vercel",
    "url": "https://vercel.com/blog/vercel-ship-2026-recap",
    "published_at": null
  },
  "source_class": "blog_post",
  "content_type": "Engineering Post",
  "layer": null,
  "domains": [],
  "topics": [],
  "verification": {
    "status": "official_source",
    "label": "Official Source",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [
    "It's a **recap post** — vision-heavy, with self-reported case-study numbers. Maturity varies: much of the stack is GA, but **Vercel Agent** and Passport are public beta while Security Dashboard and BYOC are private beta."
  ],
  "lifecycle": "Current",
  "published_at": null,
  "modified_at": null,
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/vercel-ship-2026-recap-1w51v4r",
    "json": "https://feed7.dev/p/vercel-ship-2026-recap-1w51v4r.json",
    "markdown": "https://feed7.dev/p/vercel-ship-2026-recap-1w51v4r.md"
  }
}