Regions

Pick where your browsers run. Your sessions, replays, and saved profiles all live in the region you choose, so picking the one closest to your work keeps everything feeling fast.

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 "@solarisdk/browser"

const client = new Solari({
  apiKey: process.env.SOLARI_API_KEY!,
  baseUrl: "https://api.getsolari.com",
  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 lives in the region you pick

• Browser sessions: your browser always runs in the region you picked.
• Session replays: recordings of your sessions are stored in that region.
• Saved profiles: cookies and site data stay in the region where you created the profile.

What is shared everywhere

• API keys: one key works in every region. No per-region setup.
• Organizations & billing: one account covers every region, and usage adds up to a single invoice.
• Session limits: the number of browsers you can run at once is shared across regions. 10 at once means 10 total, not 10 per region.
• Console & dashboard: one place, console.getsolari.com, shows your sessions from every region, with a column telling you which region each one is in.

What to expect for speed

The biggest thing that affects speed is how far you are from the region you picked. As a rough guide for creating a session and loading a first page:

• Close to the region (for example, running in US West with region: "us-west"): 200-400ms.
• Across the country (for example, running in US East with region: "us-west"): add roughly 60-80ms each way.
• Across an ocean: add roughly 120-200ms each way.