Service type
App service
App service
Node.js service
Runtime service for Node.js APIs, workers, and custom application workloads.
Use it as a versioned stack building block that can build from source, plug into CI/CD, and connect to external providers without hardcoding secrets into the codebase.
Why teams use this service
Technical profile
Review versions, ports, source, and packaging.
Stacks that use it
See where this service fits in ready-made stacks.
Source builds and CI/CD
Build from Git, use Wodby CI, and publish images cleanly.
Runtime wiring and defaults
See ports, links, storage, configs, and runtime behavior.
Build on top of this service
See derived services that extend the same runtime.
Overview
Technical profile and packaging
This page shows how Node.js is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.
Versions
24, 22, 20
Source repository
Public Helm chart
Ports and protocols
3000/HTTP
Labels
node
Stacks
Use it inside ready-made stacks or your own
These public stacks already include Node.js as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.
CI/CD
Build from source and ship changes without extra glue work
Node.js can build from source as part of a stack. Connect your repository, start from a public build template when one exists, and keep CI/CD and image storage inside the same Wodby workflow.
Express.js boilerplate
Start from a working boilerplate instead of wiring the build process from scratch.
wodby/expressjs-boilerplateGit providers
Connect repositories from supported Git providers when this service should build from your own codebase.
CI providers
Wodby CI is the default path, but external CI providers can fit the same build and release workflow when that suits your team better.
Container registries
Keep built images in Wodby Registry by default or store them in another registry without changing how the service is built.
Runtime wiring
Reuse connectivity, storage, and runtime defaults
This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.
Endpoints
3000/HTTP
Technical domains
HTTP endpoints from this service can use technical domains with auto-renewed TLS certificates on Wodby.
Service links
These links define which other services can connect to Node.js when it is used inside a stack.
db
Eligible linked services
sendmail
Eligible linked services
redis
Eligible linked services
Derived services
Build your own service on top of Node.js
These services already extend Node.js. They show how the same base runtime can be turned into more specialized building blocks without rebuilding everything from scratch.