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

# Quickstart

> Evaluate sureops with a demo environment in 5 minutes

The fastest way to understand sureops is to watch it handle a real incident end-to-end. This guide walks you through the demo environment path — a pre-wired environment that comes with a running sample application, connected observability stack, and the ability to trigger incidents on demand.

<Note>
  The demo environment uses a real running application with real telemetry. The AI agents diagnose from actual logs, metrics, and traces — the same way they would on your production stack. There's no simulation.
</Note>

***

<Steps>
  <Step title="Sign up and log in">
    Go to [app.sureops.ai](https://app.sureops.ai) and create your account. If you're in private beta, use the invite link from your onboarding email.

    After logging in, you'll land on the **Onboarding** screen. Select **Evaluate with demo environment** to continue on this path.
  </Step>

  <Step title="Connect your demo environment">
    sureops provisions a demo environment for your account automatically. This environment includes:

    * A sample microservices application (OpenTelemetry-instrumented)
    * Prometheus, Loki, Tempo, and Grafana pre-connected via MCP
    * A Kubernetes cluster with ArgoCD managing deployments
    * GitHub connected for repository context and fix PRs

    The onboarding wizard confirms each integration is healthy. Green checkmarks on all six rows means you're ready. If any integration shows an error, click **Need help?** to open a support thread.
  </Step>

  <Step title="Trigger a demo incident">
    Navigate to **Settings → Environments → Demo** and click **Trigger incident**.

    This injects a real fault into the demo application. Within 30–60 seconds, an alert fires, sureops detects it, and a new incident appears on the **Command Center** dashboard.

    You don't need to do anything — watch the incident card appear and the stage indicator advance in real time.
  </Step>

  <Step title="Follow the incident through the lifecycle">
    Click the incident to open the **Incident Hub**. You'll see:

    * The **triggering alerts** that created the incident
    * The **triage assessment** — severity, affected services, estimated impact
    * The **diagnosis agent** running its investigation (live progress in the agent activity feed)
    * Once diagnosis completes: ranked **recommendations** with evidence and confidence scores

    The demo environment starts in **Supervised mode**, so the AI pauses after diagnosis and waits for your approval before proceeding.
  </Step>

  <Step title="Approve a HITL action">
    When the diagnosis completes, a **Pending Approval** banner appears at the top of the incident hub (and on the Command Center dashboard).

    Review the recommendations — each one shows the proposed action, the risk level, the agent's reasoning, and the evidence it used. When you're ready:

    * Click **Approve** to let sureops execute the fix and continue to verification
    * Click **Reject** to decline and either provide feedback or take manual control

    After approval, the resolution agent executes the fix, verification confirms recovery, and the incident closes automatically with a generated RCA.

    <Note>
      This approval step is the core of **Human-in-the-Loop (HITL)**. In Self-Driving mode with low-risk incidents, this gate can be configured to auto-approve — but it is always present for high-risk actions and P1/P2 severity. See [HITL gates](/next/operating-modes/hitl-gates) for the full policy model.
    </Note>
  </Step>
</Steps>

***

## What to explore next

After your first incident, the demo environment gives you a few more things worth trying:

* **Take Control mid-incident** — click "Take Control" while the diagnosis agent is running. Watch it finish its current operation, hand off findings, and pause. Use the stage chat to ask the agent questions, then release it back to autonomous.
* **Problem Records** — after the incident closes, navigate to **Problems**. A Problem Record was created automatically. This is where recurring pattern tracking and post-closure investigation live.
* **ECHO chat** — open the chat sidebar and ask ECHO about the incident. It has full context from the pipeline and can answer questions about what happened, why the AI made the decisions it did, and what to watch for next.

***

## Ready to connect your own stack?

The demo environment is designed for evaluation. When you're ready to run sureops against your own services and infrastructure, see:

* [Demo vs. Adopt — choosing your path](/next/onboarding/demo-vs-adopt)
* [Adopt — connect your stack](/next/onboarding/adopt-connect-your-stack)
* [Integrations overview](/next/integrations/how-integrations-work)