Ship a Next.js app in three minutes

Open the Next.js wizard

In the dashboard sidebar, click Development → tab "Development" → card "Next.js Application" → button "Deploy". The card shows the Next.js logo and a short description. Clicking Deploy opens the four-step wizard with a node selector pinned to the top right.

Step 1 — Server Configuration

Pick a Deployment Type (Virtual Machine, Kubernetes, or Docker Host). Enter the Server IP of your target VM, the SSH Username (typically ubuntu), and pick an SSH Key Pair Name from the dropdown — it lists every keypair stored in your workspace Vault.

• ▸Use Test SSH Connection (green button) to verify reachability before continuing.
• ▸The Services Checking button (yellow) runs runtime smoke-tests on the VM if you want a deeper preflight.

Step 2 — Application Source

Choose "From Repository" (default) or "Upload Zip". For Git: paste the repo URL, set a branch (defaults to main), pick the Git provider (GitHub, GitLab, Bitbucket), and either OAuth-connect or paste a personal access token. The token is stored in your workspace Vault and reused on subsequent deploys — you only enter it once.

Step 3 — Next.js Configuration

Select Build Mode (production / development), Node.js Version (22, 20, 18, or 16), and an App Name. App Name is what you will see later in Monitoring as the resource identifier.

Step 4 — Application Settings

Set Entry Point (default ".") and Package File ("package.json"). Add Environment Variables — one KEY=value per line. Set Application Port (typically 3000), HTTP Port (80) and HTTPS Port (443) for the front-facing reverse proxy.

Click Deploy and watch progress

A live progress card appears: 10% session created → 38% repo cloned → 50% npm install → 70% next build → 90% systemd unit started → 100% reverse proxy live. Logs stream over WebSocket; the same view is reachable later under Monitoring → session ID.