> 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/help-center/general-faq/when-to-use-shade-cloud.md). # When to use Shade Cloud Shade Cloud is storage that Shade hosts and manages for your drives. You get everything Shade and its drives can do without managing any storage infrastructure yourself. You pay Shade for the storage and its management. ### Unify your files in one place One of Shade's biggest benefits is bringing scattered, hybrid workflows into one place. You get one app to manage both cloud and self-hosted data, with full search, access, and sharing for all of it, wherever you are. ### AI works better in Shade Cloud In Shade Cloud, Shade can use the full capacity of its cloud and additional AI models, which means faster indexing and richer metadata for cloud drives. ### Teams that share a lot Shade's speed still depends on your internet connection and the distance between you, Shade's servers, and the people you're working with. If your team works remotely across regions or countries, we highly recommend using Shade Cloud as the base for your shared work. ### When Shade Cloud isn't the right fit Consider connecting your own storage instead if: * Your data has to stay in your own cloud account, for compliance, contract, or data residency reasons. * You already pay for storage with a provider such as AWS S3, Wasabi, Backblaze, or Google Cloud Storage and want to keep using it. See [Bring Your Own S3 Storage](https://academy.shade.inc/byos/bring-your-own-s3-storage) to connect it. --- # 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/help-center/general-faq/when-to-use-shade-cloud.md?ask=&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.