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

# Welcome to Sled

The All-In-Once Data Governance Solution for Snowflake

Sled helps you to find, understand and trust your analytics. We build it for the Snowflake data cloud, because we believe deep integration enables better workflows and allows us to double down on hard platform specific challenges.

Sled has two engines: one for metadata, one for metrics. Both work hand in hand to make your analytics scalable and trustworthy.

**Data Catalog and Observability - it's meta data management!**

* Search everything, from columns in Snowflake to dashboards in Tableau
* Discover and observe your data with data profiles
* Document your data and visualization assets
* Understand data flows down to to the column level (Lineage)
* View access rights and manage ownership of your assets

**Metric Store - Define once, use everywhere.**

* All Calculations should live in one place, your data warehouse.
* Define metrics once and consume them with SQL in any other tool.
* Discover and document your metrics in the catalog.

![](https://2457798860-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEdkjXblQVFxdE5uvkTZt%2Fuploads%2FbFoSIu00GBeKqLTerJzq%2Foverview_architecture.png?alt=media\&token=3d77e0bd-10d9-4045-808e-1411817245df)

Sled connects directly with your cloud data warehouse. It needs access to the system database and tables of the warehouse (e.g. in `SNOWFLAKE.ACCOUNT_USAGE`). The metadata engine also connects to dbt cloud, Tableau cloud and PowerBI.


---

# 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.sled.so/readme.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.