> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/faq/c142/c149/q430.md).

# How do I start a trial to test the app?

Trials are available for new users when you subscribe.

**Report and Run: Cloud**

* You can [subscribe from the Report and Run: Cloud web portal](broken://pages/rm64ei3LPmRFan8MMDM0) or from [the mobile app](/manual/report-and-run-integrate/quick-start-guide/subscribe.md). You will see if you qualify for a 30-day trial at checkout.
* Please note that trials are only available for the monthly renewing subscription. Pre-paid months or years do not include a trial.

**Report and Run: Offline (paid tier)**

* You can [subscribe from within the app](/manual/report-and-run/subscription/how-to-subscribe.md) and you will see if you qualify for a 30-day trial at checkout.

**Report and Run: Offline Team**

* [Contact us](/manual/faq/c169/q575.md) with your company email address and the number of users that you would like to have in your account and we can set up a trial.

## Related

* [FAQ: How do I get started with the offline version?](/manual/faq/c142/c144/q395.md)
* [FAQ: How do I get started with a cloud account?](/manual/faq/c142/c144/q394.md)
* [FAQ: Can I use the app for free?](/manual/faq/c142/c149/q427.md)


---

# 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.reportandrun.com/manual/faq/c142/c149/q430.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.