How to deploy a NestJS app for free from a ZIP

What the Free plan includes.

Sitedropper Free is a $0 plan for a small real deployment workflow. The dashboard is the source of truth for the current ZIP limit shown beside Choose ZIP.

• Up to 3 projects
• 30 deployments per month
• Draft, Password protected, and Public sharing
• Sitedropper URL

Before you build.

Run the Nest tests and build before packaging. The deployment runtime must start compiled JavaScript, not depend on a globally installed Nest CLI. Sitedropper now prefers start:prod when that script exists.

• @nestjs/core listed in package.json.
• A build script that creates the production JavaScript output.
• A start:prod script and production-safe start selection.
• Bootstrap code that reads process.env.PORT.

Build and check NestJS locally.

Run these commands from the project root. Finish the local check before creating the archive so the deployment is not the first place a dependency, compile, or startup error appears.

The final server command stays running. Open the local URL in another terminal or browser, complete the checks, then stop it with Ctrl+C.

npmpnpmYarn

npm

Check the NestJS project with npm

Use npm when package-lock.json is the project lockfile. If the project has no lockfile yet, run npm install once instead of npm ci and keep the generated lockfile.

Check the NestJS project with npmCopy Check the NestJS project with npm code

npm ci
npm run build
npm run start:prod

pnpm

Check the NestJS project with pnpm

Use pnpm when pnpm-lock.yaml or the packageManager field selects pnpm. Keep the lockfile and any workspace manifest with the source archive.

Check the NestJS project with pnpmCopy Check the NestJS project with pnpm code

corepack enable
pnpm install --frozen-lockfile
pnpm run build
pnpm run start:prod

Yarn

Check the NestJS project with Yarn

Use Yarn only when the checked-in release accepts --frozen-lockfile, which matches Sitedropper’s current generated build. Otherwise choose the project’s npm/pnpm lockfile or an existing Dockerfile instead of changing commands only for upload.

Check the NestJS project with YarnCopy Check the NestJS project with Yarn code

corepack enable
yarn install --frozen-lockfile
yarn run build
yarn run start:prod

Use one dependency workflow: keep the lockfile that matches the selected package manager and do not mix install commands.

Create the ZIP on your operating system.

Package reviewed source and build metadata; use the exclusions to keep local-only files out. The Windows and macOS recipes include graphical menu guidance, while the commands remain the precise archive contract.

No command line required

Directly create the ZIP in your file system.

First create and inspect a clean staging folder containing only the required source, manifest, configuration, and entry-point files. In Windows File Explorer, right-click the reviewed selection and choose Compress to → ZIP File. On macOS, Control-click the reviewed selection and choose Compress Items.

Open the resulting archive before upload. If an outer folder wraps the expected files, recreate the ZIP by selecting the folder’s contents instead.

Or create and inspect the ZIP from the command line.

macOSWindowsLinux

macOS

Compress the reviewed source in Terminal

The exclusions keep common dependencies, caches, local data, and secrets out. Finder users must first make and inspect an equivalent clean staging folder, then select its contents, Control-click, and choose Compress Items—not compress the raw project folder.

1. Run from the project root.
2. Inspect project-specific local files before upload.
3. Confirm the manifest, lockfile or requirements, source, and entry point are present.

Compress the reviewed source in TerminalCopy Compress the reviewed source in Terminal code

if [ -e site.zip ]; then echo "site.zip already exists. Move or rename it before continuing." >&2; exit 1; fi
zip -qr site.zip . -x "node_modules/*" ".venv/*" "venv/*" ".git/*" "__pycache__/*" "*/__pycache__/*" "*.py[cod]" ".next/*" "dist/*" "build/*" "out/*" ".cache/*" ".turbo/*" ".env" ".env.*" "*/.env" "*/.env.*" ".npmrc" "*/.npmrc" "*.sqlite" "*.sqlite3" "db.sqlite3" "*.log" ".DS_Store" "*/.DS_Store" "site.zip" ".sitedropper-package/*"
unzip -l site.zip | head -60

Windows

Stage and compress the source in PowerShell

A clean staging folder prevents dependencies, caches, local databases, and secrets from entering the ZIP. For File Explorer, stop after robocopy, inspect the staging contents, select them, right-click, and choose Compress to → ZIP File; never compress the unreviewed project folder.

1. Run from the folder containing the manifest or requirements.txt.
2. Review the staging folder created beside the project before upload.
3. The command intentionally leaves the staging folder in place and never deletes it automatically.

Stage and compress the source in PowerShellCopy Stage and compress the source in PowerShell code

