> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/getting-started/what-is-shade.md).

# What is Shade

**Shade is an AI-powered media storage and collaboration platform that transforms how creative teams manage, search, and collaborate on media assets.**

We provide cloud storage with local file access, natural language search, and asset review, all in one unified platform.

### Our Vision: The CRM for Your File System

Companies today have files sprawled across 6-7 different tools and systems: stored on hard drives, cloud platforms, and everywhere in between. This fragmentation creates chaos, slows down workflows, and makes it nearly impossible to find what you need when you need it.

Shade is building the solution: **a unified file system that acts like a CRM for all your assets.**

We build both:

* **The file system layer**: Centralized storage that brings everything together
* **The workflow layer**: Tools to work, search, share, and automate files across your entire business

Instead of jumping between Dropbox, Google Drive, external hard drives, and server storage, Shade gives your team one intelligent platform where every file is accessible, searchable, and actionable.


---

# 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://academy.shade.inc/getting-started/what-is-shade.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.
