Choose where your data runs
Every project runs on one data plane: the cluster that runs tasks and stores conversations, files, memory, and telemetry. Configuration and identity live in the control plane, run by Introspection.
1. Choose a deployment model
| Managed Cloud | BYOC | On-prem | |
|---|---|---|---|
| Data plane runs in | Introspection’s cloud | Your AWS, GCP, or Azure account | Your private or air-gapped environment |
| Operated by | Introspection | Introspection, in your account | Agreed per Enterprise contract |
| Choose it when | You want the fastest path | Data must stay in your cloud account | The platform must run privately |
For BYOC or on-prem, contact Introspection.
2. Pick a region
You pick a project’s data plane, and so its region, when you create the project in the dashboard. It never changes, and every runtime in the project uses it. The organization’s Data planes page shows each plane’s cloud, region, and health. For the list of regions, contact us.
To keep agent model calls on a provider endpoint in your region, use your own
model keys (llm_mode: byok, see Choose and change models).
3. Know what leaves your cloud on BYOC
Conversations, tasks, files, memory, telemetry, observations and judgements are stored in the data plane in your account. BYOC keeps that storage in your cloud; it does not keep all content from leaving it. By default, conversation text still goes out for processing:
| Leaves your cloud | Why |
|---|---|
| Calls to the control plane (sessions, tokens, member lookups, usage) | The control plane holds member identities, audit records, and your bindings’ credentials, encrypted |
| Observation extraction (always) | Conversation text goes through Introspection’s model gateway. To turn it off for a project, contact us. |
Agent model calls and live judges on a managed runtime | They go through the gateway; on byok they call your provider. |
| Per-user connections | Tool calls go to Pipedream; authorization runs through the control plane |
| Calls to any MCP server or API you bind outside your cloud | The agent calls them from the sandbox |
What you can rely on
| Guarantee | What it means |
|---|---|
| Tenant isolation | The organization comes from your credential, never from the request |
| One sandbox per task | Each task runs in its own sandbox; outbound hosts are allowlisted |
| No real credentials in the sandbox | See Secrets |
| Read-only recipe access | A runtime gets a read-only token for its own recipe repository unless you grant write |
| Encryption | See Your data |
Verify
introspection whoami # dp_url is the data plane your project usesLimits
| Not supported | Do this instead |
|---|---|
| Moving a project to another region | Create a new project on the plane you need. |
| Redacting content before it is recorded | Keep sensitive values out of prompts and tool results, and ask us to turn off observation extraction. BYOC alone does not keep content in your cloud. |