Adios
Apps and APIs · plans from $10/month

Deploy Node.js.Run the real production command.

Deploy a persistent Node.js web process or worker from its existing package scripts, with release health, logs, secrets, routing, and Git history attached.

Deploy my projectDeploy a template
Keep the repositoryInspect build and logsCustom domains and TLS
Adios deploy

Candidate release

Node.js

Healthy

SOURCE

Git

REGION

de

ROUTE

HTTPS

01Source received

02Build completed

03Runtime started

04Health check passed

Promoted route

production.adios.run

A production path for

Node.js 24ExpressFastifyNestJSHonoWorkers

The production path

A working Node.js project still needs a safe release.

The application or service is only one part of production. Build evidence, runtime state, health, secrets, logs, routes, and the promoted version should remain inspectable together.

Keep the Node.js build you already use

Install from the committed lockfile and run the project's existing build script. JavaScript and TypeScript applications keep their normal package layout and commands.

Promote the version that reports healthy

Start the production entrypoint, bind to the declared port, and require a health response before the candidate becomes the current release.

Trace production back to source

Build output, runtime logs, health state, secrets, domains, and the promoted release stay attached to the project instead of being split across unrelated tools.

From source to release

Three steps keep the deployment path reviewable.

Use the source and production behavior the project already has. The manifest records what the platform should build or provision and how the result becomes ready.

  1. 01

    Start with source or a template

    Bring the existing repository, or inspect and deploy one of the exact starter variants linked below.

    $adios login
  2. 02

    Review the deployment contract

    Keep commands, runtime or service version, health behavior, and secret references in adios.yaml.

    $git diff -- adios.yaml
  3. 03

    Deploy and inspect the result

    Follow build and runtime evidence, verify the candidate, and open the promoted route or service connection.

    $adios up
adios.yaml
Your project
name: node-service
build_cmd: npm ci && npm run build
start_cmd: node dist/server.js

runtime:
  name: node@24
  port: 8080
  health_path: /healthz
Match the package manager, output directory, start command, and health path to your project.

Deployable starting points

Start Node.js from a template when the repository is not ready.

Choose Express, Fastify, or NestJS when you want a framework-specific starting point, or inspect Hono for a smaller API surface.

API starters

Node.js Express

Express, Fastify, Hono, and NestJS starters with production-ready start commands.

JavaScriptnpm
Template key
node-express
Runtime
node
Repository
templates
Source path
nodejs/express
git clone https://github.com/adiosdotdev/templates.git
cd templates/nodejs/express
adios up
DeployView source

API starters

Node.js Fastify

Express, Fastify, Hono, and NestJS starters with production-ready start commands.

JavaScriptnpm
Template key
node-fastify
Runtime
node
Repository
templates
Source path
nodejs/fastify
git clone https://github.com/adiosdotdev/templates.git
cd templates/nodejs/fastify
adios up
DeployView source

API starters

Node.js Hono

Express, Fastify, Hono, and NestJS starters with production-ready start commands.

JavaScriptnpm
Template key
node-hono
Runtime
node
Repository
templates
Source path
nodejs/hono
git clone https://github.com/adiosdotdev/templates.git
cd templates/nodejs/hono
adios up
DeployView source

API starters

Node.js NestJS

Express, Fastify, Hono, and NestJS starters with production-ready start commands.

TypeScriptnpm
Template key
node-nestjs
Runtime
node
Repository
templates
Source path
nodejs/nestjs
git clone https://github.com/adiosdotdev/templates.git
cd templates/nodejs/nestjs
adios up
DeployView source
Review the runtime manifest

Before production

Verify the workload.Then promote it.

The safest first release starts with a reproducible build or service configuration and a preview that exercises the dependencies production will actually use.

Ready when…

  • Dependencies install from a locked package graph.
  • The production command does not use a development watcher.
  • The process binds to the manifest port.
  • Runtime credentials are not committed to source.

Preview when…

  • Native modules or browser binaries install during the build.
  • The app uses workers, WebSockets, or streams.
  • Startup depends on a database or message broker.

Questions, answered

What to know before deploying Node.js.

Review the runtime or service boundary, template path, failure behavior, and production checks before creating the first release.

Can Adios deploy an existing Node.js project?

Yes. Run the Adios CLI from the project root, keep the repository and dependency files you already use, and add an adios.yaml file that describes the production build, start command, port, and health path.

Do I need Docker to deploy Node.js?

Not for a standard supported runtime. Use the project's normal production commands in adios.yaml. If the build needs unusual operating-system packages or native libraries, verify those dependencies in a preview before promotion.

Can I use npm, pnpm, or another Node.js package manager?

Use the package manager and lockfile already chosen by the repository, then put its deterministic install and production commands in adios.yaml.

Can a Node.js worker run without an HTTP route?

Yes. Give the worker a persistent start command and define a useful health strategy. Test retry, shutdown, and dependency failure behavior independently from web traffic.

What happens when the build or health check fails?

The candidate release keeps its build and runtime output for inspection. It must report healthy before it becomes the promoted version serving the application route.

Can I start from a template instead of an existing repo?

Yes. This page links to the closest official Adios Node.js starters. Inspect the exact source variant, deploy it in the console, or clone it locally and run adios up.

Related deployment paths

Connect the rest of the stack.

Browse all deployment pages

Deploy Express

Run an Express API as a persistent Node.js process with its install command, port, health endpoint, secrets, logs, and promoted release connected.

Deploy Fastify

Deploy a Fastify service from its existing Node.js source, bind it to the production port, verify readiness, and inspect the exact build serving traffic.

Deploy NestJS

Build a NestJS application from source, start the emitted production entrypoint, verify dependency readiness, and keep deployment evidence beside the project.

Deploy Adios workflows

Deploy scheduled jobs, webhook processors, approval gates, maintenance tasks, and operational automation from a versioned workflow manifest.

The first release

Deploy Node.js with the source and evidence attached.

Start from the repository or a template, review the deployment contract, and inspect what becomes the promoted production version.

Start with AdiosCompare plans