Deployment
The Control Plane is where your organization, members, and billing live, and it is always operated by Introspection. The Data Plane is where the sensitive work happens: agent runs, conversations, observations, files, and telemetry. The deployment model is a choice about where the Data Plane runs, and it’s the main lever for data-residency and compliance requirements.
There are two models, and every organization is on one of them.
The two models
Managed multi-tenant
The default. Your organization runs on Introspection’s shared Data Plane infrastructure, alongside other organizations, with strict logical isolation: every record is scoped to your org and stays separated from every other tenant. This is the fastest way to get started and the most cost-effective, with automatic scaling and no infrastructure to operate.
Dedicated single-tenant
Your organization gets its own Data Plane infrastructure, separate from every other tenant, reachable on its own subdomain (for example acme.dp.introspection.dev). Isolation is guaranteed at the infrastructure level rather than only logically. This is the model for organizations with compliance or contractual requirements that rule out shared infrastructure, and is an Enterprise offering.
Comparison
| Managed multi-tenant | Dedicated single-tenant | |
|---|---|---|
| Data residency | Introspection-operated shared infrastructure | Introspection-operated dedicated infrastructure |
| Isolation | Logical (per-org scoping) | Infrastructure-level |
| Subdomain | Shared (dp.introspection.dev) | Own subdomain (acme.dp.introspection.dev) |
| Who it’s for | Most teams getting started | Compliance-driven organizations |
A dedicated deployment is genuinely its own environment, not shared with any other tenant, so its isolation is more than network separation.
Choosing a model
- Start on managed multi-tenant. It’s the default, and your data is isolated by organization across the platform.
- Move to dedicated single-tenant when you need infrastructure-level separation, typically a compliance, audit, or contractual requirement.
The deployment model is a property of your organization’s setup, not of any single project: all of an org’s projects are linked to deployments under the same model. Changing models is an operational change coordinated with Introspection, not a self-serve toggle.
Related
- Security model: isolation, encryption, and credential handling across both planes.
- Infrastructure: encryption, networking, and identity behind both models.
- Organizations, projects & members: the tenancy model deployments sit beneath.