Deploying into customer environments

Running a system in infrastructure the customer owns: their cloud accounts, containers and CI/CD, serverless, restricted networks, and the cost and latency profile of LLM systems.

This module covers how a system gets running inside infrastructure the customer owns: their cloud accounts (AWS, Google Cloud and Azure), containers, CI/CD and serverless delivery, and their private, air-gapped or classified networks. It closes with the scaling and performance-cost tradeoffs of LLM systems, which decide whether a deployment survives production.

Lessons (4)

• Deploying into customer clouds: AWS, Google Cloud and Azure · Practice

  Forward deployed work usually ends with software running in an account the customer owns, under their identity, network and compliance rules.

• Containers, CI/CD and serverless delivery · Practice

  Containers, pipelines and serverless functions are the packaging and delivery mechanics behind every customer deployment.

• Networking for private, air-gapped and classified customer environments · Practice

  Many enterprise and government customers run workloads on networks with no public ingress, tightly filtered egress, or no internet connection at all.

• Scaling and performance-cost tradeoffs for LLM systems · Practice

  LLM systems have an unusual cost and latency profile: spend scales with tokens, latency scales mostly with output length, and capacity is bounded by provider rate limits or by GPUs.

Changes

• Version 1, 2026-10-14: re-cut from the role pathway groups into a topic module (site 2026.10.2); no lesson changed