Skip to main content
Pick the path that matches how you work. Each one runs your app in a cloud session, in a Web browser or on a mobile simulator or emulator, and leaves evidence you can open in Revyl. Web is in alpha. To add it to your organization, email [email protected]. Each path starts with its own setup prompt for your coding agent.

Choose a path

Revyl opens each pull request’s build in a session, exercises the changed behavior, and posts a verdict on the PR. It works for Web, iOS, and Android apps, and it’s the fastest way to see Revyl work on your own code.
1

Install the Revyl GitHub App

In the dashboard, open Integrations → GitHub and install the app on your repository. From a terminal, revyl github connect does the same.
2

Configure a project root

Select the repository and configure its first project root: how each pull request is built for Web, iOS, or Android, and the app that receives each build. New project roots turn on proof of changes with the Revyl agent. From a terminal, run revyl github setup in your project instead.
3

Open a pull request

Revyl opens the pull request’s build in a session, and an agent exercises what the pull request changed.
4

Read the verdict

One comment on the pull request carries the verdict, a verification confidence score, screenshots, and a link to the session recording. Cloud Agents → Proof of Changes lists your organization’s proof runs.
Next: Proof of changes covers verdicts, sign-in, and which agent runs the proof. GitHub covers project roots and build profiles. On GitLab, follow the GitLab tutorial.

Keep going

Core concepts

Runtimes, evidence, Atlas, and the objects behind them

Atlas

The record of how your app behaves