Regions

Pick the region your browsers run in. Sessions, replays, and profile storage are colocated with the region, so picking the one closest to your workload minimizes per-action latency.

Available regions

Selecting a region

Pass region to the SDK constructor. The default is us-west, so existing code keeps working unchanged.

import { Solari } from "@solaribrowser/sdk"

const client = new Solari({
  apiKey: process.env.SOLARI_API_KEY!,
  region: "us-west",   // default — can be omitted
})

Every session created with this client runs in the configured region. To run sessions in more than one region from the same process, instantiate one Solari per region.

What is region-scoped

• Browser sessions — the pool node that serves your session is always in the region you picked.
• Session replays — rrweb NDJSON is stored in the regional S3 bucket. Replay URLs presign against the same region.
• Profile storageState — cookies and localStorage live in the region the profile was created in.

What is global

• API keys — one key works against every region. No per-region rotation.
• Organizations & billing — a single org spans regions; usage rolls up to one invoice.
• Concurrent-session limits — your plan's concurrency cap is shared across regions. 10 concurrent browsers means 10 total, not 10 per region.
• Console & dashboard — one URL, console.solaribrowser.com, shows sessions from every region with a region column.

Latency expectations

Each region's gateway and pool live in the same AWS region, so the gateway → pool hop is sub-millisecond. The dominant latency component is your network to the gateway. As a rough guide for session.create() + first page.goto():

• Same-region client (e.g. AWS us-west-1 workload → region: "us-west"): 200-400ms.
• Cross-coast client (e.g. AWS us-east-1 workload → region: "us-west"): add 60-80ms per round-trip. Two round-trips on session create + connect.
• Cross-continent client: add 120-200ms per round-trip. The us-east region (when GA) will close most of this gap for European workloads via AWS's east-coast peering.