Skip to content

Deploy guides for every framework

Enzonic Deploy recognises 26 frameworks and runtimes from your repository and builds them with the right commands. Each guide shows what Deploy detects, how it builds and runs the app, and how to connect a database.

How detection works

  • Deploy reads package.json, the lockfiles, requirements.txt, pyproject.toml, Pipfile, go.mod, .nvmrc and a few framework config files. It never runs your code to decide.
  • The first match wins, in this order: full-stack frameworks, api/ functions and Node.js servers, Vite, Hugo, Python, Go, a generic Node.js server, then plain static files.
  • Monorepos are scanned for apps in workspaces (npm, pnpm, Yarn, Lerna, Turborepo, Nx) or in folders up to three levels deep, and you pick the root directory.
  • Anything detected can be overridden in the project settings: framework, install command, build command and output directory.
  • Node.js 18, 20, 22 and 24 are available. Deploy reads engines.node in package.json, then .nvmrc or .node-version, and uses Node.js 22 when nothing pins a version.

Your framework, live in minutes

Connect a repository and Deploy fills in the build settings for you. Free plan, no card.

Start free