Run a Node.js app on shared hosting

Shared hosting can run a lightweight Node.js application beside a normal website through the Hestia Node.js app installer. This is not a Docker host and not a reserved-CPU Node platform.

Supported versions and packages

• Versions: current Node LTS releases available in the Hestia installer on your server — commonly 18, 20 and 22. Open a ticket if you need to confirm the list on your account.
• Package managers: npm is the default. yarn or pnpm can be used if you install them in the app directory; they are not a separate managed service.

Process persistence, restarts and ports

• Hestia keeps the Node process running and restarts it after a crash or server reboot when the app is enabled in the panel.
• Your app must listen on the localhost port Hestia assigns. Do not bind to public 80/443 — the web server proxies HTTP to that port.
• Do not pick a random high port and expect it to be reachable from the internet.

WebSockets, cron and workers

• WebSockets work when the proxy upgrade headers are in place. If a socket connection fails, open a ticket with the app name and we check the proxy template.
• Use Hestia cron for scheduled jobs. Long-running workers share the same fair-use CPU, RAM and process limits as the website.

Memory and process limits

There is no reserved RAM or dedicated Node worker pool on shared plans. A memory leak or a busy API that starves neighbours may be throttled or asked to move to a VPS. See the Technical limits table on shared hosting.

Need Docker, custom systemd units, multiple public ports or guaranteed RAM? Order a VPS.