> 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/c147/q413.md).

# What are the additional features included in the Report and Run: Offline paid tier?

Report and Run: Offline has built-in trials of most of the features in the upgraded version, so you can test out the paid app before subscribing. The main benefits of upgrading are:

* removing the 8-report-a-month limit
* adding custom branding to the reports
* removing the "generated by Report and Run" footer
* removing the lifetime usage limits on:
  * docx exports
  * image builder (combining multiple images)
  * adding cover pages
  * full page images
  * paragraphs of text
  * text templates (saving and re-using text)

## Related

* [FAQ: How much does the 'upgraded' version of Report and Run: Offline cost?](/manual/faq/c142/c149/q432.md)
* [FAQ: How do I upgrade to the paid tier of Report and Run: Offline?](/manual/faq/c142/c144/q397.md)
* [FAQ: Can you give me an overview of the Report and Run: Offline Team version?](/manual/faq/c142/c145/q398.md)
* [FAQ: What are the differences between the cloud and offline versions of the app?](/manual/faq/c142/c143/q388.md)
* [FAQ: How much does the 'cloud' version of the app cost?](/manual/faq/c142/c149/q431.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/c147/q413.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.