Connect the repository.
Import it from GitHub or GitLab and choose the production branch.
Nuxt hosting
Deploy a Nuxt app from GitHub or GitLab. Lahyer runs nuxt build output as a Node.js server, or serves nuxt generate output as static files, with HTTPS, previews and logs.
Deploy your projectWhat Lahyer does with it
Lahyer fills these in from your repository. Change anything that does not fit in the project's build settings.
| Detected from | nuxt in your package.json dependencies |
|---|---|
| Install | npm, pnpm, Yarn or Bun, chosen from your packageManager field or lockfile |
| Build | Your build script, or nuxt build |
| Runs as | A Node.js server from .output/. When the build script runs nuxt generate, static files from .output/public/ |
| Node.js | 20 or 22, read from .nvmrc, .node-version or engines.node (22 by default) |
Your first deploy
Import it from GitHub or GitLab and choose the production branch.
Keep nuxt build for server rendering and server routes. Change the build script to nuxt generate for a prerendered site.
Every push deploys, pull requests get preview URLs, and runtime logs show what the server is doing.
A few useful answers
Yes, when you deploy with nuxt build. Routes in server/api run on the Nitro server Lahyer starts.
From your package.json build script. If it runs nuxt generate, Lahyer serves the prerendered files. Otherwise it runs the server.
Server apps on Free sleep when idle and start again on the next request, which can take a moment. Pro keeps one production app always on.
Yes. Add Postgres from the project's Database tab and Lahyer puts the connection string in DATABASE_URL for production and preview. Free includes one 1 GB database.