> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/object-storage/details/quota-and-regions.md).

# Quota and Regions

Quota is the space you reserve in the repository, and the region is where it is hosted. You define both when activating the service, and they determine capacity and data location.

### Quota

> #### 🚧 Range to be confirmed
>
> The quota is configurable. The product material points to an approximate range of 100 GB to 20 TB.
>
> We confirm the current minimum and maximum with the current platform before publishing the figure.

You increase the quota as the customer's volume grows, without recreating the repository.

### Regions

The region determines where the data resides, which is key for sovereignty and compliance requirements.

> #### 🚧 Regions to be confirmed
>
> The material points to regions in Madrid, Paris, and Querétaro.
>
> We confirm the regions currently available before publishing them.

### Where to follow

* The why of the product and its use cases: ¿[What is Object Storage?.](https://docs.plenit.com/docs-en/productos/object-storage/concepts/what-it-is.md)
* How data is protected and where it is replicated: [Resilience, encryption, and compliance.](https://docs.plenit.com/docs-en/productos/object-storage/details/encryption-and-compliance.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.plenit.com/docs-en/productos/object-storage/details/quota-and-regions.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.
