> 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/how-to-subscribe.md).

# Upgrading a plan

### Upgrade to Bravo Solo plan

If you are on the Bravo Starter plan, you can go to the [pricing page](https://www.bravostudio.app/pricing) and upgrade to Bravo Solo. You can choose between the monthly or yearly subscription.

{% hint style="info" %}
The add-on apps billing cycle will follow your Bravo Solo billing cycle, meaning if you have a yearly Bravo Solo billing cycle and then adds an Advanced app upgrade, the Advanced app will also be a yearly billing.
{% endhint %}

If it’s your first time upgrading to Bravo Solo, you will have a 7-day free trial after you sign up and before your billing cycle starts. If you have been on the Bravo Solo plan before, your billing cycle will begin immediately after you upgrade.

**Didn't answer your question? 🧐**

Let us know in [our Community](https://community.bravostudio.app/) so we can further help you!


---

# 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/how-to-subscribe.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.