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

# Cells

> S2 cells isolate compute, storage, and networking by provider and region to define fault domains and support tenancy and scaling.

A cell is an isolated deployment of S2 within a specific [**location**](/concepts/basins#location), which is the user-visible combination of cloud provider and region — for example, `aws:us-east-1`.

Each cell has its own compute, storage, and networking resources; see [Architecture](/platform/architecture) for internals.

An S2 **account**, i.e. your [organization](https://s2.dev/dashboard), has exactly one home cell per location.

When you create a basin, you choose from the available locations. The basin [endpoint](/api/endpoints) routes to the right cell via DNS.

<Tip>
  Pick a location that most closely matches your workloads when creating a basin, for the lowest latencies.
</Tip>

## Tenancy

Cells are multi-tenant by default, which is how S2 offers purely usage-based [pricing](https://s2.dev/pricing). Idle accounts can scale to zero, while active workloads can burst into pooled capacity.

Dedicated cells are available with a minimum commitment. They are useful when you want stronger isolation than the default multi-tenant fleet — [contact us](mailto:hi@s2.dev).

<Tip>
  [Private networking](/platform/private-networking) works with both multi-tenant and dedicated cells.
</Tip>