Can You Use Node.js on Shared Hosting?

Key highlights

Learn whether shared hosting can run your Node.js app and what the answer depends on.
Understand how a persistent Node.js process differs from traditional per-request hosting.
Know the runtime, package and routing support your host needs before Node.js will work.
Compare shared hosting against a virtual private server (VPS) or Virtual Dedicated Server Hosting (VDS).
Discover the concrete signals that tell you it is time to move up.

Can you use Node.js on shared hosting? The honest answer is that it depends on your provider and the server environment they give you.

Some shared hosts support Node.js through control-panel tooling, but Node.js support is not standard across shared hosting plans. For production workloads that need persistent processes, greater control or more resource flexibility, a VPS is usually the more dependable choice.

Node.js is a popular runtime, so this question comes up often. In the 2025 Stack Overflow Developer Survey, it was the most used web technology among respondents, at 48.7%.

This guide explains whether you can use Node.js on shared hosting, why support varies between hosts, what your host has to provide and which apps are realistic. We also cover the limitations and compare shared hosting with VPS and VDS to help you choose the right environment.

Can you use Node.js on shared hosting?

Yes, but only if your hosting provider has enabled it. Node.js is not a default feature on many shared plans, so the same app can run on one host and fail on another. Whether it works comes down to a few specific conditions.

You can run Node.js on shared hosting when:

Your host offers a cPanel or DirectAdmin “Setup Node.js App” tool backed by the CloudLinux Node.js Selector.
Your app is small and tolerant of shared resource limits.
You only need standard web requests over Hypertext Transfer Protocol (HTTP), not custom ports or long-lived connections.

Shared hosting may not be suitable for your Node.js app when:

Your host locks the environment to PHP (Hypertext Preprocessor) and static files with no Node runtime available.
Your app needs root access, custom system packages or its own process manager.
Your application depends heavily on WebSockets, background workers, persistent processes or sustained traffic that the shared environment restricts.

There are three practical paths for hosting a Node.js app. The first is a cPanel Node app on a shared plan that supports it. The second is a VPS or VDS, where you control the whole environment.

The third is a platform-as-a-service (PaaS) provider that runs the Node process for you. Which one fits depends on how much control and headroom your app needs.

How does Node.js work on shared hosting?

A Node.js application normally runs as an application process that can handle multiple requests through its event loop. On shared hosting, the provider needs a way to start, route traffic to and manage that process.

Node.js application process: The runtime handles incoming requests through a running application process rather than requiring a new Node runtime for every request.
Web server or application manager: Apache or Nginx commonly receives public traffic and routes it to the application.
Passenger or an equivalent runtime: Some cPanel environments use Phusion Passenger for Node.js to start, supervise and scale application processes.
Resource restrictions: Shared plans can limit CPU, memory and concurrent processes to prevent one account from consuming excessive server resources.

With Passenger, application processes can be started or stopped according to traffic and server configuration. This differs from having unrestricted control over a continuously running process on a self-managed VPS.

What does shared hosting need to support Node.js?

Node.js support is not a single switch. A host has to provide several pieces together, and any missing piece can stop your app from starting.

On many cPanel-based shared hosting environments, Node.js support is provided through tools such as CloudLinux’s Node.js Selector. Other providers may use different application-management systems. That is why availability differs from one provider to the next.

Supported Node.js runtime: The server must have Node.js installed and exposed to your account, not just present on the machine.
Node Package Manager (npm): You need npm access to install the dependencies in your package.json.
Application process management: Something has to keep your app running and restart it after a crash, usually Passenger on a shared plan.
Environment variables: You need a way to set values such as PORT, NODE_ENV and API keys without hardcoding them.
Domain or application routing: The control panel must map a domain or subpath to your running app so traffic reaches it.
Supported Node.js versions: The host should offer a current version your framework requires, since older environments lag behind.

These capabilities depend on the individual hosting provider and plan. Before deploying, confirm that your host exposes the Node.js runtime, package management and application-routing features your project requires.

What can you run with Node.js on shared hosting?

