Node.js apps, properly hosted

Deploy

From npm run build to live in four steps

Nothing Node-specific to learn. A VM, a process manager and a CDN deployment.

~/acme-api — zsh

$ edge compute create --name api \

--size s-2vcpu-4gb --image ubuntu-24 \

--region london --script nodejs \

--script-param node_version=22

✓ vm-51ac3e running · Node 22 · PM2

$ rsync -a dist package*.json api:app/

$ ssh api 'cd app && npm ci --omit=dev'

$ ssh api 'cd app && pm2 reload all'

✓ api · cluster mode · 2 instances online

$ curl -s https://api.acme.dev/health

Cold starts0

api.acme.devHealthy

RuntimeNode 22 · Hono

Processpm2 · 2 instances

1. 01

   Create a VM with Node

   The nodejs library script installs Node 22 LTS, PM2 and an Nginx reverse proxy on first boot.

   shellCopy

   $ edge compute create --name api --size s-2vcpu-4gb \
       --image ubuntu-24 --region london --script nodejs \
       --script-param node_version=22

2. 02

   Connect to Edge Storage

   The official AWS SDK works unchanged. Only the endpoint and path-style addressing differ.

   src/storage.tsCopy

   import { S3Client, PutObjectCommand } from '@aws-sdk/client-s3'
   
   export const s3 = new S3Client({
     endpoint: 'https://storage.edge.network',
     region: 'us-east-1',
     forcePathStyle: true,
     credentials: {
       accessKeyId: process.env.EDGE_ACCESS_KEY!,
       secretAccessKey: process.env.EDGE_SECRET_KEY!,
     },
   })
   
   export const upload = (Key: string, Body: Buffer) =>
     s3.send(new PutObjectCommand({ Bucket: 'acme-files', Key, Body }))

3. 03

   Keep it running with PM2

   pm2 reload gives zero-downtime restarts across both instances. Run pm2 startup once so it survives reboots.

   ecosystem.config.cjsCopy

   module.exports = {
     apps: [{
       name: 'api',
       script: 'dist/server.js',
       instances: 2,
       exec_mode: 'cluster',
       env: { NODE_ENV: 'production', PORT: 3000 },
     }],
   }

4. 04

   Front it with the CDN

   Only GET responses with a cacheable Cache-Control header are cached. POSTs, errors and anything with Set-Cookie go straight to your process.

   shellCopy

   $ edge cdn create --name acme-api
   $ edge cdn domains add cdn-72e9b3 \
       --domain api.acme.dev \
       --origin https://<vm-ip>

Prefer to hand it off? Give the job to your AI agent or have our engineers do it.