Real verified devices
Real Android phones and real people. Never emulators, bots, or device farms.
Core Service
Pass Google's 14-day closed test with real testers.
Google Play requires new personal developer accounts to run a closed test with at least 12 testers for 14 days in a row before production access. We supply real people on real Android phones, keep them active for the whole test, and give you the proof you need to apply.
12 to 25 verified testers
Starts in 3 hours
Approval guarantee
At a glance
- Duration
- 14 consecutive days
- Testers
- 12, 20 or 25
- Devices
- Real Android phones
- Price
- From $13.99, one-time
- Success rate
- 99.9% across 550+ apps
The requirement
Google's closed test in four numbers
-
12
testers
Minimum number of continuously opted-in testers.
-
14
days
Consecutive days each counted tester must stay opted in.
-
3
form sections
To complete when you apply for production access.
-
≤7
days review
Usual Google review time. It can sometimes take longer.
Applies to personal developer accounts created after 13 November 2023. Source: Google Play Console Help.
How it works
Your journey from order to production
-
Day 0
Order & create your track
Pick a plan, then create a closed testing track with a release in your Play Console.
-
Day 0
Add testers & share your link
Download our tester email CSV, add it to your track's tester list, then submit your opt-in link in your dashboard.
-
Within 3 hours
Testers opt in
Your verified testers join. The 14-day clock starts once the full count is opted in.
-
Days 1–14
Real daily usage
Testers use your app on real devices while you follow progress on the live dashboard.
-
Day 14+
Apply & get reviewed
Click Apply for production in Play Console. Google usually reviews within seven days.
How Google counts testers
Four rules that decide whether a test counts
Most failed tests break one of these. See how each tester is counted, then how we cover every rule.
-
Tester A Counted
Opted in for all 14 consecutive days.
-
Tester B Not counted
Opted out on day 9, before completing 14 days.
-
Tester C Clock restarted
Left on day 5 and returned on day 9, so the count starts again.
Which track counts?
- Closed testingCounts
- Internal testingDoes not count
- Open testingDoes not count
-
Continuous opt-in
Testers must stay opted in for at least 14 consecutive days. Testers who leave early do not count.
We keep testers opted in for the whole period.
-
Opt-outs restart the clock
If a tester opts out and returns later, their 14-day count starts again. Only consecutive days are counted.
Grow and Scale add buffer testers as insurance.
-
Closed track only
The test must run on a closed testing track. Internal and open testing do not satisfy the requirement.
You add our tester emails to your closed track and share its opt-in link.
-
Real Google accounts
Testers join with a Google Account through your opt-in link, on their own Android device.
Every tester is a verified human on a physical phone.
The application
What Google asks when you apply for production
The Apply for production form has three sections. We document your test so each one is easy to answer. See our production access form guide for examples.
-
About your closed test
How you found testers, how they used your app, and a short summary of the feedback you got.
-
About your app or game
Your target audience, the value your app offers and your estimated number of installs.
-
About production readiness
What you changed based on testing and why you believe the app is ready to launch.
Launch includes a standard answer template. Grow and Scale include custom-written answers.
What's included
Every plan covers the full 14-day cycle
Everything below comes standard. Plans differ only in tester count and reporting depth.
Live progress dashboard
Follow opt-ins and the day count in real time, without chasing updates.
Day 9 of 14Example view
Testers opted inAll active
Evidence & answers
Opt-in evidence screenshots and documentation for Google's production questionnaire.
- Opt-in evidence screenshots
- Answer template or custom-written answers
- Delivered after your test ends
Bug & crash reports
Reporting depth grows with your plan.
- Launch Basic
- Grow Detailed, with crash and ANR logs
- Scale Full
Free re-test guarantee
Rejected for engagement after following our process? We re-test for free or refund you.
Free re-test or refund
No account access
We never ask for your Play Console login. You add tester emails and share your opt-in link.
No login needed
Plans & pricing
Pay once. Pick your safety margin.
Google's minimum is 12. Buffer testers protect you if someone drops out during the 14 days.
-
Launch
$13.99 one-time
12 testers 12 required + 0 buffer
- Standard reporting and answer template
- Basic bug reports
- 48-hour post-test delivery
-
Grow Most popular
$24.99 one-time
20 testers 12 required + 8 buffer
- Custom-written production answers
- 1 core user flow and detailed bug reports
- Priority scheduling, 24-hour delivery
-
Scale
$39.99 one-time
25 testers 12 required + 13 buffer
- Up to 3 user flows, full reports
- Highest scheduling priority
- 12-hour post-test delivery
Compare every feature in the full plan comparison table. Managing several client apps? See the Agency Partner Program.
Why real testers
Real people versus emulators and bots
Hire App Testers
- Verified humans on physical Android devices
- Natural daily usage across varied devices
- Safe for your developer account
- Backed by a free re-test or refund guarantee
Emulators, bots and device farms
- Detectable patterns that Google can flag
- Identical device fingerprints
- Risk of rejection or account action
- No accountability if it fails
Read why in Why Google bans emulator testers.
Before you start
Make sure nothing else blocks approval
Tester engagement is only half of production access. Follow the complete guide to publishing on Google Play, run a Play Console audit first, learn how to pass the 14-day test and read the closed testing requirements. Prefer proof? Read customer reviews.
Frequently asked questions
What do I need to do after ordering?
You create a closed testing track with a release in Play Console, download our tester email list from your dashboard and add it to the track's tester list, then submit the track's opt-in link in your dashboard. After that we keep your testers active for the full 14 days. Step-by-step instructions are in your dashboard guide and in our 14-day test guide.
What is the Google Play 14-day closed test?
Personal developer accounts created after 13 November 2023 must run a closed test. At least 12 testers must stay opted in for 14 days in a row before you can apply for production access. We supply the testers, keep them active for the whole test, and record the results.
How many testers do I need?
Google requires a minimum of 12 continuously opted-in testers. Launch covers exactly 12. Grow adds 8 buffer testers (20) and Scale adds 13 (25), so your app stays above the threshold even if a tester drops out. Our 12 testers guide explains the options.
Are the testers real people on real devices?
Yes. Every tester is a real person using a physical Android phone. We never use emulators, bots, or device farms. Google can detect them, and they can put your developer account at risk.
How quickly does testing start?
Your first testers are typically opted in within 3 hours of you adding our tester emails to your closed track and submitting your opt-in link. The 14-day clock starts once the required number of testers have opted in.
How long does Google take to review my application?
Google says review usually takes seven days or less, but it can sometimes take longer. Google emails the account owner when the review is done.
What if Google rejects my production access request?
If you follow our process and are rejected for tester engagement, we re-test for free, or you can claim a refund under our approval guarantee. See the refund policy for details.
Do you need my Play Console login?
No. You create a closed testing track in Play Console, add our tester emails to its tester list and submit its opt-in link in your dashboard. We never ask for your developer account credentials.