{"id":21141,"date":"2026-10-21T03:13:28","date_gmt":"2026-10-21T03:13:28","guid":{"rendered":"https:\/\/www.hostinger.com\/support\/?p=21141"},"modified":"2026-10-21T03:47:18","modified_gmt":"2026-10-21T03:47:18","slug":"hostinger-node-js-limits-for-web-and-cloud-plans","status":"publish","type":"post","link":"https:\/\/www.hostinger.com\/support\/hostinger-node-js-limits-for-web-and-cloud-plans\/","title":{"rendered":"Hostinger Node.js limits for web and cloud plans"},"content":{"rendered":"

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.<\/p>

Node.js limits per hosting plan<\/h2>

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

\n\n\n\n\n\n\n\n\n
\n

Plan<\/b><\/p>\n<\/td>\n

\n

Node.js websites<\/b><\/p>\n<\/td>\n

\n

Process limit (NPROC)<\/b><\/p>\n<\/td>\n

\n

Entry processes<\/b><\/p>\n<\/td>\n<\/tr>\n

\n

Business\/Unlimited<\/p>\n<\/td>\n

\n

5<\/p>\n<\/td>\n

\n

120<\/p>\n<\/td>\n

\n

60<\/p>\n<\/td>\n<\/tr>\n

\n

Cloud Startup<\/p>\n<\/td>\n

\n

10<\/p>\n<\/td>\n

\n

200<\/p>\n<\/td>\n

\n

100<\/p>\n<\/td>\n<\/tr>\n

\n

Cloud Professional<\/p>\n<\/td>\n

\n

10<\/p>\n<\/td>\n

\n

400<\/p>\n<\/td>\n

\n

200<\/p>\n<\/td>\n<\/tr>\n

\n

Cloud Enterprise<\/p>\n<\/td>\n

\n

10<\/p>\n<\/td>\n

\n

600<\/p>\n<\/td>\n

\n

300<\/p>\n<\/td>\n<\/tr>\n

\n

Cloud Enterprise Plus<\/p>\n<\/td>\n

\n

10<\/p>\n<\/td>\n

\n

800<\/p>\n<\/td>\n

\n

400<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>

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

How the Node.js process limit works<\/h2>

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<\/code> and www.domain.tld<\/code> each run a separate process.<\/p>

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<\/a>. To see how close your plan is to the limit, see how to check resource usage in Hostinger<\/a>.<\/p>

Node.js request timeout<\/h2>

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

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.<\/p>

Features not supported on Node.js web and cloud hosting<\/h2>

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