Cloudways Node.js Deploy Review 2026: An Honest Verdict

This post contains affiliate links. If you purchase through our links, we may earn a commission at no extra cost to you.

If you’ve searched for how to run a Node.js app on Cloudways, you’ve probably landed on a tutorial that’s years old and skips the part where it doesn’t quite work out of the box. This Cloudways Node.js Deploy Review 2026 covers what’s actually true right now: Cloudways was built for PHP and WordPress, Node.js support today means a manual workaround, and a real native Node.js product just came out of nowhere — but you can’t sign up for it yet.

Cloudways and Node.js: The Real Picture in 2026

Cloudways is a PHP/WordPress platform first. There’s no general-availability, native Node.js runtime on the standard Cloudways platform — every existing tutorial you’ll find is describing the same workaround: spin up a “Custom App” (Cloudways’ own blog still sometimes calls it “a PHP application” container, even though setup-flow guides now label it “Custom Application”), SSH in, and run your Node process manually inside it.

The technical snag is that Cloudways servers only open ports 80 and 443 to the internet by default. Your Node app listens on its own port — usually 3000 — so nobody can reach it until you reroute traffic. The fix is enabling Apache’s mod_proxy module and adding a rewrite rule to .htaccess:

RewriteRule ^(.*)?$ http://127.0.0.1:3000/$1 [P,L]

That sounds simple enough, but Cloudways’ own blog and third-party guides both confirm mod_proxy is disabled by default on Cloudways servers — some users have had to open a support ticket just to get it turned on before the rewrite rule does anything.

Then there’s the process itself. SSH sessions close, and when they do, your Node app dies with them unless something keeps it alive. That “something” is PM2, installed manually via npm install pm2@latest -g. This matters more than it sounds: Cloudways’ built-in monitoring and uptime tooling is built around Apache and PHP-FPM, not PM2, so if your Node process crashes, Cloudways’ dashboard has zero visibility into it. PM2’s own restart policy is the only thing standing between a crash and downtime — and multiple commenters on The Cloud Keeper’s long-running Cloudways Node.js tutorial report exactly this failure mode: the app quietly stops the moment the terminal session closes, and nothing in Cloudways flags it.

How to Deploy Node.js on Cloudways Today (Custom App + PM2)

This is the workaround path — available right now, no waitlist required. It’s what you’ll actually use if you provision Cloudways for a Node app this week.

1. Create a server and Custom App. In the Cloudways dashboard, launch a new server (DigitalOcean-backed “Flexible” plans are the standard entry tier) and choose “Custom Application” rather than a WordPress or Laravel preset.
2. Deploy your code. Upload via SFTP, or SSH in and run git clone manually — there’s no first-class Git-push deploy flow on this legacy path, and no build pipeline or per-app Node version picker. Whatever Node version ships with the server image (or whatever you install yourself via nvm over SSH) is what you’re running.
3. Install and configure PM2. Run npm install pm2@latest -g, then start your app with pm2 start server.js (or your entry file) and set it to restart on reboot with pm2 startup and pm2 save.
4. Enable mod_proxy and edit .htaccess. If the module isn’t already active, contact Cloudways support to enable it, then add the rewrite rule that forwards port 80/443 traffic to your app’s local port.
5. Test, then keep watching PM2. Because Cloudways’ dashboard doesn’t monitor the Node process, pm2 logs and pm2 status are your only real-time visibility into whether the app is actually up.

If this manual proxy juggling sounds like more babysitting than you want, a plain VPS with a real Nginx reverse proxy from the start is often less fragile — our Vultr Node.js deploy guide walks through that setup end to end.

None of this is broken, exactly — it’s a real, working setup that plenty of small Node apps run on today. But it’s also self-managed in every way that matters: no zero-downtime deploys, no automatic restarts you didn’t configure yourself, and no dashboard that tells you when something’s wrong.

What’s Coming: Cloudways Managed Node.js Hosting

On June 16, 2026, Cloudways published “Cloudways Managed Node.js Hosting Is Here” — and unlike the workaround above, this is a genuinely native Node.js product, not a repurposed PHP container. It’s currently in Private Preview and invite-only. Cloudways says it’s “onboarding developers, agencies, AI builders, and founders in stages,” with signups going through a waitlist at cloudways.com rather than a self-serve checkout.

What the new product actually offers, per Cloudways’ own announcement:

• Git-based deploys by default — connect a GitHub repo, pick a branch, and Cloudways builds and deploys automatically, traceable to commits, no FTP or SSH required.
• Zero-downtime deployments, with traffic rerouted to the new version instead of a maintenance window.
• Per-app Node version selection — currently Node 22.x and 24.x LTS — chosen through the dashboard, not whatever the server image happens to ship with.
• Dashboard-based process management (start/stop/restart/monitor) and unified build/error logs, so you’re not relying on pm2 logs over SSH to know your app is alive.
• Optional local PostgreSQL provisioning, or bring your own external database, or skip a database entirely.
• The same managed security stack Cloudways runs for PHP — WAF, DDoS protection, Imunify360 malware protection, Cloudflare CDN, auto-managed SSL and OS patching — now extended to Node.
• Framework support listed on the landing page includes Astro, Angular, Fastify, Express, React, and “2M+ NPM packages.”

