Next.js hosting

Next.js plans run your application in an isolated container with a managed reverse proxy. You push code, we build and serve it — with automatic SSL, environment variable management, and live logs.

What's included

Plans

Deploy your app

1. Create a Next.js site

   Panel → Websites → Create website → Node.js application. Assign your domain or use the preview URL.

2. Connect Git

   In the site settings → Git → Connect repository. Authenticate with GitHub, GitLab, or Gitea. Select the repository and branch.

3. Configure build

   Set your build commands (defaults work for most Next.js apps):

   Command	Default	Override if needed
   Install	npm install	pnpm install, yarn install
   Build	npm run build	pnpm build, custom script
   Start	npm start	node server.js, etc.

4. Set environment variables

   Panel → Environment variables → Add:

   • Variables are injected at both build time and runtime
   • Mark sensitive values as Secret (hidden from logs)
   • Changes trigger a clean rebuild

5. Deploy

   Push to your connected branch. The panel shows build logs in real time. Once the build succeeds and the health check passes, traffic routes to the new version.

Environment variables

Manage secrets without committing them to your repo:

• DATABASE_URL — database connection string
• NEXT_PUBLIC_* — client-side variables (exposed to browser)
• API_KEY, JWT_SECRET — server-only secrets
• NODE_ENV — automatically set to production

Variables are encrypted at rest. Changes trigger a rebuild unless you explicitly skip it.

Logs

Build logs

Streaming during deploy: Panel → your site → Deployments → click a deploy. Shows install, build, and start phases.

Runtime logs

Panel → your site → Logs. Shows stdout and stderr from your running application. Useful for debugging API errors, uncaught exceptions, and slow requests.

Zero-downtime deploys (Plus+)

On Plus tier and above:

1. New build starts in a separate container
2. Health check verifies the new version responds
3. Traffic seamlessly shifts to the new container
4. Old container is removed

Your users never see downtime during deploys.

Custom domains

1. Add your domain in Panel → your site → Domains
2. Point DNS (A record to server IP, or CNAME if using Cloudflare)
3. SSL certificate issues automatically

Multiple domains can point to the same app (e.g. app.yourdomain.com and yourdomain.com).

Databases

Next.js plans don't include a managed database, but you can:

• Connect external databases (Supabase, PlanetScale, Neon, your own Postgres)
• Install a database on a VPS plan and connect via DATABASE_URL
• Use Coolify on an App Platform plan for one-click Postgres/Redis

Static export mode

If your Next.js app uses output: "export" (static HTML):

• The build produces static files
• They're served directly from the CDN edge
• No Node.js process runs at runtime
• Fastest possible serving, lowest cost

Troubleshooting

Best practices

• Use output: 'standalone' in next.config.js for smaller deployment artifacts
• Set NEXT_TELEMETRY_DISABLED=1 to skip telemetry
• Cache API responses at the route level with Next.js cache headers
• Keep node_modules out of git (we install from lockfile)
• Use ISR (Incremental Static Regeneration) for pages that change occasionally

Related docs

• Custom domain guide
• SSL certificates
• VPS hosting — for apps needing root access
• Coolify — self-hosted PaaS alternative