Hostinger Node.js limits for web and cloud plans

Node.js limits at Hostinger depend on your web or cloud hosting plan. Each Node.js website runs as one long-running Node.js process, and all websites on the plan share the same process limit and memory. Every plan stops a request after 120 seconds and doesn’t support inbound WebSockets or always-running background workers.

Node.js limits per hosting plan

The number of Node.js websites, the process limit (NPROC) and the entry process limit depend on your hosting plan:

For CPU, memory and other plan resources, see parameters and limits of hosting plans in Hostinger. To create a Node.js website on one of these plans, see how to add a Node.js web app in Hostinger. To compare Node.js on web, cloud, VPS and Agency hosting, see Node.js hosting options at Hostinger.

How the Node.js process limit works

The process limit (NPROC) counts every process and thread running on your hosting plan, not only Node.js apps. All websites on the plan share it. One Next.js app can use about 10–11 threads, and domain.tld and www.domain.tld each run a separate process.

When the plan reaches the process limit, Node.js websites can return a 503 error. To fix it, see how to fix 503 and too many processes errors on Node.js websites at Hostinger. To see how close your plan is to the limit, see how to check resource usage in Hostinger.

Node.js request timeout

A single request to a Node.js website at Hostinger is stopped after 120 seconds. Move longer tasks to a cron job for your Node.js website instead of handling them inside a request.

Builds run with separate, higher resource limits than the running app. Very long builds can still fail, so keep build steps as short as possible.

Features not supported on Node.js web and cloud hosting

Hostinger Node.js runs each app as one standard Node.js server, so some features of other platforms aren’t available:

• Inbound WebSockets: apps can open outgoing WebSocket connections but can’t accept incoming ones, for example from a Socket.IO server. See are sockets supported at Hostinger.
• Always-running background workers: queue workers, bots and endless timers stop when the app is deployed or restarted. Use cron jobs for Node.js websites instead.
• Custom ports and extra services: apps can’t listen on their own ports or run Docker, Redis or Python services.
• Bun: only Node.js with npm, yarn or pnpm is supported. See how to deploy monorepos with npm, yarn or pnpm on Hostinger.
• Serverless platform features: features such as Vercel Edge Functions, Vercel KV or AWS Lambda don’t exist on Hostinger. See how to migrate from Vercel to Hostinger.

For apps that need these features, use a Hostinger VPS, where you control the server and its ports. See how to set up a Node.js application on a Hostinger VPS with CloudPanel.

Knowing these limits helps you choose the right hosting plan and keep your Node.js app within its resources. If your plan reaches a limit, see what to do if your hosting plan limits are reached in Hostinger.