Docs menu

Getting started with Node.js

Deploy a minimal Node.js app to Primcloud end-to-end using a sample Express repo, in about five minutes.

On this page

Deploy a small Node.js app to Primcloud: fork a sample repo, import it, watch the build, and open the app at its *.primcloud.app URL. It takes about five minutes.

Before you start#

You'll need:

  • A Primcloud account. Standard accounts have no monthly fee; compute is metered by the minute once you deploy, from around $5/mo for the smallest app.
  • A git provider connected to your Primcloud account; see Source Control.
  • Optional: Node.js 22, 24, or 26 installed locally, if you want to run the sample or make changes before deploying.

The sample app#

This guide uses Heroku's heroku/nodejs-getting-started repo. It's a minimal Express app that builds on Primcloud with no changes. Fork it into an account you've connected to Primcloud.

It has the two files the build needs: a package.json with engines.node and a start script, and npm's lockfile, package-lock.json.

1. Create the application#

Hit Import Git Repository on the applications list, then:

  1. Select your fork of nodejs-getting-started.
  2. Configure the branch (main) and a region.
  3. Verify the commit and hit Import.

2. Deploy#

The first deployment starts as soon as the app is created, and its build log streams live:

Primcloud finds package.json, installs the Node.js version from engines.node, and installs the dependencies with npm ci, since the repo has a package-lock.json. The sample has no build script, so nothing else runs before its web process starts.

When the deployment's Rollout phase shows Complete, the app is live.

3. Reach the app#

Click the *.primcloud.app URL in the dashboard header to open the app.

If it doesn't come up:

  • The deployment's build log has the output from the build, including npm errors.
  • The Logs tab has your app's output, including startup errors.
  • Check that the app listens on process.env.PORT, as the sample does.

Where to go next#