Secure Delivery · 01 of 3
Delivery Patterns
No customer data offshore, one agent in two environments, and other boundary patterns.
01
One Agent, Two Environments
Built in one zone, run in another. The drawing shows the secure side: open-weight models behind one gateway.
- Development zoneMock and synthetic data, public models for speed, NGT engineers.
- Your secure zoneYour real data stays put; a self-hosted open-weight LLM; people you approve.
- Between the twoReviewed release packages only. Nothing flows back out.
Hybrid LLM Gateway
Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.
02
Crossing the Boundary
- 01Build
- Agent core, logic and tests
- On mock or synthetic data
- 02Review
- Source code reviewed
- Every package checked
- 03Check
- Licence checks
- SBOM
- Vulnerability scan
- 04Approve
- You approve the release
- Before anything is imported
- 05Import
- Imported into your zone
- Connected through your adapters
03
More Boundary Patterns
SourcesFPT Software Hanoi executive outlook, secure AI delivery patterns (Oct 2026)NGT self-hosted MLOps practice notes (2026)AI-First DevOps Transformation Services & Solutions (Oct 2026)NGT Platform Engineering v1.2 (Sep 2026)NGT DevSecOps Service Offering (Jan 2025)NGT Cloud managed-service map (Mar 2026)FPT Full SDLC with GenAI and multi-agents v1.2.4 (Jun 2025)FleziLift runbook and connector notes (Oct 2026)
