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

# Quickstart

> Run Lookout from source and query the local HTTP interface.

> For the complete documentation index, see [llms.txt](https://devlookout.com/llms.txt). Markdown versions are available by appending `.md` to page URLs.

This path starts a development instance bound to `127.0.0.1:4173`. Use the automated installer for a production deployment.

## Prerequisites

* Node.js 20 or later
* npm
* Access to the private Lookout repository

<Steps>
  <Step title="Install dependencies">
    From the repository root:

    ```sh theme={null}
    npm ci
    ```
  </Step>

  <Step title="Validate the configuration">
    The example is safe for loopback-only development and stores state outside the `config` directory.

    ```sh theme={null}
    LOOKOUT_CONFIG=./config/lookout.example.json \
      node bin/lookout.js config-check
    ```
  </Step>

  <Step title="Start Lookout">
    ```sh theme={null}
    LOOKOUT_CONFIG=./config/lookout.example.json npm start
    ```

    Open `http://127.0.0.1:4173` to view the local console.
  </Step>

  <Step title="Verify health">
    In another terminal:

    ```sh theme={null}
    curl --fail --silent http://127.0.0.1:4173/health | jq
    ```

    The unauthenticated health response contains aggregate runtime state, not event or graph contents.
  </Step>

  <Step title="Query the graph">
    The example configuration permits loopback requests to act as local admin:

    ```sh theme={null}
    curl --fail --silent http://127.0.0.1:4173/api/v1/graph | jq
    ```
  </Step>
</Steps>

<Warning>
  Do not use `npm start` as a production installation. It does not provision service accounts, private TLS, encrypted storage, signed collectors, or systemd hardening.
</Warning>

## Next steps

<CardGroup cols={2}>
  <Card title="Configure Lookout" icon="sliders" href="/configuration">
    Set storage, collectors, exports, and webhooks.
  </Card>

  <Card title="Explore the HTTP interface" icon="code" href="/reference/overview">
    Send authenticated requests and inspect available resources.
  </Card>
</CardGroup>
