Skip to main content
Servbase supports Next.js with mode-aware deployment behavior.

​
Supported modes

Current Next.js rendering modes in the dashboard:
  • ssr
  • csr
  • ssg

​
How mode affects deployment

​
SSR

SSR runs as a managed runtime application. Current behavior:
  • runtime-style deployment
  • rebuild support
  • restart support when the runtime is healthy

​
CSR and SSG

CSR and SSG behave as static-output deployment flows. Current behavior:
  • build output is expected in dist
  • the platform deploys the generated static output rather than a long-running SSR runtime

​
Build behavior

For Next.js apps, the platform currently normalizes key configuration depending on the selected mode. At a high level:
  • SSR keeps a runtime path
  • CSR and SSG use static-output behavior with dist as the expected output directory

​
During app creation

The current dashboard flow asks for:
  • app type: Next.js
  • rendering mode: ssr, csr, or ssg
  • base domain
  • source code input

​
Checklist

  • Confirm the selected mode matches how your project is meant to run
  • Confirm the repository branch is correct when deploying from GitHub
  • Confirm required environment variables are set
  • For CSR and SSG, confirm the build produces the expected static output

​
Rebuild source behavior

If the app is not connected to GitHub, rebuild normally uses the current workspace contents. If the app is connected to GitHub, rebuild can be run from either:
  • GitHub — re-clone and rebuild from the repository source
  • Workspace — rebuild from the files currently present in the Servbase workspace