Visitar URL original
Opslane — Catch the bugs code review misses
Skip to content
YBacked by Y Combinator

Trust every PR your agents ship.

Stop hoping your PRs work. Opslane runs your app on every PR and finds the bugs before you merge.

>Set up https://app.opslane.com/INSTALL.md

Open them on your computer when you're ready.

Your first 10 reviews are free. Setup takes about 10 minutes.

Pull request #482

Add partner payouts

  • Tests passed
  • Code review approved
  • Opslane found 1 bug

Partners get paid twice.

If the app restarts mid-payout, Alice gets $240 for the $120 she’s owed.

Caught before merge
Example PR. The bug is one Opslane found in Dub.co.

Why bugs still reach your customers

Your agents ship more code than anyone can check, and nothing in the usual checks runs your app the way production does.

  • Reading every PR yourself

    You can't keep up. Your agents write more code than anyone can read.

  • AI code review

    It reads the diff. It never runs your app.

  • Your agent's own tests

    They test the happy path, without Stripe, Slack, or the other services your app depends on.

  • Opslane

    Runs your app on every PR with test versions of its services, and finds the bugs that only show up when it runs: a failed payment, two requests at once, a restart mid-job.

Bugs Opslane found in open-source apps

We ran Opslane on open-source apps with 165k GitHub stars between them. It found 12 bugs in released code, and we reported every one to the maintainers. Here are four.

Lago · Open-source usage-based billing · 10.7k GitHub stars

What if Stripe takes the money, then returns an error?

Run by Opslane

  • Lago
  • Postgres
  • Redis
  • Stripe· 500

Lago bills a customer $50

Stripe takes the money, then answers with an error

Lago marks the payment failed

Retry the payment

Charged again: $100 for a $50 invoice

See it on GitHub

Stripe charges

chargeamountstatus
1$50succeeded
2$50succeeded

Lago invoice

amountpayment
$50failed

See all 12 bugs in 6 open-source apps

Every bug comes with a recording and a repro

The run, the data before and after, and the steps to reproduce it. This one is from Twenty, an open-source CRM with 59.9k GitHub stars.

opslanereported on twentyhq/twenty · #28043

Deleted a workspace while Stripe was failing. Everyone is locked out, and it's still billing.

Recording of the run

Terminal recording: before, the subscription is active with 1005 members. Stripe answers 500 to the cancel. deleteCurrentWorkspace fails with 'A payment processing error occurred.' After: 0 members, workspace not deleted, Stripe subscription still active, and the admin gets 'User not found'.

Stripe answers 500 to the cancel.

Before and after

BeforeAfter the delete failed
Stripe subscriptionactiveactive, still billing
Members10050
Workspace deletednono
Admin signs inworks"User not found"

deleteCurrentWorkspace: "A payment processing error occurred."

Steps to reproduce

  1. Use a workspace with an active, card-backed subscription.
  2. Make Stripe return 500 for DELETE /v1/subscriptions/{id}.
  3. As the admin, delete the workspace.

Opslane

Bug reported.

The fix

Cancel billing before removing anyone.

Its test

Passes. Fails without the fix.

Read the issue on GitHub See the fix

Paste one line. Your coding agent does the setup.

It reads your app, sets up test versions of its services, and Opslane tests your next PR.

  1. Minute 0

    Paste one line

    Into Claude Code, Codex or Cursor.

    > Set up …/INSTALL.md

    that's the whole setup.

  2. Minutes 1–10

    Your agent sets things up

    It reads your app and prepares test versions of its services.

    • your app
    • postgres
    • redis
    • stripe (test)
    reading your app…

  3. Your next PR

    Opslane tries it

    When something goes wrong, you get the bug on the PR, with a recording.

    Paid Alice twice after a restart

    posted on the PR.

Stripe fails. Redis drops. See what your app does.

Opslane runs isolated test versions of the services your app and its agents call, from Stripe to the LLM.

APIs
Stripe OpenAI Anthropic Gemini OpenRouter Slack Gmail Google Calendar Google Ads Meta Ads
Infrastructure
PostgreSQL Redis Kafka SQS DynamoDB S3 SMTP test inboxes

Use another API? We can build a test version of it for your app.

Pay per review, not per seat

Your first 10 reviews are free.

Pro

Recommended
$150/month

One plan for your whole team. Credits are shared.

  • 150 PR reviews a month
  • Your first 10 reviews are free
  • Need more? Packs of 25 reviews for $25, or turn on auto top-up
Get 10 free reviews

Enterprise

Custom

For larger teams, or code that has to stay in your cloud.

  • Runs in your own cloud
  • SSO
  • PR reviews sized for your team
Talk to us

Questions

What shows up on my PR?
A pass or fail for each thing Opslane tried, with a video of the run and the request log. When something fails, the comment says what Opslane did and what happened.
How is this different from AI code review?
Code review reads your diff. Opslane runs your app with the PR, tries what breaks in production, and shows you what happened. Every open-source bug on this page was in code that had already shipped.
Can it test an AI agent?
Yes, the same way it tests a billing flow. Your agent runs with test versions of the LLM and the services it calls, and Opslane checks what it actually did: what it stored, what it sent. An agent can say it sent an email it never sent; the transcript looks fine, the test inbox is empty. Opslane can also make the model leave steps out of its plan, as in the OpenHands tab above, or drop the Redis connection its webhooks depend on, which is how it found a bug in Sim.
How does Opslane decide what to try?
It reads the PR description to learn what the PR should do. Then it reads your code to find where that could go wrong: requests at the same moment, users with less access, the emails and jobs that run afterwards.
Where does it run, and how long is setup?
In our cloud. Each PR gets a fresh copy of your app with test data and test inboxes, deleted after the run. Setup takes about 10 minutes: paste one line into your coding agent.
Do I need to write tests?
No. Opslane works out what to try from the PR and your code, so there are no test scripts to write or keep up to date.
Is my code safe?
Your code runs in a sandbox that is destroyed after each run.

Try Opslane on your next PR.

Your first 10 reviews are free. Setup takes 10 minutes.

>Set up https://app.opslane.com/INSTALL.md

Open them on your computer when you're ready.