# Configure build and start for NestJS

Build and start for a NestJS app on Ample. Verified on NestJS: the app built and started with the documented commands and answered on its public HTTPS URL. Build and start: npm install, nest build (TypeScript) then node dist/main.js on the node-22 template.

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86\_64 Firecracker microVMs; sizes are the priced VM sizes.

## You need

- A NestJS project (npm install, nest build (TypeScript) then node dist/main.js on the node-22 template)
- An Ample account token with servers:write

## Exact tested configuration

- build npm run build --if-present
- install npm install
- runtime node
- sizes-1vcpu-1gb
- start npm run start
- template node-22

## Steps

1. **Build and start.** npm install, nest build (TypeScript) then node dist/main.js on the node-22 template; the server must bind 0.0.0.0 on PORT.
2. **Deploy.** Run the synchronous deploy once and read the result.
   
   ```
   $ ample deploy . --name <app-name> --public
   ```
3. **Verify.** Fetch the live URL on the example; on failure read the build and runtime logs.
   
   ```
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓ app responds on its public URL· http get/ → “ample canary nestjs patterns”

## Evidence

1. November 6, 2026 · canary run

NestJS pattern fixture deployed on Ample (npm install, nest build (TypeScript) then node dist/main.js on the node-22 template); for this guide: the app built and started with the documented commands and answered on its public HTTPS URL.

## Tested examples

- **NestJS pattern fixture.** Verified build and start on NestJS.

## What it doesn’t cover

- Verified on the node-22 template at s-1vcpu-1gb.