Pricing is free during Private Preview and the upcoming Public Preview; at general availability, Cloudways states pricing will start at $21/month with flat billing rather than usage-based surge pricing. Cloudways also discloses real limitations at this stage: infrastructure is DigitalOcean-only for now (no AWS, GCP, Vultr, or Linode support on this specific product yet), there’s no CI/CD pipeline, no multi-region deployment, and no public GA date has been announced.

If you’re evaluating Cloudways for a new Node.js project today, the honest read is: the new Managed Node.js product looks like the real answer to everything wrong with the Custom App workaround, but it isn’t something you can sign up and pay for yet. Most readers researching this in 2026 will still end up on the workaround path described above, at least for now.

Pricing: Cloudways vs Node-Native Platforms

The Custom App workaround runs on Cloudways’ standard DigitalOcean-backed “Flexible” plans — the same servers used for WordPress and PHP hosting, billed hourly.

Prices last checked: 2026-07-09.

Cloudways’ own pricing page lists the entry tier at $11/month, while several third-party review sites report $14/month as of their 2026 checks — treat it as an $11–14 range and confirm the live number before you buy. All tiers include a 3-day free trial with no credit card required, unlimited sites/visits, and backup storage billed separately at roughly $0.033/GB beyond what’s included.

Compare that to platforms built for Node.js from day one:

For a typical small SaaS stack (web server, database, Redis), a realistic Railway bill lands around $15–40/month at roughly $20 per vCPU-month and $10 per GB-month of RAM. Render for the same workload tends to run $25–60/month but with flat, predictable per-service pricing rather than usage-based billing — a real trade-off depending on whether your traffic is steady or bursty. DigitalOcean App Platform undercuts everyone on entry price at $5/month, with autoscaling gated behind a $29/month dedicated-CPU plan.

The pattern here is consistent: every Node-native competitor gives you Git-push deploys and zero manual proxy configuration for less than Cloudways’ entry general-purpose tier costs today — and all of them are self-serve, no waitlist. If you want to run these numbers against your own expected traffic before committing, our free VPS cost calculator is a quick way to sanity-check a monthly estimate before you provision anything.

If you’re already invested in Cloudways for other sites — say, a WordPress install and a client’s WooCommerce store — provisioning one more server for a Node app at $11–14/month to run under the Custom App workaround is a reasonable extension rather than a reason to add a second vendor. New signups get a 3-day free trial with no credit card required, plus 30% off the first three months.

Who Cloudways Node.js Hosting Is For (and Who Should Skip It)

It makes sense if: you’re already running WordPress or PHP apps on Cloudways and want to bolt on a small Node microservice — an API, a webhook receiver, a background worker — without paying for and managing a separate vendor. The security stack (WAF, DDoS protection, managed SSL, backups) is genuinely mature, and it’s the same infrastructure you’re already trusting for your main site.

It doesn’t make sense if: Node.js is your primary workload and you’re choosing a host from scratch. Railway, Render, and DigitalOcean App Platform all give you native Git-push deploys and zero-downtime releases today, for less money, without touching mod_proxy or babysitting a PM2 process that Cloudways’ own dashboard can’t see. Paying more for less tooling only makes sense if the Cloudways ecosystem lock-in (billing, other apps, team access) already outweighs the deploy friction.

If you’re waiting on the new Managed Node.js product, join the waitlist, but don’t plan a launch around it — there’s no GA date, and the current DigitalOcean-only, no-CI/CD limitations mean even invited users are working with a preview, not a finished product. For a closer look at where Cloudways stands overall outside the Node.js question, our broader Cloudways verdict and Cloudways vs Vultr comparison cover the general hosting trade-offs in more depth.

Mature for PHP, Fragile for Node.js

For WordPress and PHP, Cloudways is a mature, purpose-built product. For Node.js specifically, right now, it’s a workaround wearing a hosting platform’s clothes — functional, but fragile in exactly the places that matter: a single PM2 process Cloudways can’t see, a manually-enabled Apache proxy rule, and zero build pipeline.

If you’re already on Cloudways for other apps, the Custom App + PM2 path is worth using for a small, low-traffic Node service rather than adding a new vendor. You can start that 3-day free trial and get the workaround running in an afternoon. But if Node.js is your main workload and you’re picking infrastructure from a blank slate, Railway, Render, or DigitalOcean App Platform will get you Git-push deploys and zero-downtime releases today, for less money, with none of the manual proxy babysitting. Cloudways’ new Managed Node.js Hosting looks like it could close that gap entirely — but until it leaves invite-only preview, it’s a “watch this space,” not a reason to switch today.