Overview
UnderHost shared hosting is designed primarily for PHP applications (WordPress, Laravel, etc.) and static websites. We also provide limited Node.js capability through cPanel’s Setup Node.js App (Passenger-managed) for lightweight use cases.
This article explains what Node.js features are available on shared hosting, key limitations, and when a VPS/Dedicated Server is required.
Applies To
- Shared Hosting plans with cPanel
- cPanel feature: Setup Node.js App (Passenger)
What Shared Hosting Supports
Fully Supported (Recommended Use Cases)
- PHP applications (WordPress, Laravel, custom PHP scripts)
- Static websites (HTML / CSS / JavaScript — no server-side runtime)
- Softaculous installers (for supported PHP applications)
- Manual uploads via cPanel File Manager or FTP
Limited Node.js Support (Shared Hosting)
Shared hosting can run basic Node.js web applications using:
- cPanel → Setup Node.js App
- Passenger-managed application runtime
- Request-based applications intended for simple usage
This is best suited for:
- Small demo or low-traffic applications
- Simple Node.js apps (e.g., basic Express apps) without complex build steps
- Projects that can run without SSH and without background workers
What Shared Hosting Does NOT Support (Important)
Shared hosting does not provide the environment needed for many modern Node.js deployments.
Not Available on Shared Hosting
- SSH / Terminal access (including Jailed Shell)
- Running install/build/start commands such as:
npm installnpm run buildnpm start
- Long-running background processes (workers, queues, schedulers, daemons)
- WebSockets / persistent connections (not guaranteed and commonly restricted in shared environments)
- Heavy frameworks that typically require build pipelines (often incompatible), such as:
- Next.js (commonly requires build steps)
- Nuxt (commonly requires build steps)
- NestJS (commonly requires build steps)
- Native module compilation or tooling that requires system build dependencies
Why These Limitations Exist
Shared hosting is a multi-tenant environment. Allowing terminal access and persistent Node.js processes increases:
- Security risk to other accounts on the same server
- Resource contention (CPU/RAM) and platform instability
- Abuse vectors (miners, scanners, unauthorized long-running processes)
Quick Compatibility Checklist
A Node.js script is not suitable for shared hosting if it requires any of the following:
- Vendor instructions that say “Open SSH/Terminal and run npm commands”
- Running
npm install,npm run build, ornpm start - Background workers or long-running tasks
- WebSockets or real-time services
If any of the above apply, you should use a VPS or Dedicated Server.
Recommended Solution for Full Node.js Support
For Node.js applications that require SSH, build steps, or persistent processes, we recommend:
- VPS Hosting (most common)
- Dedicated Server (higher performance / isolation)
With VPS/Dedicated, you get:
- Full SSH access
- Full npm tooling support
- Ability to run services reliably (systemd / pm2 / Docker)
- Greater performance and isolation
If You Purchased a “Website Script” That Requires Node.js
Many marketplaces provide scripts with installation instructions like:
- Upload ZIP
- SSH into server
- Run
npm install - Run
npm run build - Run
npm start
If your script includes those steps, it is not compatible with shared hosting.
In these cases, you can:
- Upgrade to a VPS/Dedicated (recommended)
- Ask the vendor for a PHP version (if available)
- Request a refund/exchange from the marketplace
Need Help Choosing the Right Option?
If you open a support ticket, please include:
- Script name or marketplace link
- Installation requirements provided by the vendor
- Expected traffic/usage (low / medium / high)
- Whether you need WebSockets, workers, or background tasks
Our team can recommend the correct hosting option and assist with migration or setup.