A supported shared plan suits lightweight workloads rather than demanding production systems. The resource limits keep heavy apps out, but plenty of smaller projects run well. These use cases are generally realistic on a supported shared environment.

Small Express apps: Basic sites or dashboards built on Express with modest traffic.
Simple, low-traffic APIs: Internal or personal APIs that serve occasional requests.
Lightweight web apps: Server-rendered tools and utilities with a small user base.
Dev and test projects: Prototypes, demos and learning projects where uptime is not critical.
A companion service: A small Node service running beside a main PHP or WordPress site.

One common source of confusion is the front-end framework build. A static build of React, Vue or Angular does not need server-side Node at all. You run npm run build locally, then upload the generated static files like any other HTML, CSS and JavaScript.

You only need a running Node.js process when your app renders on the server or exposes an API. Exact capabilities still vary by provider, so confirm what your plan allows.

What are the limitations of Node.js on shared hosting?

Even when Node.js runs, a shared plan sets boundaries that affect a growing app. These limits come from sharing one machine across many accounts, so they protect every tenant. Weigh them before you decide whether you can use Node.js on shared hosting for production.

Shared CPU and RAM caps: Tight caps on processor, random access memory (RAM) and concurrent processes can crash apps under load.
Limited runtime configuration: You often cannot change kernel settings, global Node flags or system tuning.
Restricted background processes: Long-running jobs, workers and schedulers are frequently limited or disallowed.
Blocked custom ports: Public custom ports are usually closed, so your app works through the host’s routing.
Unreliable WebSockets: Real-time connections may be restricted or drop under shared limits.
Native module build failures: Packages that compile native code can fail without the right build tools.
No custom process managers: Passenger usually manages the lifecycle, so you cannot run Process Manager 2 (PM2) yourself.
Server-level dependencies: Software that needs root to install is generally off-limits on a shared account.
Resource scaling is limited: Shared hosting generally does not let you independently increase CPU, RAM or other server resources for a single application.

If you are weighing these trade-offs against more control, our comparison of web hosting vs VPS hosting shows where each option fits. It is a good next read before you commit.

Node.js shared hosting vs VPS: Which should you choose?

The clearest way to choose is to compare each option against the requirements of your Node.js application. The criteria below focus on control, resources and the features that most often decide whether an app runs well.

Requirement	Shared hosting	Self-Managed VPS or VDS
Small Node.js app	Sometimes (if the host enables it)	Yes
Root and server control	Limited or none	Yes
Custom packages and native modules	Limited	Yes
PM2 and background processes	Often restricted	Yes
Custom ports	Restricted	Yes
WebSockets and real-time	Often restricted	Yes
Scaling resources	Limited	Greater control
Multiple production services	Not ideal	Better suited

Shared hosting can be enough for a small, tolerant app, though it leaves you dependent on your provider’s limits. A self-managed VPS can give you full server control and allocated resources, while a VDS goes further by providing dedicated compute resources locked at the hypervisor level. Our overview of how VPS hosting works explains what that added control includes.

Can you use Node.js with Bluehost hosting?

You can run Node.js on our Self-Managed VPS and VDS hosting, where you get the server-level control needed to configure the runtime, processes and supporting software.

Our Web Hosting runs in a managed shared environment, so it is better suited to workloads that do not require custom Node.js server configuration.

Run Node.js on a Bluehost Self-Managed VPS

Our Self-Managed VPS hosting gives you full root and SSH access, so you can configure the Node.js runtime, frameworks and server software your application requires.

You can use tools such as PM2 for process management and run Nginx or OpenLiteSpeed as your web server. We also offer an OpenLiteSpeed + Node.js application option to give you a faster starting point.

Our Self-Managed VPS plans use NVMe SSD storage and AMD EPYC hardware, with unmetered bandwidth and a 99.99% uptime SLA. Plans range from 1 vCPU and 2 GB RAM to 8 vCPU and 16 GB RAM.

Our guide to set up a Node.js VPS walks you through the process step by step.

Step up to Bluehost Virtual Dedicated Server Hosting (VDS) for heavier Node workloads

