Guides
Quick Start
Never built an AI app? Start here and ship a live app before you write real code.
Never built an AI app? Start here. You'll have a live app before you write real code.
You only build the top bit
An AI app has layers: your application, an optional workflow or agent, a model-access layer, and the provider that runs the model. You mainly build the application and its behavior. Vercel hosts the app, AI Gateway authenticates and routes supported model requests, and the selected provider runs the model.
Here's the whole request flow — what happens when someone uses your app:
You build the app on the left. Gateway model IDs are easy to change, but models have different capabilities, settings, latency, and cost, so test a change before treating it as a drop-in replacement.
Before the hackathon (~1 hour)
- Create a Vercel account and a v0 account.
- For local development, get an AI Gateway API key — Vercel deployments can use OIDC automatically. See AI SDK guide.
- Build one tiny app in v0 and deploy it. That's the whole loop.
Your first hour
- Pick a scoped idea from What to build.
- Copy a small example or clone a matching starter — see starter templates.
- Deploy it and open the live URL in a private/incognito window to confirm it works.
Your first day
- Replace the template's content and logic with your idea.
- Add one thing that makes it useful: a tool call or a data source (AI SDK guide).
- Keep scope tight — aim to demo ~25% of the big idea, done well.
Make it visible to judges
Judges need your live URL and to see the code, so deploy your app and put it on GitHub as a public repo (or share your v0 project link). Both easy paths start on v0 — the same two ways as the How to build page:
- All on v0 + Vercel (no local setup) — build in v0, deploy for a live URL, then use the current Git controls to connect and push to the intended public repo.
- Start on v0, then refine locally — build in v0, connect the intended GitHub repo, pull it to your machine, and publish from Vercel when you're ready.
The exact Git labels can change, so confirm the full owner/repo name before syncing. The Deployment guide covers current account and repository restrictions.
Pushing to GitHub also backs up your work — do it early and keep pushing, so a closed tab or spent credits never costs you the project.
Keep secrets out of a public repo — never commit .env.local or keys. More in the Deployment guide.
The one rule
Deploy early and often. A live URL that does one thing beats a perfect app on your laptop.
It's 2 weeks, part-time: deploy something small in week 1, then improve it in week 2. Don't wait until it's "ready" to ship.