> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/running-tests/parallel-mode.md).

# Parallel runs

Run BugBug cloud tests in parallel: how parallel runs work, the organization limit shared by all projects, turning on parallel runs in a suite, the queue, buying more parallel runs, and making tests s

Parallel runs let more than one test run [in the cloud](/running-tests/in-cloud-on-server.md) at the same time, so a suite finishes much faster. With 8 parallel runs, a suite of 40 tests runs up to 8 times faster than one test at a time.

{% hint style="info" %}
**In short**

* Every paid plan runs **1 cloud test at a time**. Buy extra parallel runs to run more at once: up to 32 yourself, more through support.
* The number is for the whole **organization**, shared by all its projects, suites, schedules and API or CLI runs.
* Turn on **Parallel cloud runs** in a suite to run its tests in parallel. It's off for new suites.
* Only cloud runs can be parallel. Local runs in your browser run one test at a time.
* Tests that run at the same time must not depend on each other. See [Independent tests](/creating-tests/independent-tests.md).
  {% endhint %}

## How parallel runs work

* **One limit per organization.** Your plan includes 1 cloud test at a time. Each extra parallel run you buy lets one more test run at the same moment. The limit is shared by every cloud run in the [organization](/collaboration/organization-settings.md#what-are-organizations): all projects, suites, [schedules](/running-tests/schedules.md), and runs started from the [CLI](/integrations/cli.md), [Public API](/integrations/public-api.md) or [MCP](/ai-testing/mcp.md).
* **Other tests wait in the queue.** When all parallel runs are busy, the next tests are queued and start as soon as a slot is free. An organization can have up to 1000 tests queued or running at once.
* **A test can wait too long.** If a test can't start for too long because all slots are taken, it fails with a message that it waited too long in the queue. Buy more parallel runs or spread your schedules over time.
* **Local runs are never parallel.** In your own browser, a suite runs its tests one by one, because all incognito windows share cookies and storage.

## Run a suite in parallel

1. Go to **Suites** and open or create a suite.
2. Turn on **Parallel cloud runs**.
3. Save the suite.

![Parallel cloud runs option in suite settings](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FLWiceSCVQhGi8kvZrnUe%2Fimage.png?alt=media\&token=03b1471e-b2b1-42b5-a5cb-3a9b75c41366)

When the suite runs in the cloud, its tests start in parallel, up to your organization's limit. The suite shows **Parallel Cloud (Nx)**, where N is the number of tests that can run at the same time. With **Parallel cloud runs** off, the suite's tests run one after another, even if you have more parallel runs.

## Buy more parallel runs

You can buy parallel runs on all paid plans, in the **Subscription** tab of the organization settings or when you choose a plan:

1. Click **Upgrade parallel runs**.
2. Choose how many parallel runs you need.
3. Check the price in the order summary and confirm.

You can also lower the number of parallel runs; the current number stays until the end of the billing period.

You can buy up to 32 parallel runs yourself. If you need more, contact BugBug support at <support@bugbug.io>.

### Parallel runs pricing

Each additional parallel run costs **$80/month** on a monthly subscription. On an annual plan, you get a **15% discount** on this price. See the current prices on the [pricing page](https://bugbug.io/pricing/).

**CORE** plan pricing with extra parallels

<table><thead><tr><th width="212">Number of parallel test runs</th><th width="70">-</th><th width="73">2</th><th width="78">4</th><th width="87">8</th><th width="94">16</th><th>32</th></tr></thead><tbody><tr><td>Billed monthly</td><td>$119</td><td>$199</td><td>$359</td><td>$679</td><td>$1,319</td><td>$2,599</td></tr><tr><td>Billed yearly</td><td>$99</td><td>$167</td><td>$303</td><td>$575</td><td>$1,119</td><td>$2,207</td></tr></tbody></table>

**PRO** plan pricing with extra parallels

<table><thead><tr><th width="212">Number of parallel test runs</th><th width="70">-</th><th width="73">2</th><th width="78">4</th><th width="87">8</th><th width="94">16</th><th>32</th></tr></thead><tbody><tr><td>Billed monthly</td><td>$219</td><td>$299</td><td>$459</td><td>$779</td><td>$1,419</td><td>$2,699</td></tr><tr><td>Billed yearly</td><td>$189</td><td>$257</td><td>$393</td><td>$665</td><td>$1,209</td><td>$2,297</td></tr></tbody></table>

**BUSINESS** plan pricing with extra parallels

<table><thead><tr><th width="212">Number of parallel test runs</th><th width="70">-</th><th width="73">2</th><th width="78">4</th><th width="87">8</th><th width="94">16</th><th>32</th></tr></thead><tbody><tr><td>Billed monthly</td><td>$659</td><td>$739</td><td>$899</td><td>$1,219</td><td>$1,859</td><td>$3,139</td></tr><tr><td>Billed yearly</td><td>$559</td><td>$627</td><td>$763</td><td>$1,035</td><td>$1,579</td><td>$2,667</td></tr></tbody></table>

## Make tests safe to run in parallel

Tests that run at the same time can get in each other's way. Make each test [independent](/creating-tests/independent-tests.md):

* Don't let one test depend on data created by another test.
* Use unique data in every run, for example `{{testRunId}}` in emails and names. See [built-in variables](/editing-tests/variables.md#use-built-in-variables-for-dynamic-or-random-values) and the [Testing Inbox](/editing-tests/testing-inbox.md).
* Don't use one user account in tests that change its settings at the same time.

## FAQ

<details>

<summary>How many tests can I run at the same time?</summary>

1 on every paid plan, plus the parallel runs you buy. You can buy up to 32 yourself; for more, contact <support@bugbug.io>. The number is for the whole organization.

</details>

<details>

<summary>Why do my tests run one by one even though I bought parallel runs?</summary>

Check that **Parallel cloud runs** is on in the suite, and that the suite runs in the cloud. Also check whether other cloud runs in your organization, for example schedules, are using the parallel runs at the same moment.

</details>

<details>

<summary>Do parallel runs work in local runs?</summary>

No. Local runs in your browser always run one test at a time.

</details>

<details>

<summary>Are parallel runs per project?</summary>

No. They're per organization, shared by all projects.

</details>

<details>

<summary>What happens when more tests start than I have parallel runs?</summary>

The extra tests wait in the queue and start when a slot is free. A test that waits too long fails with a queue time message.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugbug.io/running-tests/parallel-mode.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
