> 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/hibernate/starfish.md).

# Starfish

Starfish is a software application for managing files and objects at any scale. Starfish enables users to view all their storage allocations across multiple platforms in a single view and to participate in storage management and content classification.

Some of the key features of Starfish are

* Metadata and content classification
* Reporting and analytics
* Data usage insights
  * Types/sizes of files, access times
  * Hot Spots (Growth, user(s)/Group(s)
* Data migration
* Archive and recovery

Starfish uses 'zones' to facilitate researchers with their own unique view of storage. A 'zone' combines storage owned by a researcher on different storage platforms providing a holistic view. So, to begin using Hibernate service, a PI/researcher should request a [zone](broken://pages/-MkIHyEy2ioVrfcSKznN) that also provides access to the Starfish tool.

Today, the Starfish tool can provide insight into the following storage platforms:

* files22.brown.edu
* files.brown.edu
* lrs.brown.edu
* oscar
* nfs\*.brown.edu


---

# 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/hibernate/starfish.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.