Ship your app without shipping bugs.
Describe a test in plain English. An AI agent taps through your app on a real device like a user would, then hands you a video, a step-by-step report, and a verdict on every pull request.
Works with any .apk or .ipa · No test scripts to write
From build to answer in three steps
The whole loop takes about a minute, and none of it involves writing a script.
- 1
Upload your build
Drop in an .apk or .ipa straight from CI. No SDK, no code changes, no test scripts.
- 2
Describe the test in English
“Sign up, add an item to the cart, and check out.” That sentence is the whole spec.
- 3
Get a video and a verdict
An agent taps through your app on a real cloud device and tells you what broke, with a recording.
Catch it in the pull request, not in the store review.
Install the GitHub App once and every pull request gets a real end-to-end run on a real device. Results come back as a Check Run and a comment, with a linked recording for each test, so a reviewer can watch the failure instead of guessing at it.
- Runs automatically on every push to a PR
- Comment on demand with “@clickproof run”
- Works with your existing build workflow
- Sign up and check outreport
- Apply a discount codereport
- Guest checkoutPay button never enabledreport
Posted automatically on every push. Each report links to the recording of that run.
Everything you need to trust “it works”
Built for the tests that matter most and break the hardest: the ones that go all the way through your app.
Real cloud devices
Tests run on actual Android and iOS hardware: real timing, real keyboards, real system dialogs.
Plain-English tests
No Appium, no selectors, no brittle scripts. Write what a user would do and let the agent figure out the taps.
Video + step reports
Every run returns a scrubbable recording plus a screenshot and a reason for each step.
Runs on every PR
Install the GitHub App and each pull request gets a real end-to-end run before it merges.
Survives redesigns
Because the agent reads the screen instead of matching selectors, moving a button rarely breaks a test.
Teams and billing built in
Organizations, seats, run allowances, and metered device-minutes out of the box.
Simple, usage-based pricing
Start free. Upgrade when you ship more. Every plan includes every feature.
Try it end to end
- 10 runs / month
- 1 concurrent runs
- 30 device-minutes
- 1 seat
- Every feature unlocked
- Video reports
- GitHub App + Action
For solo builders
- 100 runs / month
- 2 concurrent runs
- 200 device-minutes
- 3 seats
- 1 project
- Auto-run on pull requests
- Shareable video reports
For product teams
- 600 runs / month
- 5 concurrent runs
- 1,200 device-minutes
- Unlimited members
- Unlimited projects
- Unlimited team members
- Scheduled runs
- Priority email support
A run is one test executed on a real device, capped at 10 minutes. iOS runs count as two runs, since an iOS device costs twice as much to run. Runs pause once you reach your monthly allowance and resume at the start of the next cycle.
Questions, answered
Do I need to change my app or add an SDK?
No. You upload a build (an .apk or .ipa) exactly as your CI produces it. There is no SDK, no instrumentation, and no code change. The agent drives the app through the device, the same way a person would.
How is this different from Appium or Maestro?
Those need you to write and maintain scripts against selectors, which break whenever the UI moves. Here the test is a sentence in plain English, and a vision agent decides what to tap. When your layout changes, the test usually still passes.
What happens when a test fails?
You get the reason in plain language, a screenshot of every step, and a video of the whole run. On a pull request, that lands as a Check Run and a comment with a link to each report.
Does it run on real devices?
Yes. Real cloud Android and iOS devices, not simulators. That means real timing, real keyboards, and real system dialogs.
Can I run it in CI?
Two ways. Install the GitHub App and tests run automatically on every pull request, or call the API from any pipeline with the GitHub Action.
What counts as a run?
One test executed once. Free includes 10 runs to try the whole flow end to end; paid plans renew their allowance every billing period. An iOS run counts as two, because iOS device time costs us twice as much.