Concurrent Browsers

Concurrent Browsers represent the total number of browser profiles running simultaneously, including both automated profiles (Selenium, Playwright, Puppeteer) and manual profiles.

For example: Running 2 automated and 2 manual browsers counts as 4 concurrent browsers total.

Monitor Concurrent Browser usage

Checking your concurrent browser usage is possible through the Local API:

Endpoint: GET /general/user-info

Response includes:

runningUserProfiles: Stats for your email account
runningTeamProfiles: Stats for all team emails
runningTenantProfiles: Stats for tenant level

A value of -1 indicates no limit. Quota updates refresh every 60 seconds.

"runningUserProfiles": {
  "automated": {
    "currentUsage": 0,
    "maximumLimit": -1
  },
  "manual": {
    "currentUsage": 0,
    "maximumLimit": -1
  },
  "total": {
    "currentUsage": 0,
    "maximumLimit": -1
  }
}

Understanding Concurrent Brower Tracking

The following steps can be experienced on your side related to Concurrent Browser counting.

Start Profile

Initiating profile start
Current Concurrent Browser Count is incremented and all CLI instances are informed about new value
Profile actually starts and you can see the browser

Stop Profile

Initiating profile stop
Current Concurrent Browser Count is decremented and all CLI instances are informed about new value
Profile actually stopped

If a CLI instance loses network connectivity, any browsers it started will be automatically released within 130 seconds.

Please note that the number of running browsers you track locally may not always match the actual value maintained by Kameleo. This mismatch can occur if profiles are started and stopped extremely rapidly, especially when operating close to the concurrent browser limit, or when Kameleo is running across multiple nodes. A browser slot becomes locked the moment a profile start request is initiated, not when the browser window actually appears, which can further contribute to differences in locally measured values.