> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/storage-and-transfer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccv.brown.edu/storage-and-transfer/campus-file-storage/quotas-and-billing.md).

# Quotas and Billing

Campus file storage implements quotas for several critical management and organizational reasons. Every research lab or department starts with a standard baseline allocation of 1 TiB. If your research or administrative needs exceed this baseline, we offer scalable options to accommodate your growth.

## Research Quotas

Each researcher (PI) gets **1 TiB** of free allocation to use across all storage platforms managed by OIT-Storage. ***Researchers are also eligible for an additional 10 TiB replicated storage or 20 TiB non-replicated storage per active grant.***

Any data usage beyond free or grant-based allocations will be charged at the following rates:

* **Replicated Storage: $100/TiB/Yr**
* **Non-Replicated Storage: $50/TiB/Yr**

For more information about quotas, rates, and pooled storage allocations, please visit the [CCV Rates ](https://ccv.brown.edu/services/rates)page.


---

# 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.ccv.brown.edu/storage-and-transfer/campus-file-storage/quotas-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.