> For the complete documentation index, see [llms.txt](https://help.hippoly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hippoly.com/administration/subscription-and-billing.md).

# Subscription and billing

Your Hippoly subscription determines which features and limits your workspace has access to. You can manage and change your subscription yourself at any time.

{% hint style="info" %}
**Note:** Subscription and billing can only be managed by users with the **Workspace Owner** or **Workspace Administrator** roles.
{% endhint %}

## Understand Subscription and Billing

Hippoly uses a freemium pricing model. This means there is a **Free plan** and several paid plans with additional features and higher limits.

When a user creates a collaboration space in Hippoly, it is automatically placed on the **Free plan**. The Free plan can be used for an unlimited time but includes certain limitations defined by the plan.

If a user wants access to more features or higher limits, they can upgrade the collaboration space to one of the paid plans. All upgrades are managed directly by the user.


---

# 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://help.hippoly.com/administration/subscription-and-billing.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.