> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/warehouse/connect-your-warehouse.md).

# Connect your Warehouse

## **Why connecting your warehouse to** [**Whaly**](https://whaly.io)**?**

In order to use Whaly you have to connect a database that is commonly called a data warehouse. A data warehouse is **a central repository of information that can be analyzed to make more informed decisions**. Data flows into a data warehouse from transactional systems, relational databases, and other sources, typically on a regular cadence.

Connecting a Whaly to a warehouse ensures:

* Your data is stored on your own premise and that you control what Whaly has access to
* Your data is centralized in one database allowing you to "join" multiple sources
* Your data is observable so you can connect to your own warehouse and see exactly how it is stored

## How is the warehouse connection working?

When connecting Whaly to your warehouse, we ensure that the connection to your warehouse is the most secured based on the driver you are using. As of today Whaly supports two drivers, [BigQuery](/warehouse/google-bigquery.md) and [Snowflake](/warehouse/snowflake.md). 


---

# 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.whaly.io/warehouse/connect-your-warehouse.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.