Skip to main content
A cell is an isolated deployment of S2 within a specific cloud provider and region — for example, aws:us-east-1. Each cell has its own compute, storage, and networking resources. See Architecture for details on what’s inside a cell. Every account has a home cell in a given scope. Your basin endpoints route to the right cell via DNS.

Latency

The main impact of cell choice is latency. For the lowest latency, run your workloads in the same cloud region as your cell.

Multi-tenancy

Cells are multi-tenant by default, which is core to how S2 provides serverless scale-to-zero with pure usage-based pricing. Dedicated cells are available with a minimum commitment — contact us.

Private networking

Within a cloud provider, you can connect to S2 privately via AWS PrivateLink, avoiding the public internet and benefiting from reduced egress costs. See Private Networking for setup.

Regions

There is currently one cell: aws:us-east-1. aws:us-west-2 is up next — see the Roadmap for details and timelines on additional regions.