$ProjectRoot = (Resolve-Path .).Path
$ProjectName = Split-Path $ProjectRoot -Leaf
$Stage = Join-Path (Split-Path $ProjectRoot -Parent) "$ProjectName-sitedropper-package"
if (Test-Path $Stage) { throw "$Stage already exists. Move or rename it before continuing." }
if (Test-Path .\site.zip) { throw "site.zip already exists. Move or rename it before continuing." }
robocopy $ProjectRoot $Stage /E /XD node_modules .venv venv .git .next dist build out .cache .turbo __pycache__ .sitedropper-package /XF .env .env.* .npmrc site.zip *.pyc *.pyo *.sqlite *.sqlite3 db.sqlite3 *.log
if ($LASTEXITCODE -ge 8) { throw "robocopy failed with exit code $LASTEXITCODE" }
Add-Type -AssemblyName System.IO.Compression.FileSystem
$Archive = Join-Path $ProjectRoot "site.zip"
[System.IO.Compression.ZipFile]::CreateFromDirectory($Stage, $Archive)
tar.exe -tf .\site.zip

Linux

Compress the reviewed source in a Linux terminal

The exclusions keep common dependencies, caches, local data, and secrets out. Install your distribution’s zip package first if needed.

1. Run from the project root.
2. Inspect project-specific local files before upload.
3. Confirm the manifest, lockfile or requirements, source, and entry point are present.

Compress the reviewed source in a Linux terminalCopy Compress the reviewed source in a Linux terminal code

if [ -e site.zip ]; then echo "site.zip already exists. Move or rename it before continuing." >&2; exit 1; fi
zip -qr site.zip . -x "node_modules/*" ".venv/*" "venv/*" ".git/*" "__pycache__/*" "*/__pycache__/*" "*.py[cod]" ".next/*" "dist/*" "build/*" "out/*" ".cache/*" ".turbo/*" ".env" ".env.*" "*/.env" "*/.env.*" ".npmrc" "*/.npmrc" "*.sqlite" "*.sqlite3" "db.sqlite3" "*.log" ".DS_Store" "*/.DS_Store" "site.zip" ".sitedropper-package/*"
unzip -l site.zip | head -60

Inspect before upload: compare the ZIP listing with the archive tree below and remove dependencies, caches, local data, and secrets.

Check the archive root.

Keep start:prod aligned with the actual compiled entry (commonly node dist/main). Exclude node_modules and dist because the deployment build recreates them.

site.zip
├── package.json
├── package-lock.json / pnpm-lock.yaml / yarn.lock
├── nest-cli.json
├── tsconfig.json and tsconfig.build.json
└── src/

Upload the NestJS ZIP to Sitedropper.

Create a Draft project, upload site.zip, follow the deployment, and open the generated URL only after the progress reaches Ready.

The dashboard screenshots use fictional project and account data. Yellow outlines identify the documented controls.

1. 01

   Create a project

   Open Projects, choose New project, enter a name, and select the highlighted Create project action. New projects begin as Draft.

   

2. 02

   Upload the ZIP

   Open the project’s Upload and deploy card, then select the highlighted Choose ZIP control or drop the archive into the same area.

   

3. 03

   Open the deployed site

   Wait for Analyze, Build, and Deploy to finish. Then use the highlighted Open Sitedropper site action to review the generated URL.

   

Dashboard screenshot

Dashboard action

Close ×

Check the NestJS result.

Use the deployed URL like a visitor rather than relying only on the successful status.

• Run the production command after the local build, not only nest start --watch.
• Open the root controller or a dedicated health controller.
• Test validation/pipes used by one endpoint.
• Confirm bootstrap reads process.env.PORT and does not require a local .env file.

Update Sitedropper Project settings.

Project settings are separate from framework configuration. Update the project name or description, keep Draft while reviewing, then choose Password protected or Public only when that matches the intended audience. Free does not include Private sharing by email, URL customization, or custom domains.

The dashboard screenshots use fictional project and account data. In the first settings image, the existing yellow outline marks Open site; the Project settings card is visible below and is identified by the instructions.

1. 01

   Review Project settings

   The Project settings card is below the project header. Update the name or description, review the generated URL, and keep the first deployment Draft while you test it.

   

2. 02

   Choose who can open the site

   Open Visibility. Free includes Draft, Password protected, and Public. Select Public only when anonymous access is intentional, then close the menu and choose Save changes.

   

Dashboard screenshot

Dashboard action

Close ×

Finish the change: close the visibility menu, select Save changes, and wait for the “Changes saved” confirmation before leaving the page.

Troubleshoot this NestJS deployment.

The runtime cannot find nest

The production command is still using the development CLI. Make start:prod run the compiled node entry and rebuild.

The compiled entry path is wrong

Inspect dist after the local build and update start:prod to the real output path.

The app starts on port 3000 only

Use process.env.PORT in bootstrap with 3000 as a local fallback.

A module depends on local configuration

Keep secrets out of the ZIP and remove startup requirements that this dashboard workflow cannot configure.

Know the Free-plan boundaries.

• The application must be stateless on its local filesystem.
• Sitedropper does not provide an application database, cron process, or background worker in this ZIP workflow.
• Keep credentials and local environment files out of the archive.

The generated Sitedropper URL remains available on Free. Check the dashboard for current usage and upload limits before starting another deployment.

NestJS deployment FAQ.