AI review that opens your app

CI says it passes. Hydrofoil checks it works.

Hydrofoil opens each pull request's preview deployment in a real browser, checks the change against your ticket, and posts bugs, accessibility problems and visual issues to GitHub. Every finding comes with a screenshot and repro steps. There are no tests to write or maintain.

Review your first PR free See how it works

Works with

GitHub
Vercel
Netlify
Cloudflare Pages
Jira

OpenAdd postcode lookup to checkout #214postcode-lookupintomain

BuildUnit testsHydrofoilReviewing preview…4 findings

FindingsSelect one to see its evidence

Needs review findings never fail the check.

BlockerHigh confidence

Checkout button does nothing on a slow network

Reproduction

1Throttle the network to Slow 3G
2Fill in the delivery address
3Select “Pay $48.00”
4Nothing happens for 5 seconds. There's no loading state.

src/checkout/PayButton.tsx:42

MajorHigh confidence

Error message isn't announced to screen readers

Reproduction

1Enter an invalid postcode
2Select “Pay $48.00”
3The error appears on screen, but the accessibility tree has no live region for it

src/checkout/AddressForm.tsx:88

MinorMedium confidence

Mobile layout clips the postcode field

Reproduction

1Resize the viewport to 390px
2Scroll to the delivery address
3The postcode field runs past the right edge

src/checkout/address-form.css:17

Needs reviewLow confidence

“Sign in” and “Log in” are both used

Reproduction

1The header says “Sign in”
2The checkout form says “Log in”
3Both go to the same page

src/components/Header.tsx:12

Low confidence, so it won't fail the check.

The gap

Passing CI doesn't mean the feature works.

01
Tests check what you told them to check.
End-to-end suites are powerful, but someone has to write and maintain them, and they only catch the scenarios someone encoded.
02
Code review reads the diff, not the product.
No reviewer can realistically click every new flow, resize the window, trigger every error state and read the accessibility tree.
03
QA arrives after the PR is waiting.
By the time someone finds the broken interaction, the work has moved on and the fix costs more.
Hydrofoil closes the gap between code review and real-world QA.

How it works

From pull request to evidence, automatically.

See the full walkthrough and a sample report

01
Open or update a PR.
Hydrofoil is notified through the GitHub App.
02
It finds the preview and reads the context.
The deployment, diff, PR description and linked ticket.
03
It reviews the preview in a real browser.
Isolated, with deterministic checks first and AI judgement on top.
04
Results land in GitHub.
A check, a summary and inline comments, each with evidence.

Every finding shows its work.

Evidence

No mysterious AI warnings.

Every Hydrofoil finding comes with evidence, so your team can see what went wrong and decide what to do about it.

Hydrofoil · Evidence drawer

1

4

MajorHigh confidence

Error message isn't announced to screen readers

The postcode error is visible, but it has no live region and isn't linked to the field.

2

1Open /checkout
2Enter “BS1 4XX” as the postcode
3Select “Pay $48.00”
4Read the accessibility tree

3

src/checkout/AddressForm.tsx:88

88<p className="error">{error}</p>

SeverityBlockerMajorMinorNit

ConfidenceHighMediumLow · Needs review

Screenshot01The exact UI state, with the problem area highlighted.
Reproduction02The steps the agent took.
Code location03file:line for code findings.
Confidence04How sure Hydrofoil is.

Findings without evidence are dropped.
Low-confidence findings are marked Needs review and never fail your check.
Dismiss a finding with a reason and it stays dismissed.

What it reviews

One PR. Seven kinds of review.

Ticket to verdicts

Hydrofoil reads the ticket, then checks the work.

It builds acceptance criteria from your Jira or GitHub issue, the PR description and the diff. Then it verifies each one in the code and in the browser, and flags changes that no ticket explains.

Met
Partially met
Not met
Unable to verify

You can edit the criteria. Your edits carry over to later runs.

Hydrofoil · Acceptance criteria

ACME-123Let customers update their billing address

TicketPR descriptionDiff 5 criteria

1.User can open billing settings CheckingMet
2.Required fields are validated edited CheckingMet
3.Changes persist after refresh CheckingPartially met
The old address shows until reload
4.Invalid addresses show an error CheckingNot met
5.Changes appear on the next checkout CheckingUnable to verify
The preview has no saved cart

Change with no ticketsrc/lib/analytics.ts changes tracking. Nothing in the ticket explains it.

Tests what you forgot

Hydrofoil doesn't stop at the happy path.

What happens when…

