Billing, limits & error reference
Browser fleets use the same billing, quota, and lifecycle rules as browser tests. There is no separate fleet plan and no new meter.
How fleets are billed
Section titled “How fleets are billed”MaxoPerf meters a fleet exactly like a browser load test: one running browser = one browser-class virtual user, per location, per minute, drawn from your plan’s VU-hours.
- You pay for browsers that are allocated and running, per location, for as long as the fleet holds them. It does not matter whether a session is driving a browser at that moment.
- Metering starts when a browser becomes ready and stops when MaxoPerf releases it (fleet deleted, idle timeout, or TTL reached).
- Fleet minutes and browser-test minutes draw from the same VU-hours pool. A fleet adds no new line item, and MaxoPerf never counts it twice against a browser test.
Every setting that decides what a fleet costs sits on the create form, so you see the shape of the request before you submit it:
Packing: browsersPerRunner
Section titled “Packing: browsersPerRunner”browsersPerRunner sets how many browsers share a runner. It is the fleet version of “virtual users per runner” on test create. It does not change your bill (billing is per browser, per location). It changes the video layout and the runner count:
1→ each session runs alone with a full-screen video.> 1→ MaxoPerf tiles browsers on a runner, each with its own tile view.
The default comes from your plan’s browser policy, and MaxoPerf clamps the value to your tier’s minimum and maximum, as it does on test create.
Limits & timeouts
Section titled “Limits & timeouts”| Limit | Default | Notes |
|---|---|---|
| Session idle timeout | 300 s | MaxoPerf closes a single WebDriver / Playwright session with no activity. Start a new session to continue. |
| Fleet idle timeout | 15 min | A fleet with no active sessions releases all its browsers and stops billing. Set it per fleet with idleTimeoutMinutes. |
| Fleet TTL (lifetime) | 120 min | Hard cap on how long a fleet lives, active or not. Set it per fleet with ttlMinutes. |
| Maximum TTL | 480 min | Ceiling on ttlMinutes. MaxoPerf clamps requests above it. |
| Browser counts / concurrency | plan-dependent | Your plan’s browser-VU quota gates the total browser count, the same as for browser tests. |
Error reference
Section titled “Error reference”The gateway returns errors in each protocol’s own format, so your existing client handles them as usual.
| Situation | Response |
|---|---|
| Missing or invalid credentials (WebDriver) | 401 Unauthorized with a WWW-Authenticate: Basic challenge |
| Missing or invalid token (Playwright / CDP) | WebSocket connection closed / rejected |
| Explicit Playwright version not supported | HTTP 428 with a JSON body listing the supported minors |
| Unknown or already-ended session | W3C invalid session id error |
| No free browser after the queue wait (~60 s) | W3C session not created error |
| Fleet has ended (TTL, idle, or deleted) | 410 Gone on every endpoint |
| Plan / quota limit hit on create | 402 Payment Required |
| Adding browsers to a running fleet would exceed the plan’s concurrent-VU limit | 403 Forbidden (limit_live_concurrent_vus). In the console, saving the Configuration tab opens the upgrade dialog and nothing is added |
| Starting a fleet would exceed the plan’s concurrent-VU or duration limit | 403 Forbidden. The fleet stays stopped; in the console, Start opens the upgrade dialog |
See also
Section titled “See also”- Browser fleets overview: endpoints, auth, and the capability matrix.
- Connect a client: endpoint and credential reference for every protocol.
- Playwright quickstart: version matching and CDP.
- Selenium quickstart: Python / Java / JS and the REST create call.
- Billing: how VU-hours and plan tiers work across MaxoPerf.