# Get started

Short tutorials take you from nothing to a suite that runs itself and tells you when
something breaks. Each one ends with something you can see on screen.

<div class="grid cards" markdown>

-   :material-download:{ .lg .middle } **Install**

    ---

    Run DataQ locally with Docker in about five minutes. No cloud account, no identity
    provider — sign in with an emailed code.

    [:octicons-arrow-right-24: Install](install.md)

-   :material-play-circle:{ .lg .middle } **Your first suite**

    ---

    Connect a datasource, author two checks, run them, and read the result.

    [:octicons-arrow-right-24: First suite](first-suite.md)

-   :material-bell-ring:{ .lg .middle } **Your first alert**

    ---

    Route a suite's breaches to Teams, Slack or email, prove it fires, and see why it stays
    quiet afterwards.

    [:octicons-arrow-right-24: First alert](first-alert.md)

-   :material-play-speed:{ .lg .middle } **Run it automatically**

    ---

    Trigger the suite when your ADF, Airflow or dbt pipeline succeeds, or put it on a cron.

    [:octicons-arrow-right-24: Automate](connect-pipeline.md)

-   :material-robot:{ .lg .middle } **Ask an AI assistant**

    ---

    Mint a token, point Claude, Copilot or Cursor at `/mcp`, ask the four questions.

    [:octicons-arrow-right-24: Ask an assistant](ask-assistant.md)

-   :material-lightbulb-on:{ .lg .middle } **Concepts**

    ---

    The six words you need — connection, suite, check, run, result, incident — and how
    they fit together.

    [:octicons-arrow-right-24: Concepts](concepts.md)

</div>

## Where next

The [Guides](../guides/index.md) go deeper on each of these; the
[Reference](../reference/index.md) lists every check type, endpoint and tool.