> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/release-instant-datasets/faq.md).

# FAQ

## Does Release have access to my production data?

No. Release follows the principle of least privilege and only requires a minimal role on your cloud account for managing and checking out database snapshots. Release has no need to touch your data, and your data never leaves your cloud account.

## How do I integrate Instant Datasets into our developers' local development workflow?

Instant Datasets functionality is available through [REST APIs](https://api.release.com/api-docs/) that you can use to integrate into your tooling.

## Which cloud platforms do you currently support?

We currently support AWS. GCP support will be coming soon.

## Which databases do you currently support?

We currently support Amazon RDS and Aurora (MySQL and PostgreSQL). CloudSQL support will be coming soon.

## How much does Instant Datasets cost?

Instant Datasets is currently in beta and will be free during the beta period.


---

# 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.release.com/release-instant-datasets/faq.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.
