Requirements
- Node.js 18+ installed locally
- Account on Vertra Cloud
Project Structure
Configuration
next.config.js
For deployment on Vertra Cloud, configurestandalone mode to optimize build size:
package.json
vertracloud.config
Available Versions
Deploy
- Dashboard
- CLI
- VS Code
- Compress the project into a
.zip(folders likenode_modules,venvandtargetare removed automatically) or push it to GitHub. - In the dashboard, click New Project and upload the
.zipor paste the repository URL. - In Build, check the runtime (JavaScript or TypeScript), and the memory. Under Advanced settings, confirm the build command
npm run buildand the start commandnpx next start -p 80; both are pre-filled for Next.js projects. - Add your environment variables in Environment.
- In Network, turn on web publishing so the app gets a
*.vertraweb.appaddress (512 MB of memory or more). The app must listen on port 80. - Review and deploy. Follow the output in the Logs tab.
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
Build fails due to lack of memory
Build fails due to lack of memory
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 exceeds the time limit
Build exceeds the time limit
build_command has a 10-minute ceiling (BUILD_TIMEOUT). Trim dependencies or split a very
large build.Page returns 404
Page returns 404
Check if
output: 'standalone' is configured and if the build completed successfully in logs.