Frameworks/Deploy NestJS on your own server
NestJS

Deploy NestJS on your own server

Push a NestJS API and Deplo builds it and starts it, on a server you own, with HTTPS in front.

From repo to live in three steps

  1. 01Connect the repository that holds your NestJS app.
  2. 02Deplo detects NestJS and sets the install, build and start commands and the port.
  3. 03Push to the branch: every push builds and rolls out a new version.

What Deplo sets up

  • Detected from nest-cli.json or the NestJS dependencies.
  • Install, build and start commands chosen for you, with port 3000 already set.
  • A managed database in the same environment, reachable over the internal network.
  • HTTPS through Traefik as soon as the domain points at the server.

Detection runs on every deploy and is never stored, so a change to the project is picked up by the next push.

NestJS on Deplo

Short answers to what comes up before moving a NestJS app onto your own server.

Read the PORT variable: Deplo sets it to the app's port, and you can change that port in the settings.

Yes. Managed databases live in the same environment and reach the app over the internal network.

No. The new container has to pass its health check before the old one is retired.

Ten minutes from now,
it's live.

Answer three questions and pick a host, or install Deplo on a server you already have. It's free, and leaving is as easy as arriving. What you do with the money you save is your business.