> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sidecardata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sidecar Docs

> Get started with Sidecar by connecting your data stack

## What is Sidecar?

Sidecar is a data catalog that connects to your entire data stack — dbt, Snowflake, BigQuery, Looker, and more — to give your team a unified view of your data assets, lineage, and metadata.

## Connect Your Data Stack

Each integration guide walks you through setup step by step.

<CardGroup cols={2}>
  <Card title="Context Garage" icon="warehouse" href="/products/context-garage/key-concepts">
    Create, version, and serve semantic context for analytics and AI tools
  </Card>

  <Card title="Agent Console" icon="terminal" href="/products/agent-console/overview">
    Run autonomous agents like Builder against your repositories, with
    human-approved delivery
  </Card>

  <Card title="Data Warehouses" icon="database" href="/integrations/data-warehouses/snowflake">
    Connect Snowflake, BigQuery, Redshift, or Databricks
  </Card>

  <Card title="Transformation" icon="code" href="/integrations/transformation/dbt-cloud">
    Connect dbt Cloud or dbt Core
  </Card>

  <Card title="BI & Analytics" icon="chart-bar" href="/integrations/bi-analytics/looker">
    Connect Looker, Metabase, Lightdash, Omni, or Power BI
  </Card>

  <Card title="Extract & Load" icon="arrows-rotate" href="/integrations/extract-load/fivetran">
    Connect Fivetran
  </Card>

  <Card title="Communication" icon="comments" href="/integrations/communication/slack">
    Connect Slack or Microsoft Teams
  </Card>

  <Card title="Project Management" icon="list-check" href="/integrations/project-management/jira">
    Connect Jira or Linear
  </Card>
</CardGroup>

## Metadata-Only Access

By default, Sidecar operates in a metadata-only mode. This means Sidecar does not query or access the underlying data in your warehouse. Instead, we work with metadata about your stack, such as:

* Table and column names
* Schema structure
* Lineage and dependencies
* dbt metadata
* Query history metadata
* Operational signals and usage patterns

Our goal is to build context about how your data platform works without requiring access to the data itself.

### Exceptions

The primary exception is optional automated dbt test generation. If enabled, Sidecar may query limited warehouse data in order to automatically generate and validate common dbt tests, including:

* Primary key tests
* Not null tests
* Unique tests
* Accepted values tests

This functionality is optional and can be disabled at any time.

### Business Context Integrations

Sidecar can also integrate with tools like Slack and Jira. These integrations help enrich the context layer with institutional and business knowledge that typically does not exist in metadata alone.

In some cases, Slack may also be used purely for operational notifications and alert delivery. In those scenarios, Sidecar does not need to ingest Slack conversation history or message content.

When enabled for contextual enrichment, data from these systems is used solely to improve discovery, lineage understanding, operational awareness, and AI-assisted workflows within Sidecar. These context-enrichment capabilities can be disabled if preferred.

## Need Help?

If you run into any issues during setup, reach out to us at [support@sidecardata.com](mailto:support@sidecardata.com) or via your dedicated Slack channel.