> 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/in-cloud-on-server.md).

# Run in cloud

Discover how to run tests in the cloud or on your server with BugBug's comprehensive guide. Improve your testing efficiency and scalability today.

### Why run in the cloud?

Thanks to running in the cloud, you don't need to use your computer to monitor your website for bugs.

Running in the cloud is required for

* [scheduling tests](/running-tests/schedules.md)
* integrating with build pipelines ([running via CLI](/running-tests/running-via-api.md))
* making use of [parallel runs](/running-tests/parallel-mode.md)

### How to run in the cloud?

1. Go to test view and choose `Run in cloud`option on the right.
2. Then you will use BugBug cloud for your test run:
3. You will not see any window for cloud runs, just observe the status of the test steps

Now that your tests pass in the cloud, you can [set up a schedule to automatically run them every hour](/running-tests/schedules.md).

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FhbPFg3yk32Ft0T59i4ey%2Fimage.png?alt=media\&token=5a7fa9a4-fecc-44f7-abb2-f0e359995905)

{% hint style="info" %}
**Important!** You can't run tests in the cloud on a FREE plan. Start a free trial or upgrade your plan to "PRO" - see [pricing](https://bugbug.io/pricing/).
{% endhint %}


---

# 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/in-cloud-on-server.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.