Video proof on every pull request

See it work, before you merge.

No tests to write. Kery reads the diff and works out what the change was supposed to do.

Connect your repo Or run it locally
Use case 01 · Pull request checks

A pull request opens; Kery checks it.

Kery reads the diff, works out what the change claims to do, runs those claims in a real browser on the preview deployment, and posts each verdict back to the PR — with video proof.

Tasks: create, edit, share, delete #128

Open wants to merge 2 commits into main
Preview deployment ready — acme-dashboard-pr-128.vercel.app
kery-ai bot commented just now

4 verified · 1 contradicted — ▶ video proof

  • Creating a task
  • Editing a task
  • Sharing a task with a teammate
  • Deleting a task — it comes back on reload

    Deleted the task and the list updated. After reload it was back.

  • Email notification sent

Test my sign-up form

4 passed · 1 failed — ▶ watch the run

  • Sign-up page opens from the header button
  • Email field accepts a valid address
  • Password field accepts a valid password
  • Create account submits the form
  • Success message appears after signing up

    Submitted fine, then the page reloaded to an empty form. No confirmation shown.

Use case 02 · Plain-English tests

You describe a flow; Kery tests it.

Group tests into suites

Bundle sign-up, checkout, and settings into one group and run it in one go.

Put runs on a schedule

Nightly or hourly passes over the flows you care about, results waiting for you.

Auto-scan your app

Kery crawls your routes, finds the flows worth covering, and suggests the tests.

Use case 03 · Local & open source

Run the whole stack on your machine.

  • Open-source engine you can inspect, run, and extend locally.
  • Runs locally with Docker.
  • Installs MCP into Cursor, Claude Code, and Codex CLI.
  • Point Kery at your app running locally and start testing it.
  • Supports the following providers.
OpenAI Anthropic Google Gemini OpenRouter
View GitHub README See how it works
kery setup
Kery Cloud

Why teams trust the verdicts.

It gets past your login.

Clerk, Supabase, Auth0, Firebase, 2FA codes, magic links, Vercel preview protection. Most agents stop at the sign-in page. Kery signs in and keeps going.

Nothing to write.

No test scripts, no acceptance criteria, no ticket. Kery reads the diff and works out what the change was supposed to do.

Video of the moment it broke.

Every check comes with a recording, and “watch this moment” seeks straight to the deciding step.

It won’t block your merge on a maybe.

Only a contradicted check fails the build. Everything else gets reported, not enforced.

It gets quieter every run.

Kery remembers your app’s paths and conventions, and the findings you’ve called false positives. Fewer repeats each time.

It runs itself.

Install the GitHub App. Kery picks up every pull request and its preview deploy. No CI config, no YAML.

Or run the whole thing yourself — Apache-2.0, Docker, your infrastructure, your model keys.

Self-serve

Connect a repo, get your next PR checked

Kery Cloud runs on your pull requests today. GitHub App, one-command connect, no API keys.

Connect your repo
FAQ

What teams usually ask first.

What is Kery?

Kery checks that your pull requests do what they say. It reads the diff, works out what the change claims to do, runs those flows in a real browser, and posts each check back to the PR with a verdict and video of what actually happened.

Do I need to write test scripts?

No. Kery works out what to check from the pull request itself. You can also point it at a flow in plain English, and useful flows can be saved and rerun.

Does it work behind authentication?

Yes. Kery supports logged-in products through configured environments and credentials, including form login, Clerk, and Supabase Auth. It is not limited to simple public sites.

Which LLM providers are supported?

Kery supports OpenAI, Anthropic, Google Gemini, and OpenRouter. Bring your own provider keys when running locally.

Can I run Kery in CI?

Yes. Kery Cloud runs on your pull requests today — connect the GitHub App and every PR gets checked against its preview deployment. The open-source stack can also run in your own pipeline.

What can I do with MCP?

Use Kery from MCP-compatible clients like Cursor, Claude Code, and Codex CLI to run browser checks on your app, inspect route coverage, and pull results.

Where does my data live?

In the open-source setup, run artifacts live in your own environment. Kery only sends prompts and required context to the LLM provider you configure.

Is Kery open-source?

Yes. The local engine is open-source, built for self-hosting, inspection, and extension. Kery Cloud adds hosted execution and team workflows.

Community

Join the Kery community.

Ask setup questions, share MCP workflows, compare real browser runs, and follow what lands next.

Join Discord
Get started

Put proof in every pull request.

Connect your repo Star on GitHub