Deploy your first app and verify the live result

Outcome and prerequisites

Prepare a deployable version of the task app and verify its live create -> refresh journey. You need a working app, a host account, a selected development/preview database, and its server-side connection settings. This guide describes deployment; following its preflight does not itself publish anything.

Use Deploy an app and the deployment worksheet to record commands, variable names, storage, and the exact revision. Environment name checker checks names without printing values; it does not validate credentials.

1. Identify what actually runs

Record the package manager and runtime pins, install/build/start commands, app directory, shared packages, and persistent services. Our workspace example has apps/web importing packages/task-core, with one lockfile at the root. A folder used as the app entry point is not necessarily the complete build context.

Run the project's typecheck, lint, tests, and production build locally. For the educational workspace, use its README's root commands. The actual VibeField site uses Next.js 16.4.3, React 19.2.9, Node 22, and pnpm 9.15.0 at this review; these are reference versions, not instructions to silently upgrade your app.

2. Check cost and limits before choosing a route

Checked 2026-11-13: Vercel Hobby is a free tier with usage limits; exceeding a limit can pause a feature. Review current eligibility and terms for your intended use, and account separately for database, email, models, and domains. The Fair Use Guidelines include plan-use conditions.