Skip to main content

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.

A cell is an isolated deployment of S2 within a specific scope, which is the combination of cloud provider and region — for example, aws:us-east-1. Each cell has its own compute, storage, and networking resources; see Architecture for internals. An S2 account, i.e. your organization, has exactly one home cell per scope. When you create a basin, you choose from the available scopes. The basin endpoint routes to the right cell via DNS.
Pick a scope that most closely matches your workloads when creating a basin, for the lowest latencies.

​
Tenancy

Cells are multi-tenant by default, which is how S2 offers purely usage-based 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.
Private networking works with both multi-tenant and dedicated cells.