Dedicated Tenant Plane

In the dedicated model, your organization receives a separate Tenant Plane runtime and typically a dedicated database, while the Control Plane remains in Atlas Cloud for tenant lifecycle, AI provider configuration, and billing.

When to choose dedicated

• Regulatory or commercial need for infrastructure isolation from other customers.
• Predictable performance: no noisy-neighbor on the TP tier.
• Custom network allowlists or private connectivity to your TP endpoint.

How provisioning works

1. Your contract includes dedicated deployment; CP provisioning may require a purchase order reference (po_number on POST /api/tenants/provision).
2. The provisioning job runs extended steps: infrastructure (when enabled), database setup, and assignment of endpoint_url / db_url on the tenant record.
3. You receive your Tenant Plane URL and admin credentials through your onboarding channel.

Database

• Operational data (incidents, CMDB, runbooks, automation jobs) lives in your dedicated DB attached to that TP.
• Backups and failover follow your Atlas contract and any customer-side requirements (e.g. cross-region read replica).

Connectivity

• Users and integrations call your dedicated TP URL only.
• TP calls the Control Plane for AI routing and central configuration; ensure outbound HTTPS (443) is allowed if you apply egress filtering.

Compared to shared SaaS

Next steps

• Deployment models overview — all modes, DB, and ops.
• Hybrid Deployment — TP in your network, CP in cloud.
• Authentication & user management — users and SSO.