Keep the Express build you already use
Use npm ci and the existing build script when the app compiles TypeScript or bundles source. Plain JavaScript services can start directly from the committed entrypoint.
Apps and APIs · plans from $10/month
Deploy Express.Keep the Node.js process observable.
Run an Express API as a persistent Node.js process with its install command, port, health endpoint, secrets, logs, and promoted release connected.
Keep the repositoryInspect build and logsCustom domains and TLS
Adios deploy
Candidate release
Express
SOURCE
Git
REGION
de
ROUTE
HTTPS
01Source received
02Build completed
03Runtime started
04Health check passed
Promoted route
production.adios.run
A production path for
ExpressNode.js 24REST APIsWebSocketsnpm
The production path
A working Express 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.
Promote the version that reports healthy
Listen on the port supplied by the runtime, expose a health route before other middleware where appropriate, and inspect startup errors before promotion.
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.
- 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 - 02
Review the deployment contract
Keep commands, runtime or service version, health behavior, and secret references in adios.yaml.
$git diff -- adios.yaml - 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 projectname: express-api
build_cmd: npm ci
start_cmd: node server.js
runtime:
name: node@24
port: 8080
health_path: /healthzReplace server.js with your production entrypoint and add npm run build when the project compiles source first.
Deployable starting points
Start Express from a template when the repository is not ready.
Use the Express starter to inspect the health route, package setup, runtime port, and deployment manifest before replacing the example API.
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 upBefore 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…
- npm ci succeeds from package-lock.json.
- The service listens on the configured port rather than localhost only.
- Errors reach logs without leaking credentials.
- Database and API keys use secret references.
Preview when…
- Native Node modules compile during installation.
- The app holds WebSocket or streaming connections.
- The process depends on Redis, a queue, or a database at startup.
Questions, answered
What to know before deploying Express.
Review the runtime or service boundary, template path, failure behavior, and production checks before creating the first release.
Can Adios deploy an existing Express 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 Express?
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 deploy an Express TypeScript project?
Yes. Add the TypeScript build command, start the emitted JavaScript from its output directory, and keep the build artifact path explicit in adios.yaml.
Can Express serve WebSockets or server-sent events?
Yes. Test long-lived connections, graceful shutdown, proxy headers, and release transitions in a preview before production clients depend on them.
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 Express 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.
Deploy Node.js
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 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 PostgreSQL
Choose a PostgreSQL version, keep database credentials out of Git, attach persistent storage, connect the application, and verify data after a restart.
The first release
Deploy Express 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.