---
title: "Shipping Nest and Next Under NDA-Safe Constraints"
description: "How to write about production delivery without leaking private systems."
author: "Mohammad-Pouya Ghourchiani"
canonical: "https://ghourchiani.ir/blog/nda-safe-shipping-notes"
date: "2026-09-10"
lang: "en"
---
# Shipping Nest and Next Under NDA-Safe Constraints

## Direct answer

Talk about process, boundaries, and failure modes — never customer data, internal hostnames, or proprietary schemas.

## What stays public

- Stack choices at the category level (NestJS APIs, Next.js UIs, queues, Mongo)
- Delivery habits: contracts first, thin handlers, explicit health checks
- What broke in the abstract: schema drift, retry storms, ambiguous ownership

## What stays private

Anything that identifies a client, a network path, or a security control map.

## Links

- Related writing: [/blog/nestjs-iot-ingestion](/blog/nestjs-iot-ingestion)
- Experience: [/experience](/experience)
- About: [/about](/about)