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

# What is Opslane? Automatic real-browser PR testing

> Opslane runs real-browser tests on every GitHub pull request — no test scripts, no maintenance. Learn how it works and how it compares to Playwright.

Opslane is an automated testing service that watches your GitHub repositories and runs real-browser tests on every pull request — without you writing a single test script. When a PR opens, Opslane spins up a real browser in an ephemeral sandbox, crawls your app, and checks that nothing broke. Results appear as a PR comment with a pass/fail status, screenshots, and a video of the run. If a regression is detected, the merge is blocked automatically.

## What Opslane does

When you connect a repository, Opslane installs a GitHub App that listens for pull request events. Every time a PR is opened or updated, Opslane:

1. Provisions a fresh, isolated sandbox for that specific run
2. Launches a real browser (not headless emulation) inside the sandbox
3. Crawls your deployed app and exercises critical user flows
4. Compares the behavior against the baseline from your main branch
5. Posts the results — pass/fail, screenshots, and a full-session video — as a PR comment

If a regression is found, Opslane sets the GitHub check status to failing, which prevents merging until the issue is resolved or the result is manually overridden.

## Key benefits

<CardGroup cols={2}>
  <Card title="No test scripts" icon="file-slash">
    You never write or maintain test code. Opslane figures out what to test by crawling your app and learning its flows automatically.
  </Card>

  <Card title="Real browser" icon="browser">
    Tests run in a real Chromium browser, not a simulated environment. You catch rendering issues, JavaScript errors, and layout regressions that headless runners miss.
  </Card>

  <Card title="Any stack" icon="layer-group">
    Opslane works with any browser-based application — React, Next.js, Vue, Svelte, Rails, Django, or anything else that runs in a browser.
  </Card>

  <Card title="Automatic on every PR" icon="code-pull-request">
    No CI config to wire up. The GitHub App triggers a run on every pull request automatically, from the first day you connect a repo.
  </Card>
</CardGroup>

## How Opslane differs from Playwright and Cypress

Playwright and Cypress are excellent tools — but they require you to write and maintain test scripts. When your UI changes, your tests break. Someone has to update them. Over time, test suites become a maintenance burden that slows teams down.

Opslane takes a different approach: instead of running scripts you wrote, it crawls your app and discovers what to test on its own. There is no test code to write, no selectors to update, and no flaky tests to debug. You connect a repo and Opslane handles the rest.

|                                | Opslane     | Playwright / Cypress    |
| ------------------------------ | ----------- | ----------------------- |
| Test scripts required          | No          | Yes                     |
| Maintenance burden             | None        | Ongoing                 |
| Real browser                   | Yes         | Depends on config       |
| Setup time                     | \~2 minutes | Hours to days           |
| Runs on every PR automatically | Yes         | Requires CI config      |
| Catches visual regressions     | Yes         | Only with extra tooling |

<Note>
  Opslane is not a replacement for unit tests or integration tests. It focuses on end-to-end browser flows — the layer where regressions are most visible to users and least covered by existing tests.
</Note>

## Security and privacy

Every test run happens in an isolated, ephemeral sandbox that is destroyed after the run completes. Opslane does not store your application code. The sandbox spins up, runs the browser session, and is torn down — nothing persists between runs.

If you need full control over where your tests run, Opslane is open source. You can self-host the entire pipeline on your own infrastructure using the [opslane/verify](https://github.com/opslane/verify) repository.

## Supported stacks

Opslane works with any application that runs in a browser. There is nothing framework-specific to configure. As long as your app is deployed and accessible at a URL when the PR is created, Opslane can test it.

Commonly used with: React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Angular, Rails, Django, Laravel, and more.

## Get started

Opslane is free during early access. You can connect your first repository in about two minutes.

<Card title="Quickstart" icon="rocket" href="/quickstart">
  Sign in with GitHub, install the app, and get your first PR tested.
</Card>