Stack detection
Deployxa reads your repository and picks the runtime, build and start commands. Override any of them in project settings.
Deploy NestJS on Deployxa.
Deploy NestJS backends: TypeScript is compiled at build time, migrations run before release, and the API is served over HTTPS.
- 01Detected fromnest-cli.json · package.json
- 02RuntimeNode.js 20 LTS
- 03Build commandnpm run build
- 04Start commandnode dist/main.js
- 05Port3000
- 06HTTPSLet's Encrypt
01 / Quickstart
Deploy from your terminal.
Install the CLI and deploy the NestJS project in your current directory, or connect the repository in the console for push-to-deploy.
- Typical database: PostgreSQL with Prisma or TypeORM
- Build and start commands can be overridden
- Secrets stay out of build logs
$ npm install -g @deployxa/cli$ deployxa login$ deployxa deploy
02 / Guide
How NestJS goes to production.
- 01 /
Compile
nest build produces JavaScript in dist/.
- 02 /
Migrate
Run npx prisma migrate deploy (or your TypeORM migrations) before the new release takes traffic.
- 03 /
Go live
The release is health-checked and served over HTTPS.
03 / Configuration
Environment variables.
Set these in project settings. Values are never written to build logs.
| Variable | Purpose | Example |
|---|---|---|
DATABASE_URL | Database connection string | postgresql://... |
04 / Included
What every deploy gets.
Isolated builds
Every push builds in its own sandbox with cached dependencies and layers.
Managed databases
Attach PostgreSQL, MySQL or Redis and the connection details are injected as environment variables.
HTTPS by default
Every deploy gets a deployxa.online URL with a Let's Encrypt certificate; custom domains too.
Health-checked releases
Traffic only switches to a release that passes its health check, and earlier releases stay available for rollback.
Push to deploy
Connect GitHub, GitLab or Bitbucket and each push to your branch ships a new release.
05 / FAQ
NestJS questions.
How do I run Prisma migrations?
Run npx prisma migrate deploy as part of the release so the schema is current before traffic switches.