Next.js

VibeHost runs Next.js without any framework-specific config from you. next build locally, vibehost deploy, done. The CLI inspects .next/ and picks one of three runtime paths.

Deploy

npm run build                                  # or `next build`
vibehost app create my-app --runtime nextjs --json
vibehost link --app my-app
vibehost deploy --json

That's the whole thing. No output: 'standalone', no open-next.config.ts, no extra installs.

The three runtimes

The CLI picks one automatically by inspecting .next/ and your next.config:

Response fields worth watching

{
  "ok": true,
  "data": {
    "url": "https://my-app.vibehost.space",
    "immutableUrl": "https://<deploy-id>.vibehost.space",
    "deployKind": "nextjs-opennext",
    "warnings": []
  }
}

• url — alias URL. Moves with rollbacks and promotes.
• immutableUrl — permanent per-deploy URL. Link to this for a specific version.
• deployKind — which runtime path got picked.
• warnings[] — non-fatal advice, e.g. "served via static fast-path because your build has no server code".

When you might want explicit control

Optional — only touch if you need them:

Environment variables

Server-side env vars (read at runtime, not bake-time):

vibehost env set DATABASE_URL=... --app my-app
vibehost env set NEXTAUTH_SECRET=... --app my-app
vibehost env list --app my-app

NEXT_PUBLIC_* variables are baked at build time and need to be set in your build environment, not via vibehost env set.

Logs

vibehost logs --app my-app

Streams Next.js ready messages, your console.logs, API route output, ISR revalidation events.

Known limits

• Next.js runtime is env-gated and AND-composed. Allowlist + master switch + per-user PostHog flag (Hard Rule #12). If app create --runtime nextjs returns NEXTJS_RUNTIME_DISABLED, the workspace isn't on the allowlist yet — contact us.
• Recovery while disabled is not the rollback API — rollback relaunches the runtime, which is what the gate exists for. See the OOM recovery runbook.

Migration from Vercel / Netlify

If you're moving an existing Next.js app:

1. Local next build succeeds → you're 90% done. VibeHost's CLI uses the same build.
2. Move env vars: vibehost env set for each VERCEL_* / NEXT_PUBLIC_* you have on the old platform.
3. Custom domain: vibehost domain add www.example.com --app my-app, then update DNS.

No framework code changes needed.