liveBook · Manning

Deployment posture

As explained in Context Engineering

An adoption model is an organizational approach to integrating and operating generative AI within systems, processes, and governance boundaries.

An adoption model describes how an organization integrates and operates generative AI within its systems, processes, and governance boundaries. Its operating posture shapes control over models, context artifacts, data flows, observability, and operational responsibilities. section 9.3.1

Table 9.4 Adoption models for context-engineered systems
Adoption model Operating boundary Context engineering control Operational burden

SaaS consumer

Vendor hosts the application and the model

Prompts, plus the connectors, retention options, access controls, and audit logs the vendor exposes

Low

API integrator

Organization owns the application, provider hosts the model endpoint

Full context layer: retrieval, tools, memory, state, guardrails, evaluation, and tracing

Medium

LLM off-the-shelf

Organization deploys a provider-supplied or open-weight model in its own or a managed environment

Context layer, plus serving configuration, adaptation, and context caching

High

Model hoster

Organization operates the model platform in a private network, VPC, or regulated environment

Context layer, plus model serving, logs, security boundaries, data locality, and model lifecycle

Very high

Compare SaaS consumer, API integrator, LLM off-the-shelf, and model hoster postures by operating boundary, context-engineering control, and operational burden. section 9.3.1

Using multiple postures

An organization might use a SaaS assistant for internal productivity and an API-based agent for a customer-facing workflow. section 9.3.1

How Context Engineering covers it

How deep it goes
Compares four postures by operating boundary, context-engineering control, and operational burden.
Examples
Illustrates SaaS assistants for internal productivity alongside an API-based agent for a customer-facing workflow.
What you can do after
Evaluate adoption choices by comparing operating boundaries, context control, and operational burden.
How it connects
Links adoption posture to context engineering, data flows, model access, observability, and serving responsibility.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Context Engineering. The section links point to the parts of the book it draws on.