Vetted testers try your app on their own phones and computers, then send a report your developers can act on: what broke, how to reproduce it, and on which device. Including the 12-tester Google Play closed test.
Send the build you already have
What you get
Most teams arrive with one of three problems. The same testers and the same report format handle all of them.
New personal developer accounts need a closed test with at least 12 testers opted in for 14 days in a row. We supply them, keep them opted in, and send you what they found.
How the closed test worksBudget phones, small screens and slow networks: the places emulators don't show you.
People who have never seen your app follow your brief and show you where they get stuck.
Try it free on one flowSeverity, steps to reproduce, screenshots and the exact device, so fixing starts without a follow-up call.
We recruit, remind and replace testers who drop out. You see progress, not admin.
How it works
Testers work through your app at a normal pace instead of racing a timer, which is how they find the bugs that matter.
A Play Store or TestFlight link, an APK, a staging URL, a desktop installer or an extension. Then write what testers should try, in plain language.
Testers are matched to the platforms and devices you need. We handle recruiting, reminders and checking their work.
Each issue arrives with severity, steps to reproduce, screenshots and the device it happened on.
The report
Each finding is written up the way a developer needs it, so work starts the same day.
A confirmation screen, or a clear error and no charge.
Google Play closed testing
Google won't let a new personal developer account publish until it has run a closed test. We supply the testers, keep them opted in for the full 14 days, and send you what they found, which is exactly what Google's application asks about.
Personal developer accounts created after 13 November 2023 need a closed test with at least 12 testers.
Testers must stay opted in continuously for the 14 days before you apply. Someone who leaves starts over.
You answer questions about the test and what you changed. Google says review usually takes 7 days or less.
A free calculator. Nothing is sent anywhere; it runs in your browser.
The closed test most likely applies
Personal accounts created after 13 November 2023 need a closed test with at least 12 testers opted in for 14 days in a row before applying for production.
You have no margin
You meet the minimum, but one opt-out would pause your progress. Two or three spare testers protect the 14 days.
Source: Google Play Console Help. Google decides on production access; no one can guarantee approval.
The quickest way to judge a testing service is to read one of its reports. Pick the path that matters most and three people try it on their own devices, then report what breaks with steps and screenshots.
One per account, email and app. Free runs are picked up after paid ones, and we cap them each month so paying customers never wait.
Pricing
Prices in USD, shown before you sign up. No sales call, no contract.
See a real report before spending anything.
You ship every month and want every release checked.
You release a few times a year. No subscription.
Only need Google Play production access? The Play pass is $29 one-time: 12 testers on your closed test for 14 days, with their feedback and any bugs they find.
Get a Play passSmart TVs and wearables, accessibility audits or live payment testing are quoted separately. Specialist testing
Compared
You could recruit testers yourself, pay less for a headcount alone, or pay much more for an enterprise vendor. Here is the honest comparison.
Bug reports are included from the Starter plan up and on every credit run. If all you need is the 12 testers, a tester-only service usually costs less.
Three testers try one flow of your web, Android or iOS app from a public link, and report any bugs with steps to reproduce and screenshots. Each account gets one. It does not include Google Play closed testing, file uploads or desktop apps. Free runs are picked up after paid runs, and we cap how many we run each month so paying customers are never kept waiting.
Every paid plan includes at least 12 testers who join your closed test and stay opted in for 14 days in a row, which is what Google asks of new personal developer accounts. Google makes the final decision on production access and also asks you about the test in its application form, so nobody can honestly guarantee approval. We take care of the tester side.
Matching testers usually takes 2 to 3 days. How long testing takes after that depends on your brief, and a Google Play closed test runs for at least 14 days by definition. We email you when testing starts and when your report is ready.
People from our vetted tester network who test on their own phones, tablets and computers. We match them to the platforms and devices you ask for, and check their reports before they reach you.
Testers only see the build and the brief you send. Contact details aren't shared either way: for a Google Play closed test, we add testers to a private Google Group you put on your track, so you never need their email addresses.
Yes. You can cancel from the billing page at any time and your plan stays active until the end of the period you paid for. Credit packs are one-time purchases and never expire.
Plans include 12 to 20 testers per run depending on the tier. You can add more to any run for $3 per extra tester.
Start with a free Spot Check on one flow. If the report is useful, run your whole app next time.