MODULE 14 · LIVE ON VERCEL, AND STAYING LIVE

Deployment

One push. One deploy. Every tier.

The frontend goes to Vercel in every tier; from Tier 2 the backend deploys beside it. Environments stay separate — dev, preview, production — and rollback is a button you've already pressed once on purpose.

WHEN YOU NEED IT

Every tier. Deploy on day one, not launch day.

THE CHOICE, PER TIER

T0–1Vercel, connected to the GitHub repo
T2+ backend on Railway / Render / Cloud Run
T3+ health checks and a written rollback plan

SAY THIS TO YOUR AGENT

"Connect the repo to Vercel with preview deploys per PR. Production env vars set in the dashboard, never committed. Show me how to roll back, and we practice it once."

DONE WHEN

git push deploys automatically with previews per PR
Prod secrets exist only in the host's env settings
You have rolled back once, on purpose, calmly

13 Integrations