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

# Quickstart

> Go from signup to driving real hardware from your browser in about ten minutes.

This walkthrough assumes you already have at least one Lager box reachable over the network (whether on your LAN, a VPN, or Tailscale). If you don't yet, start with the [Lager getting-started docs](https://docs.lagerdata.com/source/getting-started/adding-first-lager-box) and come back when you have `lager hello` working.

## 1. Create your account

Go to [app.stoutdata.ai](https://app.stoutdata.ai) and sign up with your work email. You'll receive a verification link — click it, then sign in.

On first login Stout creates a personal organization for you. You can rename it and invite teammates from **Settings**. Additional organizations are provisioned by a Stout admin — reach out if your team needs a second org.

## 2. Register your first box

From the dashboard, open **Boxes → Add Box**. Give it a name and enter its IP address. Stout will:

1. Generate a one-time setup command you paste onto the box over SSH.
2. Exchange an API key with the box so it can send heartbeats to the control plane.
3. Pull the Stout agent container (`ghcr.io/stoutdata/stout:latest`) onto the box.

Once the heartbeat reaches the control plane, the box shows as **online** in the fleet view. Opening the box detail page reveals the **Overview**, **Nets**, **Webcams**, **Activity**, and **Settings** tabs.

<Note>
  The install flow writes to `/etc/lager/` on the box. Both `/etc/lager` and
  `/etc/lager/authorized_keys.d/` must be mode 777 so the control plane's SSH
  key sync works. See the [Boxes reference](/source/boxes/overview) for
  details.
</Note>

## 3. Drive an instrument

With the box online and at least one [net](/source/concepts/glossary#net) configured (add nets on the box's **Nets** tab, or see the [Lager docs](https://docs.lagerdata.com/source/getting-started/setting-up-instruments)), open **Workbench** from the sidebar:

1. Pick your box from the **Box** selector — only boxes that are online with an IP appear.
2. Expand an instrument to reveal its control panel.
3. Drive it directly: set a power-supply voltage and enable the output, open a UART serial console, or toggle a GPIO.

That's the fastest way to confirm end-to-end control from your browser all the way down to the bench. See the [Workbench reference](/source/workbench/overview) for every instrument type it supports.

## 4. Make it repeatable

Hands-on control is great for bring-up and debugging. When you want the same checks to run the same way every time — on a production line or in QA — move them into a [Factory suite](/source/factory/overview): a scripted sequence with structured pass/fail steps, optional camera capture, and a downloadable report per run.

## 5. What's next

<CardGroup cols={2}>
  <Card title="Invite teammates" href="/source/organizations/overview">
    Add members, create teams, and control which boxes each person can access.
  </Card>

  <Card title="Run a Factory suite" href="/source/factory/overview">
    Structured, repeatable pass/fail hardware tests for production and QA.
  </Card>

  <Card title="Check PRs on hardware" href="/source/integrations/github">
    Have an AI reviewer author and run tests on every pull request. *(Beta.)*
  </Card>

  <Card title="Set up SSO" href="/source/integrations/sso">
    Sign your team in through OIDC or SAML.
  </Card>
</CardGroup>