> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/pricing/reasons-to-buy-premium-plan.md).

# Reasons to buy premium plan

### Why should I buy the premium plan?

The premium plan is the top tier in our Pay-per-app and Unlimited Workspaces offerings. Compared to Starter and Pro plans, the Premium plan has several additional features. Some of the features which are only part of the Premium plan –

* Analytics
* Easy publish
* Customer chat
* In-app purchases
* Rich push notifications
* Merge apps
* Language selection&#x20;

Any new feature introduced on a Pay-per-app level is guaranteed to be part of our Premium plan. By choosing the Premium plan, you can thus ensure you always have access to AppMySite’s latest features.


---

# 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.appmysite.com/pricing/reasons-to-buy-premium-plan.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.
