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

# Welcome

> Revyl gives your agents a runtime to run and verify software in, and keeps what it observes in Atlas for your team and your agents to query.

<Hero title="The runtime platform for cloud agents">
  Revyl gives your agents a runtime to run and verify software in. An agent runs your app in a
  cloud session, such as a Web browser (alpha) or a mobile simulator, and Revyl records what
  happened.
  What it observes goes into Atlas: a record of how your app behaves that your company owns and
  any person or agent on your team can query.
</Hero>

## Start from where you work

<EntryPoints>
  <EntryPoint title="GitHub" icon="github" href="/agents/proof">
    Get a verdict from a live session on every pull request
  </EntryPoint>
  <EntryPoint title="Coding agent" icon="bot" href="/agents">
    Let Cursor, Claude Code, Codex, or another agent drive your app
  </EntryPoint>
  <EntryPoint title="CLI" icon="terminal" href="/install">
    Start sessions, check what your app does, and query Atlas from your terminal
  </EntryPoint>
  <EntryPoint title="Dashboard" icon="layout-dashboard" href="/atlas">
    Open Atlas, sessions, and reports in the browser
  </EntryPoint>
</EntryPoints>

## How it works

Every change goes through the same loop. Each step is something you can open in Revyl.

1. **Intent.** A pull request, a prompt to your coding agent, or the plain-English steps of a [test](/tests).
2. **Agent execution.** Your coding agent or the Revyl agent runs the app in a cloud [session](/sessions): a [proof run](/agents/proof), a test run, or a [dev loop](/dev-loop).
3. **Runtime evidence.** Each run leaves a [report](/tests/reports) with video, screenshots, logs, and network traffic.
4. **Verified behavior.** Validation steps and the proof verdict record whether the app did what was intended.
5. **Stored behavior.** [Atlas](/atlas) adds the screens, pages, and transitions the run observed to your app's record.
6. **Questions.** People open Atlas in the dashboard. Agents query it with `revyl atlas` and the Atlas skill.
7. **New intent.** What you learn, such as a screen no test covers, becomes the next change, test, or [exploration](/atlas/explore).

![A Revyl test report: the recorded run beside the steps the agent validated](https://docs.revyl.com/images/screenshots/hero-light.webp)

A test report: the run's recording beside each step, with the agent's reasoning for a validation.

## What Revyl handles

<Spotlights>
  <Spotlight title="Atlas" href="/atlas" image="spotlight-atlas" alt="The Atlas map with screens grouped into product areas">
    Every screen, page, and transition Revyl has observed in your app, with the evidence behind each one.
  </Spotlight>
  <Spotlight title="Proof of changes" href="/agents/proof" image="spotlight-proof" alt="A proof-of-changes write-up with screenshots as evidence">
    An agent exercises each pull request in a live session and posts a verdict before review.
  </Spotlight>
  <Spotlight title="Any coding agent" href="/agents" image="spotlight-dev-loop" alt="A session started from the CLI, with each action and a validation step recorded">
    Cursor, Claude Code, Codex, and other agents drive your app in cloud sessions through the CLI, MCP, and agent skills.
  </Spotlight>
  <Spotlight title="Runtimes" href="/sessions" image="spotlight-infrastructure" alt="Recent sessions with each device, runtime, duration, and start time">
    Sessions in Web browsers (alpha) and on iOS simulators and Android emulators, and macOS computers (alpha), for agents and people.
  </Spotlight>
  <Spotlight title="Tests" href="/tests" image="spotlight-tests" alt="A test's run history with status, build, and steps for each run">
    Write steps in plain English. An AI agent runs them and records video, logs, and network traffic.
  </Spotlight>
  <Spotlight title="Builds" href="/builds" image="spotlight-remote-builds" alt="A completed remote build and its build steps">
    Upload builds or register Web previews (alpha) from your own CI, or build on Revyl's runners.
  </Spotlight>
</Spotlights>

## Keep going

<CardGroup cols={3}>
  <Card title="Core concepts" href="/concepts" icon="book-open">
    Runtimes, evidence, Atlas, and the objects behind them
  </Card>
  <Card title="Frameworks" href="/frameworks" icon="package">
    Build setup for Web (alpha), iOS, Android, React Native, Expo, Flutter, KMP, and Bazel
  </Card>
  <Card title="Library" href="/library" icon="library">
    Modules, variables, scripts, and files you reuse across tests
  </Card>
  <Card title="Integrations" href="/integrations/github" icon="plug">
    GitHub, GitLab, Slack, Expo, Cursor, and Capy
  </Card>
  <Card title="Security and network" href="/security/allowlist-ip-addresses" icon="shield-check">
    IP allowlists and AWS PrivateLink
  </Card>
  <Card title="CLI reference" href="/reference/cli" icon="terminal">
    Every `revyl` command and flag
  </Card>
</CardGroup>