Deployment

Nexus AI Admin is a standard Next.js 16 app and deploys anywhere Next.js runs. Vercel is the simplest.

Deploy to Vercel (recommended)

Push the project to a GitHub/GitLab/Bitbucket repo.
Go to vercel.com/new and import the repo.
Vercel auto-detects Next.js — no build config needed.
Add any environment variables (see below), then Deploy.

The default build/run commands are correct out of the box:

Setting	Value
Framework	Next.js
Build command	`next build`
Install command	`npm install`
Output	(auto)
Node version	20.x

Custom domain

In the Vercel project → Settings → Domains, add your domain and follow the DNS instructions (an A record or CNAME). HTTPS is provisioned automatically.

Environment variables

The demo needs none to run. When you add a backend, set the variables from .env.example in your host's dashboard:

NEXT_PUBLIC_APP_URL — your production URL (used for SEO/OG metadata).
Supabase / NextAuth / AI provider / Stripe keys as you enable each feature.

Variables prefixed NEXT_PUBLIC_ are exposed to the browser. Keep secrets (service-role keys, API keys, Stripe secret) without that prefix so they stay server-only.

Other hosts

Because it's a normal Next.js app, you can also deploy to:

Netlify — via the Next.js runtime adapter.
Cloudflare Pages — with @cloudflare/next-on-pages.
A Node server / Docker — run npm run build then npm run start (defaults to port 3000; set PORT to change).
Static export — not recommended here, since some pages use dynamic rendering features.

Pre-deploy checklist

npm run typecheck   # no type errors
npm run lint        # no lint errors/warnings
npm run build       # clean production build

All three pass on a fresh clone. Run them in CI before each deploy.

Performance notes

Charts are code-split behind client boundaries and render after mount.
Fonts are self-hosted via next/font (no layout shift, no external request).
Detail routes (/users/[id], /billing/invoice/[id]) are pre-rendered with generateStaticParams.

Next: FAQ →