Skip to main content

Requirements

Project Structure

Configuration

next.config.js

For deployment on Vertra Cloud, configure standalone mode to optimize build size:

package.json

vertracloud.config

Next.js needs to be compiled before starting. Set build_command to npm run build (or the BUILD key above) instead of chaining it into the start command — it runs in its own isolated build environment (2× the application’s RAM and vCPU, 10-minute timeout) on every deploy, and a plain restart skips it when the last build already succeeded.

Available Versions

Deploy

  1. Compress the project into a .zip (folders like node_modules, venv and target are removed automatically) or push it to GitHub.
  2. In the dashboard, click New Project and upload the .zip or paste the repository URL.
  3. In Build, check the runtime (JavaScript or TypeScript), and the memory. Under Advanced settings, confirm the build command npm run build and the start command npx next start -p 80; both are pre-filled for Next.js projects.
  4. Add your environment variables in Environment.
  5. In Network, turn on web publishing so the app gets a *.vertraweb.app address (512 MB of memory or more). The app must listen on port 80.
  6. Review and deploy. Follow the output in the Logs tab.
The full walkthrough is in First deploy.

Notes

  • Recommended memory: 512MB or more (build process is intensive)
  • Environment variables: Configure via dashboard before first build
  • Use output: 'standalone' to reduce build size
  • API Routes from Next.js work normally on the platform
  • The application must listen on port 80

Common Issues

The build environment already gets 2× the application’s RAM automatically. If it still fails, raise the application’s own memory to at least 512MB — the build environment scales with it.
build_command has a 10-minute ceiling (BUILD_TIMEOUT). Trim dependencies or split a very large build.
Check if output: 'standalone' is configured and if the build completed successfully in logs.
Last modified on November 1, 2026