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

# Analytics overview

> Long-term data storage and analytics visibility for your organization.

Analytics is Lambda's long-term data store for analytics visibility. Your organization gets a dedicated Postgres database you can query with SQL, Power BI, or any Postgres client — for dashboards, recurring reports, and historical analysis.

You connect with a normal host, port, username, and password from Lambda. Day-to-day reporting does not need a custom API.

## What you get

* Long-term storage scoped to your organization
* A stable schema named `reporting`
* Curated business tables for everyday questions
* A discovery path for fields that are not yet curated columns
* Credentials you create, rotate, and revoke in Lambda

## Who this is for

Most report consumers never open SQL. Someone on your team connects Power BI once, publishes a model, and everyone else uses reports.

People who already use a database client can connect with the same credentials and run read-only queries against `reporting`.

## Start here

<CardGroup cols={2}>
  <Card title="How it works" icon="diagram-project" href="/analytics/how-it-works">
    Long-term storage, curated tables, and field discovery.
  </Card>

  <Card title="Connect" icon="plug" href="/analytics/connect">
    Create credentials and open Power BI or any Postgres client.
  </Card>

  <Card title="Query curated data" icon="table" href="/analytics/curated-data">
    Everyday tables such as `reporting.shipments`.
  </Card>

  <Card title="Discover fields" icon="magnifying-glass" href="/analytics/discover-fields">
    Find values that are not curated columns yet.
  </Card>

  <Card title="Power BI" icon="chart-simple" href="/analytics/power-bi">
    Build and publish a durable reporting model.
  </Card>

  <Card title="Reporting views" icon="book" href="/analytics/reporting-views">
    Full list of views, columns, and known gaps.
  </Card>
</CardGroup>
