Every project ships on Vercel
frankx.ai, the production site frankx.ai-vercel-website, Watch OS, Workshop OS, Library OS, Studio, ACO, Partnerships — 8+ public production deploys on Vercel under the frankxai org.
frankx.aiPartnerships
Vercel
Strategic alignmentFrankX
AI Architect — Next-on-Vercel AI CoE practice
The deployment substrate the entire AI CoE practice runs on.
Every shipped FrankX surface already runs on Vercel infrastructure. The Build First AI Agent workshop centres Vercel AI SDK. The conversation is making the alignment formal.
A deeper conversation is open with Vercel. The proposal page comes online when both sides are ready to publish.
Context
The market this conversation sits inside.
Vercel is the deployment substrate the entire FrankX AI Architect practice runs on. frankx.ai, the production site frankx.ai-vercel-website, Watch OS, Workshop OS, Library OS, Studio, ACO, Partnerships — every public surface ships on Vercel. The AI Architect Academy uses Next.js 16 with Turbopack, Cache Components, Fluid Compute, and the new vercel.ts config as its standard reference deploy.
The alignment I see is around the production agent stack — AI SDK at the centre, Fluid Compute carrying the long-running calls, AI Gateway in front of the model layer. The Build First AI Agent workshop already teaches the Vercel AI SDK as the central path. The ai-architecture and ai-coe pages on frankx.ai are Next-on-Vercel reference architectures.
Vercel Partner Program — application is in flight. This page is the conversation about the shape of a strategic-alignment relationship.
Working reality
What I already build with this kind of partner.
Verifiable today. The proposal section below builds from here, not in place of it.
Vercel AI SDK in workshop curriculum
The Build First AI Agent workshop teaches Vercel AI SDK as the central path. Curriculum branch is explicitly Vercel-anchored — workshop attendees ship their first production agent on the AI SDK + Next.js stack.
/workshops/build-first-ai-agentVercel Partner Program — in flight
Application submitted. This page is the conversation about the shape of the alignment once the program pathway completes.
Next.js 16 + Cache Components + Fluid Compute in delivery
Production stack on every frankx.ai surface — Next.js 16, Turbopack, Cache Components, Fluid Compute, the new vercel.ts config. Reference deploys, not slideware.
AI Gateway adoption
AI Gateway aware across the workshop curriculum and the ai-architecture reference pages. The production agent stack is AI SDK + Fluid Compute + AI Gateway, taught and shipped together.
Evidence
Linked artifacts.
frankx.ai — Next-on-Vercel reference deploy
Build First AI Agent — Vercel AI SDK workshop branch
ACOS — agentic creator OS, ships on Vercel
SIS — Starlight Intelligence System, Next-on-Vercel substrate
ai-architecture — Next-on-Vercel reference architectures
ai-coe — the AI CoE blueprint in public, deployed on Vercel
Conversation open
A deeper conversation with Vercel is in motion.
The proposal page comes online when both sides are ready to publish. Until then, the working partnerships hub explains how I collaborate at this depth.
If you're reading this and the conversation is yours to open on the Vercel side, the calendar link is below.
Last updated