> 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/file-storage/concepts/quota-and-backups.md).

# Quota and backups

### Quota: the space you purchase

You choose the subscription quota based on what the client needs, and expand it as it grows. To avoid surprises with usage, you set threshold alerts.

| Usage alert | What for                        |
| ----------- | ------------------------------- |
| 80%         | Start planning the expansion    |
| 90%         | Act before you run out of space |
| 95%         | Minimum margin, expand now      |

> #### 📘 Set the alerts when you sign up
>
> Space always runs out at the worst moment. 
>
> Setting the thresholds from the start turns an urgent problem into a calm alert with time to react.

### Backups included

Backups are included by default, with no setup needed, with this retention:

| Frequency  | Kept             |
| ---------- | ---------------- |
| Every hour | The last 5 hours |
| Daily      | 14 days          |
| Weekly     | 8 weeks          |

This protects you against accidental deletions, file corruption, and ransomware scenarios: you go back to a copy from before the problem. Restoration is simple and you do it when you need it.

> #### 👍 Protection is not an add-on
>
> In many consumer services, backups are paid for separately or don't exist. 
>
> Here it's included, and it's a solid argument when you explain to a customer why this storage is enterprise-grade.

### Where to go next

* What the service is and what sets it apart: [What is File Storage?](/docs-en/productos/file-storage/concepts/what-it-is.md)
* Who has access to the data: [Users, groups, and permissions.](/docs-en/productos/file-storage/concepts/users-groups-and-permissions.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.plenit.com/docs-en/productos/file-storage/concepts/quota-and-backups.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.