> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/concepts/readme.md).

# Overview

These concepts build in one direction: start with **what** you are building and **why**, drop to the **Resources** that build it, reach the result through an **Interface**, and lean on the **Glossary** for the vocabulary the rest assumes. Read top to bottom the first time; jump straight to a card after that.

### Foundations

Start here. Foundations explain what a Data Product is and how it becomes usable, which is the goal everything else serves.

<table data-view="cards"><thead><tr><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Data product</strong><br>Understand Data Products and the core concepts that support them in DataOS.</td><td><a href="/pages/AFboqVCPYoW33qaedGKN">/pages/AFboqVCPYoW33qaedGKN</a></td></tr><tr><td><strong>Activation</strong><br>Learn how Data Products become operational, discoverable, and consumable.</td><td><a href="/pages/FDEqXtEPrBIC5TQmAied">/pages/FDEqXtEPrBIC5TQmAied</a></td></tr></tbody></table>

### Resources

A Data Product is assembled from Resources. These are the declarative building blocks that connect data, run workloads, and manage storage. Each one is a piece of the product Foundations described.

<table data-view="cards"><thead><tr><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Vulcan</strong><br>Build and serve Data Products.</td><td><a href="/pages/8kxn7nvzKnWN4iOPlunf">/pages/8kxn7nvzKnWN4iOPlunf</a></td></tr><tr><td><strong>Nilus</strong><br>Move data through batch, CDC, stream, and metadata pipelines.</td><td><a href="/pages/tgnJOrI6Ndgr5NJ3AZAH">/pages/tgnJOrI6Ndgr5NJ3AZAH</a></td></tr><tr><td><strong>Lakehouse</strong><br>Create and manage open table storage on DataOS.</td><td><a href="/pages/NZyLGgwAs0SzCcaiAibn">/pages/NZyLGgwAs0SzCcaiAibn</a></td></tr><tr><td><strong>Bundle</strong><br>Package related workload assets together.</td><td><a href="/pages/mXRE4GzPtaLJWeKrWtMX">/pages/mXRE4GzPtaLJWeKrWtMX</a></td></tr><tr><td><strong>Minerva</strong><br>Query depots and lakehouse data through a federated SQL engine.</td><td><a href="/pages/Bz5dTXJASJon4jPyKDHB">/pages/Bz5dTXJASJon4jPyKDHB</a></td></tr><tr><td><strong>Secret</strong><br>Store credentials and sensitive configuration securely.</td><td><a href="/pages/WFEOO598InFQXIz97VZ0">/pages/WFEOO598InFQXIz97VZ0</a></td></tr><tr><td><strong>Depot</strong><br>Connect external data sources to DataOS without moving data.</td><td><a href="/pages/y3BG59lGs0vGcPkiXDCP">/pages/y3BG59lGs0vGcPkiXDCP</a></td></tr></tbody></table>

### Interfaces

Once a Data Product is built using Resources, you reach it through an Interface. These are the ways you and your tools interact with DataOS.

<table data-view="cards"><thead><tr><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>CLI</strong><br>Manage DataOS Resources from the command line.</td><td><a href="/pages/vbrrNFRZkwno4rgL33eO">/pages/vbrrNFRZkwno4rgL33eO</a></td></tr></tbody></table>

### Glossary

Every section above leans on the same vocabulary. The Glossary defines those terms once, so a word like Tenant or Depot means the same thing on every page.

<table data-view="cards"><thead><tr><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Glossary</strong><br>Look up platform terms and shared definitions.</td><td><a href="/pages/K5hyxvDOHX7umfQXj6pP">/pages/K5hyxvDOHX7umfQXj6pP</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/concepts/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.