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

# EvalGate

> CI for AI behavior: capture real AI failures, turn them into eval coverage, and block regressions before release.

# EvalGate: CI for AI behavior

EvalGate helps AI teams stop the same failure from shipping twice. Start with a local regression gate, then add traces, evaluation history, LLM judges, reviews, cost controls, and governance when your AI system reaches production scale.

The product is one operating loop: **trace to eval to gate**. Real behavior produces evidence. Reviewed failures become test cases. Promoted test cases become CI gates that give reviewers evidence before a prompt, model, retriever, or agent change ships.

<Note>
  Model-backed workflows are **bring your own provider key (BYOK)**. EvalGate does not bundle model inference credits: connect your own provider or gateway credential, and that provider bills model usage directly. [Understand BYOK and model-provider setup](/docs/platform/model-providers-byok).
</Note>

<CardGroup cols={2}>
  <Card title="Quick start" icon="bolt" href="/docs/quickstart">
    Copy two commands, create your first baseline, and see a local regression gate fail before it reaches CI.
  </Card>

  <Card title="Trace to eval to gate" icon="route" href="/docs/concepts/trace-eval-gate">
    Understand the operating loop before you wire in platform features.
  </Card>

  <Card title="SDK and CLI" icon="code" href="/docs/sdk/typescript">
    Install the TypeScript or Python SDK and use the same assertions locally, in app code, and in CI.
  </Card>

  <Card title="Framework recipes" icon="diagram-project" href="/docs/guides/framework-recipes">
    Copy setup paths for Node, Next.js, Python, FastAPI, LangChain, and RAG apps.
  </Card>

  <Card title="API reference" icon="brackets-curly" href="/docs/api/overview">
    Integrate directly with the EvalGate platform for traces, runs, projects, and keys.
  </Card>

  <Card title="Feature status" icon="list-check" href="/docs/platform/feature-status">
    Check what is Beta or Experimental, which interfaces are supported, and where to find acceptance evidence.
  </Card>
</CardGroup>

## The adoption path

<Steps>
  <Step title="Start with one local gate">
    Install the SDK, snapshot your current test/eval health, and add a CI step that fails when the baseline regresses. This proves the workflow before anyone has to adopt another dashboard.
  </Step>

  <Step title="Capture real failures">
    Add tracing when local gates are not enough. EvalGate captures production and staging behavior with inputs, outputs, tool calls, latency, token usage, cost, and metadata.
  </Step>

  <Step title="Promote failures into coverage">
    Convert repeated or high-risk failures into reusable eval cases. Label, cluster, synthesize, and review cases so your suites track actual user pain.
  </Step>

  <Step title="Gate releases with evidence">
    Run the eval suite in CI, compare against the baseline, and give reviewers clear pass/fail evidence before changes merge.
  </Step>
</Steps>

## What to use first

EvalGate is currently a controlled beta. Review [Feature status](/docs/platform/feature-status) before depending on a platform surface in production.

| Stage                 | Use this                                          | Outcome                                                     |
| --------------------- | ------------------------------------------------- | ----------------------------------------------------------- |
| First repo            | Local gate                                        | Baseline, break, and prove a regression report in 5 minutes |
| Production AI feature | Traces and eval runs                              | Turn real behavior into coverage                            |
| Team rollout          | Reviews, judges, and PR annotations               | Make AI quality reviewable                                  |
| Governed rollout      | Costs, benchmarks, annotations, and audit history | Track quality, spend, and release evidence across projects  |

## Explore next

<CardGroup cols={2}>
  <Card title="CI/CD integration" icon="arrows-rotate" href="/docs/guides/cicd-integration">
    Wire EvalGate into GitHub Actions or GitLab CI to gate every PR.
  </Card>

  <Card title="Tracing setup" icon="activity" href="/docs/guides/tracing-setup">
    Capture the real AI behavior that should become eval coverage.
  </Card>

  <Card title="LLM judge" icon="gavel" href="/docs/concepts/llm-judge">
    Add judge-backed scoring when assertions alone are not enough.
  </Card>

  <Card title="Model providers and BYOK" icon="key" href="/docs/platform/model-providers-byok">
    Connect your provider or gateway credential and understand the separate authentication, billing, and data boundaries.
  </Card>

  <Card title="Agent governance" icon="shield-check" href="/docs/platform/agent-governance">
    Scale from one gate to governed AI release workflows.
  </Card>
</CardGroup>