The deployment path recommendation is one of the most consequential calls on a Claude Code engagement. It determines who bills the client, how developers authenticate, where usage data lands, and which features exist. It's also difficult to change mid-engagement, which is exactly why it needs to land in the pre-kickoff window, not as a change request after rollout.
This course builds the knowledge to make and defend that recommendation. You'll cover:
- The four deployment paths; Claude for Enterprise direct, Amazon Bedrock, Google Vertex AI, and Microsoft Foundry, and the four questions that narrow the field: cloud commitments, buying route, compliance posture, and who manages users and budgets
- Feature parity gaps between the paths, including what's unavailable on cloud-native routes (WebSearch, Zero Data Retention eligibility, bundled Claude web access), and how to put those gaps in front of the client before contract, not after
- Corporate proxy configuration: HTTPS_PROXY, HTTP_PROXY, TLS inspection, and how enterprise network setups behave during install and at runtime
- LLM gateway patterns for centralized authentication, per-team cost chargeback, and spend controls across large developer cohorts
- Data residency, ZDR eligibility, and how to answer the compliance questions a client's security team will bring to the table
The practice exercise is a deployment path recommendation for a sample client profile, including rationale on cloud commitments, parity gaps, and compliance posture. That recommendation becomes your course artifact: the Deployment Decision Doc, a structured template you'll use on live engagements.
Time In Skilljar (Measured) 1 Hour 16 Minutes
Practice & Artifact Building (Estimated Time In Skilljar) 50 Min
