Updated · 2026-06-23

Recipe: deploy a Node app from GitHub

Ask your agent to deploy your repo. It provisions a nodejs-24 VM (Node 24 + supervisor, :3000 auto-exposed), uploads your code, and returns a live HTTPS URL. Wire the official deploy Action for push-to-main deploys.

The fastest path for any Node/JS app (Express, Next.js, Fastify, Vite/React). The nodejs-24 image ships Node 24 + npm/pnpm/yarn and an app supervisor that auto-runs whatever lands in /root/app and auto-exposes :3000 — so a bare create already yields a live URL.

One prompt

deploy my Node API from github.com/me/app

Your agent chains:

  1. create_vm with image: nodejs-24 — boots Node 24, supervisor watching /root/app, port :3000 exposed at https://vm-abc123-3000.superjolt.host.
  2. upload (or git clone via exec) to put your project in /root/app.
  3. For a build-step framework (Next.js, Vite), exec npm ci && npm run build in /root/app, then superjolt-app restart.

The VM is live in seconds. Ask list_vms any time to see status, tier, and a right-sizing hint.

Push-to-deploy

For continuous deploys, wire the official Action — push to main, deploy to the VM, no SSH key in GitHub Secrets. See Deploy from GitHub Actions for the workflow YAML and token setup. Prefer raw SSH (rsync/ansible)? See Deploy via SSH.

Notes

  • Long builds (npm ci) can exceed the ~100s synchronous exec edge limit — your agent runs them via exec_async + exec_poll. See Troubleshooting.
  • Watch spend with account_status (burn rate + runway). Stop the VM when idle — but note stopped VMs still bill (VM tiers).