> For the complete documentation index, see [llms.txt](https://docs.bravostudio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bravostudio.app/good-to-know/billing/app-add-ons.md).

# App Add-ons

### How to add an Advanced app  or Business app add-on

Advanced app and Business app add-ons are available if you are on the Bravo Solo plan. Each add-on is applied to only one app.

To upgrade an app to an Advanced app or Business app , click the **Upgrade app** button at the top of the screen within the app project. This will result in a confirmation pop-up. If you confirm, the app subscription will be added to your billing cycle prorated.

The add-on billing cycle will follow your Bravo Solo plan billing cycle, meaning if you have a yearly Bravo Solo billing cycle and then adds a Advanced app add-on, the Advanced app will also be a yearly billing.

![](https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXpqEanvOhm8vMtIH8i%2Fuploads%2FzzzFVIhgQ1h2gRp7VxnJ%2FScreenshot%202023-04-24%20at%2017.07.07.png?alt=media\&token=ba0dbee3-6685-4f0a-8d64-e834a38aebcc)

{% hint style="warning" %}
The add-ons are currently not supported if you have subscribed to Bravo Solo with Apple subscription on your iOS device. Please contact <mark style="color:blue;">`billing@bravostudio.app`</mark> for more information.<br>
{% 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.bravostudio.app/good-to-know/billing/app-add-ons.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.
