> ## 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.

# Self-hosting Opslane on your own infrastructure

> Run Opslane on your own servers using the open source repo. Best for teams with strict data residency or compliance requirements.

Opslane is fully open source. If your team needs to run the testing infrastructure on your own servers — because of compliance requirements, data residency rules, or a preference for self-managed tooling — you can do that using the code at [github.com/opslane/verify](https://github.com/opslane/verify).

<Note>
  Self-hosting is an advanced path that requires managing your own infrastructure, keeping the service updated, and handling your own scaling. For most teams, the hosted version at [app.opslane.com](https://app.opslane.com) is the faster and easier choice. It's free during early access and requires zero infrastructure work on your end.
</Note>

## Who self-hosting is for

Self-hosting makes sense if you:

* Have a compliance requirement that prevents sending browser traffic through third-party infrastructure
* Need to run tests against internal apps that aren't exposed to the public internet
* Want full control over where your test results and screenshots are stored
* Are operating in an environment where outbound SaaS connections are restricted

If none of these apply, use the hosted version.

## What self-hosting involves

When you self-host Opslane, you are responsible for running and maintaining the following:

<CardGroup cols={2}>
  <Card title="Verify service" icon="server">
    The core Opslane service that listens for GitHub webhook events and orchestrates browser runs.
  </Card>

  <Card title="Browser sandbox environment" icon="box">
    The ephemeral sandbox infrastructure that spins up real browsers for each PR run.
  </Card>

  <Card title="GitHub App registration" icon="github">
    Your own GitHub App installation that points webhook events to your self-hosted service.
  </Card>

  <Card title="Storage and retention" icon="database">
    Handling for screenshots, videos, and run results — the hosted version manages this automatically.
  </Card>
</CardGroup>

## Getting started with self-hosting

Full setup instructions, environment variable reference, and deployment guides live in the repository itself.

<Steps>
  <Step title="Read the repository README">
    Start at [github.com/opslane/verify](https://github.com/opslane/verify). The README covers prerequisites, environment setup, and how to run the service.
  </Step>

  <Step title="Register a GitHub App">
    You need to create your own GitHub App and configure its webhook URL to point to your running Opslane instance. The repository includes step-by-step instructions for this.
  </Step>

  <Step title="Deploy the service">
    Follow the deployment guide in the repo to run Opslane on your infrastructure. Docker and manual setup options are both covered.
  </Step>

  <Step title="Install your GitHub App on your repos">
    Once the service is running, install your GitHub App on the repositories you want to test. Opslane starts processing PRs immediately.
  </Step>
</Steps>

## Staying up to date

When you self-host, you are responsible for pulling updates from the repository and redeploying. Watch the [opslane/verify](https://github.com/opslane/verify) repo for new releases to stay current with bug fixes and improvements.

<Tip>
  If you run into issues setting up self-hosting, open an issue on [GitHub](https://github.com/opslane/verify). The open source community and the Opslane team are active there.
</Tip>