NestJS hosting
on Shipped.
Take your NestJS modules, controllers, and providers online. Shipped handles running the service and the infrastructure around it.
Deploy the application your modules describe
Build your NestJS project and run its production server as a web service. The framework keeps responsibility for controllers, providers, and dependency injection. Shipped supplies the public endpoint and HTTPS, giving your backend a stable address for frontend clients, mobile apps, and partner integrations.
Give background work its own process
A NestJS backend may combine HTTP endpoints with queues, scheduled operations, and database access. Separate long-running jobs into a worker where they need independent capacity. Store queue and database credentials as secrets, and keep durable job state outside the web process so deployments do not erase it.
Review changes across the service boundary
Use staging to check that clients still receive the status codes, response shapes, and authorization behavior they expect. Connect GitHub for repository deployments or ship local changes through your agent. Application logs and deployment history make it easier to understand which backend version handled a request.
A little more detail
Questions about NestJS?
Can I keep my chosen NestJS HTTP adapter?
Yes. Package the adapter and dependencies your NestJS app uses, such as its Express or Fastify integration. Your production configuration determines how that server starts.
Can a worker share code with my NestJS API?
Yes. A separate process can share modules and libraries with the web service while using its own start command. Keep their responsibilities and required configuration explicit.
From your workspace to the web