Node.js Dev Center

Node.js Developer’s Center

The platform provides an out-of-the-box integration of the fast, lightweight, and highly scalable Node.js application server. It includes optimization, deployment, package-management, process-management, scaling, networking, and automation tools for convenient Node.js hosting.

In this article
Node.js cloud hosting
Node.js hosting tools and capabilities available on the platform.

Node.js Environment Hosting

Use the topology wizard to create a Node.js environment. Open the Node.js tab, choose the required engine version, and add any other software stacks required by the application. You can also adjust Cloudlet limits, node count, Public IPv4 or IPv6, and other topology parameters.

Node.js topology wizard
Create and configure a Node.js environment through the topology wizard.
i

Isolated and highly available nodes

Each instance runs in a completely isolated container. Scaled-out nodes are automatically distributed across physical servers or virtual machines to improve availability.

Node.js Versioning

The source page currently lists these supported Node.js releases:

  • Node.js 16.20.0
  • Node.js 20.20.0
  • Node.js 22.22.0
  • Node.js 24.13.1
  • Node.js 25.6.1

Select the required version during environment creation. For an existing environment, change the version through container redeployment. Check the regularly updated Software Stack Versions document for the latest available releases.

Node.js versions
Select the required Node.js engine version in the platform interface.

Node.js Application Deployment

The platform automates deployment using an application archive uploaded from a local computer or external URL, or a remote version-control repository such as GitHub.

Deploy a Node.js application
Deploy Node.js applications from an archive, URL, or remote repository.
✓

Automatic port redirection

Projects are normally accessible through the platform’s port auto-redirect algorithm. To exclude services, list their ports in the REDIRECT_EXCLUDE_PORTS variable.

Node.js Package Managers

npmInstalls project modules, packages, and applications. It is the default package manager.
YarnUses the same project requirements as npm and provides an alternative package-management workflow.

Set PACKAGE_MANAGER to npm or yarn through the container variables.

Node.js package manager variable
Choose npm or Yarn through the PACKAGE_MANAGER variable.

Node.js Process Managers

npmStarts the application through project npm scripts.
PM2Provides application-process management and monitoring.
ForeverKeeps Node.js processes running and restarts them after a failure.

Select the manager during container redeployment or set PROCESS_MANAGER to npm, pm2, or forever. Restart the container after changing this variable.

Domain Management

CNAME redirectUse with the Shared Load Balancer for development and testing environments.
DNS A recordUse with a Public IP for higher-traffic production environments.
Traffic switchingUse domain swapping or the SwapExtIps API/CLI method to redirect users between environments.
Node.js domain management
Bind a custom domain or switch traffic between Node.js environments.

Automatic Vertical Scaling

The platform dynamically allocates RAM and CPU according to current load. Set the maximum Cloudlet limit; one Cloudlet equals 128 MiB of RAM and 400 MHz of CPU.

Node.js automatic vertical scaling
Set the maximum Cloudlet limit for automatic RAM and CPU allocation.

Manual Horizontal Scaling

Stateless modeCreates new nodes simultaneously from the base image template.
Stateful modeCopies the master container filesystem to new nodes sequentially.
Load balancingA load-balancer instance is automatically added when the Node.js layer is scaled out.
Node.js horizontal scaling
Set the Node.js node count and preferred scaling mode.
i

Node limit

The maximum same-type node count depends on the provider. The source notes a common limit of 16 nodes, which support may increase.

Automatic Horizontal Scaling

Open Settings → Monitoring → Auto Horizontal Scaling and configure triggers that add or remove nodes according to CPU, RAM, network, or disk usage.

Node.js automatic horizontal scaling
Configure resource-based triggers for automatic Node.js scaling.

Additional Platform Features

  • Custom or built-in SSL
  • Public IPv4 and IPv6
  • Managed software stacks
  • Container Firewall, endpoints, and environment isolation
  • Dashboard management and direct SSH access
  • Open API and Cloud Scripting
  • Usage-based pricing
  • Account collaboration
  • Multi-cloud distribution

Expected Result

A managed Node.js environment can be created with the required engine version, package manager, process manager, deployment method, domain configuration, networking, and automatic or manual scaling policies.

Important Notes

  • Check Software Stack Versions for the latest Node.js releases.
  • Restart the container after changing PROCESS_MANAGER.
  • Use a Public IP and DNS A record for higher-traffic production applications.
  • Choose stateful scaling when the master filesystem must be copied.
  • Review session handling and shared data before horizontal scaling.
  • Use REDIRECT_EXCLUDE_PORTS when selected ports must be excluded from automatic detection.