The API takes five seconds?
the loading state
BlockerExample finding
Pay button shows no loading state for 5s
The request fails?
the error state
MajorExample finding
A 500 leaves a blank panel
The user double-clicks?
duplicate submissions
MajorExample finding
One click, two orders created
The user refreshes halfway through?
whether state survives
MinorExample finding
Step 2 of the form clears on refresh
The window is 390px wide?
clipping and overflow
MinorExample finding
Postcode field runs off screen
The user only uses a keyboard?
focus and interaction
[TBD: only if live]
MajorExample finding
Focus is lost after closing the dialog
The session expires?
what the user sees
MajorExample finding
Expired session shows a blank page
“Log in” here and “Sign in” there?
terminology consistency
Needs reviewExample finding
Two names for the same action

Fits your pipeline

Reviews happen where your code lives, on the preview you already have.

Install the GitHub App. Open or update a pull request. Hydrofoil waits for your preview deployment, runs its reviews, and reports back to GitHub. Nothing to migrate, and nothing to host.

GitHub

A check run, a summary comment, inline comments on code findings, and merge gating at the severity you choose. Re-run any time with /hydrofoil run.

HydrofoilWaits for the preview, reviews it in an isolated browser Read-only code access

Previews

Vercel, Netlify and Cloudflare Pages, or any per-PR URL pattern.

Tickets

Jira Cloud and GitHub Issues.

[TBD: Linear, Slack and Figma as “Coming later”?]

Pull request #214 · Checks

BuildUnit testsHydrofoil

Hydrofoil: 2 checks passed, 1 issue foundMinorBelow your merge gate (Major)View report

All checks have passedMerge pull request

Re-run from a comment

SK

/hydrofoil run

hydrofoil bot Started a new run on the latest preview

Hydrofoil only needs read access to your code.

Logged-in apps

Test the parts of your app behind a login.

Real applications aren't public demos. Give Hydrofoil test personas and it can use them to review authenticated flows. Credentials are encrypted, never shown to the AI model, and redacted from logs and screenshots.

How we protect credentials

Hydrofoil · Signed-in run

What the AI model seesrun log

›goto/login
›fillemail{{persona.admin.email}}
›fillpassword{{persona.admin.password}}
›fill2FA code{{persona.admin.otp}}
Signed in as Admin
›goto/settings/billing
›goto/admin/users

Encrypted
Never shown to the AI model
Redacted from logs and screenshots

Keep what you have

Keep your tests. Keep your code reviewer. Cover the gap between them.

You already use	Great at	Can't see	With Hydrofoil
Playwright or Cypress tests	Repeatable checks on known flows	Flows nobody scripted, copy, design, accessibility	Reviews what the PR touches, with nothing to write
An AI code reviewer	Deep reading of the diff	The running app	Adds runtime behaviour
Visual regression tools	Pixel-level baselines	Whether a new design meets the ticket	Judges the change against the ticket
Manual QA	Human judgement	Being on every PR	Does the repetitive pass; people take the exceptions
A coding agent in your editor	Fast, flexible, free	Independence and consistency on every PR	Runs on every PR whether or not anyone remembers

Compare Hydrofoil with each of these[TBD: comparison pages]

Pricing

See what a review costs before it runs.

Credits track real compute. Every run shows an estimate beforehand and the actual cost afterwards, with a breakdown per review. Owners can set monthly and per-run spend caps. Your first PR is free.

See pricing

Hydrofoil · Run cost · PR #214

Estimate, before the run~40credits

Actual, after the run36credits

Per review Estimate Actual

Functional14
Visual & design9
Accessibility6
Requirements4
Content3

Monthly cap1,240 / 2,000

Per-run cap36 / 60

Illustrative numbers.

Frequently asked questions

Let Hydrofoil review your next PR.

Install the GitHub App, point it at a preview deployment, and see what it finds. No test scripts to write. No migration.

Review your first PR free

CI says it passes. Hydrofoil checks it works.

Passing CI doesn't mean the feature works.

Tests check what you told them to check.

Code review reads the diff, not the product.

QA arrives after the PR is waiting.

From pull request to evidence, automatically.

Open or update a PR.

It finds the preview and reads the context.

It reviews the preview in a real browser.

Results land in GitHub.

No mysterious AI warnings.

One PR. Seven kinds of review.

Hydrofoil reads the ticket, then checks the work.

Hydrofoil doesn't stop at the happy path.

Reviews happen where your code lives, on the preview you already have.

Test the parts of your app behind a login.

Keep your tests. Keep your code reviewer. Cover the gap between them.

See what a review costs before it runs.

Frequently asked questions

Let Hydrofoil review your next PR.