{"id":21133,"date":"2026-10-21T03:00:54","date_gmt":"2026-10-21T03:00:54","guid":{"rendered":"https:\/\/www.hostinger.com\/support\/?p=21133"},"modified":"2026-10-29T15:20:09","modified_gmt":"2026-10-29T15:20:09","slug":"how-to-deploy-prisma-apps-on-hostinger-node-js-hosting","status":"publish","type":"post","link":"https:\/\/www.hostinger.com\/support\/how-to-deploy-prisma-apps-on-hostinger-node-js-hosting\/","title":{"rendered":"How to deploy Prisma apps on Hostinger"},"content":{"rendered":"

Prisma apps deploy on Hostinger hosting like any other Node.js app, using the build command from your package.json<\/code> file. Most Prisma build failures have four causes: the Prisma CLI is only in devDependencies<\/code>, the Prisma version isn’t pinned, DATABASE_URL<\/code> is missing at build time, or the Prisma engine is missing. Fix these before deploying, and use the build log to find which step failed.<\/p>

Build commands for Node.js apps at Hostinger<\/h2>

Hostinger accepts any build command from the scripts<\/code> section of your package.json<\/code> file. There’s no list of allowed commands, and you set the build command in the build settings when you add a Node.js web app in Hostinger<\/a>. For example, npm run build<\/code>, pnpm build<\/code> and npx prisma generate && next build<\/code> all work.<\/p>

Hostinger installs dependencies with the package manager detected from your lock file. When a lock file exists, npm projects are installed with npm ci<\/code>.<\/p>

Prepare a Prisma app for Hostinger<\/h2>

Step 1 – Make the Prisma CLI available during the build<\/h3>

Move prisma<\/code> from devDependencies<\/code> to dependencies<\/code> in package.json<\/code> if the build log shows prisma: not found<\/code>. Alternatively, generate the Prisma client automatically after installation:<\/p>

\"scripts\": {\r\n  \"postinstall\": \"prisma generate\"\r\n}<\/code><\/pre>
Step 2 – Pin the Prisma version<\/h3>
Set exact versions for prisma<\/code> and @prisma\/client<\/code> in package.json<\/code>, for example \"prisma\": \"6.5.0\"<\/code> instead of \"prisma\": \"^6.5.0\"<\/code>. An unpinned version can install a newer major version with changed configuration or removed commands.<\/p>
Step 3 – Add DATABASE_URL for migrations<\/h3>
Add DATABASE_URL<\/code> as an environment variable if your build runs prisma migrate deploy<\/code> or prisma db push<\/code>, as described in how to add environment variables during Node.js application deployment<\/a>. These commands connect to the database during the build. Use 127.0.0.1<\/code> as the host for a Hostinger MySQL database:<\/p>
DATABASE_URL=mysql:\/\/u123456789_user:password@127.0.0.1:3306\/u123456789_database<\/code><\/pre>
To get these values, see how to find your MySQL database details in Hostinger<\/a>. For the full database setup, see connecting a Hostinger MySQL database to a Node.js application<\/a>.<\/p>
Step 4 – Add the Prisma engine for the server<\/h3>
Add binaryTargets<\/code> to the generator block in schema.prisma<\/code> if the app builds but fails at runtime because the Prisma engine is missing:<\/p>
generator client {\r\n  provider      = \"prisma-client-js\"\r\n  binaryTargets = [\"native\", \"rhel-openssl-1.1.x\"]\r\n}<\/code><\/pre>
Redeploy the Node.js application<\/a> after these changes.<\/p>
Find where a Prisma build fails<\/h2>
Open the build log and look at the last command before the error. That command shows which step failed:<\/p>