For sustained production load, our Virtual Dedicated Server Hosting (VDS) gives you dedicated vCPU and memory resources reserved for your environment at the hypervisor level, with no overcommitting. You keep full root access, plus one-click runtimes and click-to-buy scaling across tiers.

Our VDS is better suited to workloads that need dedicated, isolated compute, such as SaaS backends, APIs with sustained traffic, CI/CD pipelines and setups running several services at once.

When should you move from shared hosting to a VPS for Node.js?

A few concrete signals tell you when a shared plan may no longer be enough for a Node.js app. If several of these apply, a VPS is likely the better fit.

Persistent processes need to stay running between requests.
PM2 or another process manager is required.
Custom libraries or system packages need root access.
The application relies on WebSockets or other real-time services.
APIs handle sustained traffic rather than occasional requests.
CI/CD workloads build and deploy directly on the server.
Multiple Node.js services need to run side by side.
More allocated CPU, RAM or server-level control is required.
Dedicated, isolated compute is required for more demanding workloads, making VDS worth considering.

Final thoughts

So, can you use Node.js on shared hosting? Yes, but only when your provider has enabled it, and even then it fits low-traffic, tolerant workloads. Once your application needs persistent processes, more server control or greater resource flexibility, moving to a VPS or VDS becomes the more practical option.

With our Self-Managed VPS, you get the control to configure your Node.js environment. For workloads that need dedicated compute, our VDS provides greater resource isolation.

Compare Bluehost Hosting plans and choose the setup that best matches your application requirements.

FAQs

Can Node.js run on shared hosting?

Yes, but only when your host has enabled Node.js support, usually through a cPanel “Setup Node.js App” tool. Many shared plans do not offer it, and those that do apply resource and process limits. Confirm Node.js availability with your provider before you plan a deployment on a shared plan.

Can you install Node.js on cPanel shared hosting?

Sometimes. If your host has enabled the CloudLinux Node.js Selector, cPanel shows a “Setup Node.js App” tool that installs dependencies and starts your app. Without that feature enabled, you cannot install a running Node.js app yourself. It depends on server-level access you do not have on a shared account.

Does Bluehost support Node.js?

Yes. Bluehost Self-Managed VPS gives you full root and SSH access so you can install and configure Node.js, frameworks and process-management tools for your application. Bluehost also offers an OpenLiteSpeed + Node.js deployment option on Self-Managed VPS. For workloads that require dedicated isolated compute, Bluehost VDS provides full root-level control so you can configure the Node.js environment yourself.

Does Bluehost shared hosting support Node.js?

Bluehost Shared Web Hosting runs in a managed shared environment and is not positioned for applications that require control over a persistent Node.js runtime or server-level process management. For those workloads, we recommend a Self-Managed VPS or VDS, where you can directly configure the runtime, processes and web server.

Do you need VPS hosting for Node.js?

Not always, but usually for anything beyond a small app. A supported shared plan can run a low-traffic Express app or a simple API. Once you need persistent processes, PM2, custom ports, WebSockets or greater control over allocated server resources, a VPS gives you substantially more flexibility than shared hosting. If you specifically need dedicated compute resources with zero overcommitting, consider VDS.

Can you run Express.js on shared hosting?

Yes, if your host supports Node.js. Express apps are among the most common workloads that run on a supported shared plan, especially smaller sites and low-traffic APIs. Expect resource caps and limited background processing, so heavier Express projects with sustained traffic are better suited to a VPS you control.

Can Next.js run on shared hosting?

It depends on how you build it. A statically exported Next.js site can be uploaded as static files without a running Node process. A Next.js app that uses server-side rendering or API routes needs a persistent Node.js server. A shared plan can support this only when the provider explicitly provides the required Node.js runtime and process support, so a VPS is generally the more flexible option for these workloads.

Is shared hosting suitable for a production Node.js app?

Shared hosting is usually not the best fit for production Node.js applications that need predictable resources, persistent processes or server-level control. Shared plans apply processor, memory and process limits, and may restrict features such as WebSockets, custom ports and background jobs. For applications that require greater control and predictable resources, a VPS or VDS with root access is the more dependable choice.