Host on Vercel

Vercel is the fastest way to deploy your LandingKit project. It provides automatic builds, preview deployments for every git push, and a global edge network.

One‑click deploy (recommended)

Push to a repo: Commit your project to GitHub, GitLab, or Bitbucket.
Import on Vercel: Visit vercel.com/new and import your repository.
Framework preset: Vercel auto-detects Next.js. Keep defaults unless you customized.
Environment vars: Add any needed variables (if you added APIs or analytics).
Deploy: Click Deploy. Your site will be live on a Vercel domain instantly.

Local deploy with CLI

Use this if you prefer the CLI or don’t use a git provider.

# Install the CLI (once)
pnpm add -g vercel

# From the project root
vercel

# For production
vercel --prod

Build settings

Framework: Next.js (auto)
Build command: next build (default)
Install command: pnpm install (or npm/yarn as you use)
Output: .vercel/output (handled by Vercel)
Node version: Managed by Vercel unless you pin it in engines

Custom domain

Open your project in Vercel → Settings → Domains.
Add your domain and follow the DNS instructions (CNAME or A records).
HTTPS is automatic via Let’s Encrypt.

Environment variables

If you added features that require secrets (e.g. analytics keys), set them in Vercel → Settings → Environment Variables. Re‑deploy to apply changes.

Previews and production

Preview: Every PR receives its own preview URL.
Production: Merge to your default branch (e.g. main) to auto‑deploy.
Rollbacks: Re‑deploy any previous build from the Vercel dashboard.

Troubleshooting

Build fails: Ensure a lockfile exists and that your Node version is compatible with Next.js.
Missing images: Verify the paths under /public match your config.ts.
404 on anchors: Confirm nav hrefs match section ids (e.g. #pricing).

Tip: Use Vercel Analytics or a provider of your choice by adding the script and keys, then configure environment variables in Vercel for each environment.

One‑click deploy (recommended)

Push to a repo: Commit your project to GitHub, GitLab, or Bitbucket.

Import on Vercel: Visit vercel.com/new and import your repository.

Framework preset: Vercel auto-detects Next.js. Keep defaults unless you customized.

Environment vars: Add any needed variables (if you added APIs or analytics).

Deploy: Click Deploy. Your site will be live on a Vercel domain instantly.

Troubleshooting

Build fails: Ensure a lockfile exists and that your Node version is compatible with Next.js.

Missing images: Verify the paths under /public match your config.ts.

404 on anchors: Confirm nav hrefs match section ids (e.g. #pricing).

Tip: Use Vercel Analytics or a provider of your choice by adding the script and keys, then configure environment variables in Vercel for each environment.