> ## Documentation Index
> Fetch the complete documentation index at: https://docs.baseten.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose your hosting option

> Choose where your inference workloads run based on infrastructure ownership, isolation, connectivity, capacity, and data residency.

**Baseten Cloud** is the default hosting option and the best fit for the vast majority of teams. **Single-tenant** and **self-hosted** are enterprise-grade hosting options for organizations that have exceptionally strict isolation or data-control requirements.

Where your inference workloads run determines who owns and operates the infrastructure, how workloads connect to your applications, and which capacity and data-residency constraints apply. Baseten Cloud, single-tenant, and self-hosted use the same deployment and operations workflow, but place the workload plane in different environments.

Baseten separates orchestration from inference:

* **Control plane**: Manages your models, handling builds, scheduling, and lifecycle.
* **Workload plane**: Routes inference requests and runs model replicas on GPUs.

Baseten operates the control plane for every option. The location, ownership, and tenancy of the workload plane change. For more information about the shared architecture, see [How Baseten works](/concepts/howbasetenworks).

## Hosting option comparison

|                    | [Baseten Cloud](/hosting-options/cloud)                                 | [Single-tenant](/hosting-options/single-tenant)        | [Self-hosted](/hosting-options/self-hosted)                |
| ------------------ | ----------------------------------------------------------------------- | ------------------------------------------------------ | ---------------------------------------------------------- |
| **Workload plane** | Baseten's multi-cloud fleet.                                            | An isolated VPC in Baseten Cloud.                      | Your cloud account and VPC.                                |
| **Operations**     | Baseten operates the infrastructure.                                    | Baseten operates the infrastructure.                   | Shared responsibility model. You procure capacity.         |
| **Tenancy**        | Multi-tenant infrastructure with isolated workloads and dedicated GPUs. | Compute and networking dedicated to your organization. | Compute and networking dedicated to your organization.     |
| **Connectivity**   | Public inference endpoints with TLS and regional routing controls.      | Public or provider-native private connectivity.        | Your load balancer, security groups, and network policies. |
| **Capacity**       | Pooled, on-demand capacity across clouds and regions.                   | Dedicated capacity managed with Baseten.               | Capacity that you procure from your cloud provider.        |

Choose **Baseten Cloud** unless an infrastructure, isolation, or networking requirement rules it out. Choose **single-tenant** when you need dedicated isolation or private connectivity without operating infrastructure in your own account. Choose **self-hosted** when inference must run in infrastructure you control.

## Hybrid hosting

[Hybrid](/hosting-options/self-hosted#hybrid) combines self-hosted workload planes with Baseten Cloud. Use it when requirements differ across workloads and you want to place each workload in the appropriate environment. Hybrid extends self-hosted rather than replacing it as a separate infrastructure model.

## Next steps

* To deploy on Baseten Cloud, [sign up](https://app.baseten.co/signup) and follow the [quickstart guide](/quickstart).
* To scope single-tenant, self-hosted, or hybrid hosting, [talk to us](https://www.baseten.co/talk-to-us/).