Node.js Hosting

Host Node.js applications with Wodby using a managed stack and a Kubernetes-based runtime. Wodby Cloud is Wodby’s hosted cluster option for teams that do not want to run the cluster in their own cloud account or on their own server.

Wodby Cloud gives you persistent Wodby-hosted clusters billed by resource usage. Managed Kubernetes stays available when you need scaling; self-hosted Kubernetes is the budget path on your own servers, starting with one server.

Managed Node.js stack

Run Node.js apps on a ready-to-use stack with supporting services and a cleaner deployment model.

No separate cluster to bring

Use Wodby Cloud when you want the Wodby workflow without running the cluster in your own cloud account or on your own server.

Alternative deployment models

Use managed Kubernetes or a self-hosted Kubernetes setup on your own servers when infrastructure ownership or budget becomes more important.

In production

How Wodby runs Node.js in production

A Node.js application on Wodby runs as one required app service launched through its start script. The database, Valkey, mail, and Gotenberg services are optional and join the environment when you select them.

Read the port Wodby sets

Wodby sets its own Node port variable and leaves the generic port variable unset. The application listens on all interfaces, on the value from Wodby's variable or the same number as a default.

Environment type sets the Node mode

Dev-type environments run with the Node environment set to development and all other types get production, so a staging environment also runs in production mode.

Mailpit is protected by default

The public domains of Mailpit sit behind basic auth out of the box, and the password is shown with the environment's endpoint auths. Mailpit stores each message and forwards none.

Telemetry through a Collector

An OpenTelemetry Collector is part of the stack and starts disabled. After you enable it and choose where it forwards data, the application is given the standard OpenTelemetry SDK variables that point at it.

Read the Node.js stack guide for setup steps, settings, and limits.

Moving an existing Node.js application?

Ask your coding agent to read the repository, match the application to maintained Wodby services, and list what has to change. Review the plan before anything is created or moved.

Managed hosting model

Wodby Cloud for managed Node.js hosting

If you do not want to use your own Kubernetes cluster or server, Wodby Cloud is the most direct way to host Node.js applications on Wodby. It lets you deploy to a persistent Wodby-hosted cluster billed according to the resources you actually use.

That makes Wodby Cloud a strong fit for teams that want consistent environments without needing their own cloud account, cluster, or server setup.

Why start with Wodby Cloud

  • No need to set up your own cloud account, Kubernetes cluster, or server before deploying Node.js apps.
  • Persistent Wodby-hosted clusters billed hourly as Wodby Cloud usage.
  • Each cluster scales between the minimum and maximum node count you set.
  • Good fit for APIs, web apps, and internal Node.js tools on the platform.

Read more about Wodby Cloud or review Wodby Cloud pricing.

Platform features

More than hosting for Node.js

Wodby Cloud gives you the platform around the stack, not just a place to run it. Teams can manage environments, delivery flow, and day-to-day operations in one system instead of combining separate hosting and deployment tools.

That means the value on these hosting pages is both managed infrastructure and a repeatable application platform for ongoing work.

What you get from the platform

  • Managed Node.js stack with services that work together out of the box.
  • Environment management for production, staging, and development.
  • Integrated CI/CD with deployment history and automatic rollback attempts.
  • Managed routing and endpoints, automatic HTTPS, backups, and imports.
  • Controlled automatic updates and app service controls for ongoing maintenance.

Alternative hosting options when you want to own the infrastructure

Managed Kubernetes

Managed Kubernetes is a better fit when Node.js workloads need more flexible scaling, easier upgrades, and stronger high-availability options inside your own cloud provider account.

Budget self-hosted Kubernetes

Self-hosted Kubernetes on your own dedicated servers is a practical budget option for smaller Node.js services and multi-app setups that do not need autoscaling. You can keep multiple applications on one server, add worker nodes as you grow, and still work with a Kubernetes-based platform.

Read more on the self-hosted Kubernetes page.

Who this is for

Node.js teams that want the quickest start usually get the clearest value from Wodby Cloud because there is no cloud account or server to prepare.

If infrastructure ownership matters more later, the same stack can move to managed Kubernetes in your own account or to a self-hosted Kubernetes setup on your own servers.

Continue exploring

Managed hosting

Ready to run Node.js on Wodby Cloud?

Start with Wodby's managed Node.js stack and get environments, delivery workflow, and day-to-day operations in one hosted platform.

Connect the services your apps already use

An integration links Wodby to an account you already have, such as your Git provider, a storage bucket for backups, or an API your app calls.

Connected once
Set up a service once and reuse it across your apps.
Out of your code
Credentials stay out of your repositories and are managed in one place.
Per environment
Override any value for each environment.

Next step

Want to see what the Node.js stack includes first?

Review the services in the stack, then create an account to run Node.js on Wodby Cloud with environments, deployments, and stack operations managed from one place.

Trusted by developers and businesses worldwide since 2015

Wodby is a reliable cloud infrastructure partner for your business.
See what our customers say about their experience with Wodby.

  • We moved our Drupal hosting to use Wodby and changed our development workflow to use Docker at the same time. Now we can concentrate on Drupal development and we're not losing time configuring servers etc. When a site needs additional resources or hosting in a different region we can be way more responsive as deploying a new instance takes no time at all.

    Tony Miller
    Eighty Options
    Tony Miller, Eighty Options
  • Wodby’s innovative infrastructure helped us to increase the speed and simplify our app deployment, while also leaving us the freedom of handling our hosting and not locking us on a specific pattern. We are now much more robust for future growth and will be able to innovate faster.

    Martin Normann Lund
    Ramsalt Lab
    Martin Normann Lund, Ramsalt Lab
FAQ

Frequently Asked Questions

Have questions? We've got answers. If you don't see your question here, feel free to reach out.

Get started

Start deploying apps with Wodby

Choose Wodby Cloud, managed Kubernetes, or your own server, then deploy stacks with CI/CD, backups, SSL, integrations, and environment management in the same platform.

  • Run the same stack workflow on Wodby Cloud, managed Kubernetes, or your own server
  • Deploy app environments for production, staging, previews, and development
  • Use Wodby CI or your existing pipeline with the Wodby CLI
  • Keep backups, certificates, integrations, and access control in the platform

Start for free

No credit card required
$0/month
  • 10 app services
  • 30 minutes of integrated CI
  • 5 GB of private registry
  • Stacks & integrations
  • Technical domains with SSL
Create free account
Upgrade when you need more capacity