Google Play closed testing, operated on real devices

THE 20-TESTERBARRIER,SOLVED.

Google Play's policy requires personal developer accounts to recruit 20 testers for 14 consecutive days. BetaBox automates compliant sandbox testing using residential IP-verified simulated environments.

Compatible with platforms
Google PlayAndroidKotlinFlutterReact NativeUnity

Google Play requires new personal developer accounts to run closed testing with at least 12 testers for 14 days before applying for production access.

Read Google's policy

Not just tester sourcing. BetaBox manages the whole test campaign.

Choose a package (testers × days), create the app, pay, assign devices, track progress, and collect feedback in one workflow instead of coordinating everything by hand.

betabox.tech/overview
BetaBox dashboard overview showing application status and progress

From test-ready app to production access evidence.

The workflow reduces repetitive developer work while keeping enough context to handle login-gated apps, crashes, and new builds.

01

Choose a package and submit app details

Pick the tester count and duration that fit, enter the package name, testing URL, and login details if needed, then pay with PayPal or SePay.

02

BetaBox runs the campaign

Testers are assigned to real devices, the app is installed, and activity is monitored every day throughout the closed testing cycle you chose.

03

Receive evidence and prepare release

Track progress, device logs, and failure analysis in the dashboard, and receive operating evidence for a more confident production access request.

Configure your package

Configure your own tester count and campaign duration. Choose a quick preset or adjust the slider below to get an instant quote.

Number of testers
testers
1 tester20 testers
Test duration
days
3 days30 days

Quote Invoice

Setup fee$4.56
Daily device fee$9.57 (14 days)
Total$14.13
Matches Google Play Closed Testing standard requirement (12 testers x 14 days minimum).

Included in the campaign

Pick your own tester count (1–20) and duration (3–30 days)
Real Android devices + centrally managed tester accounts
Daily closed testing progress tracking
Per-device logs: screenshots, video, logcat, IP
4.9/5 across 180+ campaigns run

For developers who want a planned launch, not a lucky break.

"I no longer had to ask people one by one to install my app. BetaBox puts the test cycle into a dashboard, which makes tracking much easier."

Linh Nguyen

Indie Android developer

"The best part is the clear evidence. When a tester hit a login issue, the team responded quickly and I fixed it the same day."

Minh Tran

Founder, productivity app

"The app creation and payment flow is tidy enough for agency clients. We do not have to explain closed testing from scratch every time."

An Pham

Mobile agency lead

"Being able to pick the exact tester/day count helped us optimize the marketing budget. The dashboard report is easy to show to stakeholders."

Quang Vu

CTO, fintech startup

"Real devices and clear logs meant Google never asked us to redo anything when we applied for production access."

Thao Le

Solo game developer

"Support replies on Telegram incredibly fast, even on weekends. Very reassuring when running a tight campaign."

Hoang Bui

Product manager

"I no longer had to ask people one by one to install my app. BetaBox puts the test cycle into a dashboard, which makes tracking much easier."

Linh Nguyen

Indie Android developer

"The best part is the clear evidence. When a tester hit a login issue, the team responded quickly and I fixed it the same day."

Minh Tran

Founder, productivity app

"The app creation and payment flow is tidy enough for agency clients. We do not have to explain closed testing from scratch every time."

An Pham

Mobile agency lead

"Being able to pick the exact tester/day count helped us optimize the marketing budget. The dashboard report is easy to show to stakeholders."

Quang Vu

CTO, fintech startup

"Real devices and clear logs meant Google never asked us to redo anything when we applied for production access."

Thao Le

Solo game developer

"Support replies on Telegram incredibly fast, even on weekends. Very reassuring when running a tight campaign."

Hoang Bui

Product manager

Clear commitments before the campaign starts.

No. BetaBox commits to a clear closed testing process with real testers, real devices, and complete evidence. Google Play makes the final production access decision.

You need an app on the closed testing track, a testing URL, package name, and login details if the app requires an account. If you are unsure, support will guide you.

The dashboard and operations team record related errors, logs, or screenshots so you can fix them. After a new build is available, the campaign can continue based on the real status.

Send your app details and BetaBox will suggest the right test setup.

If you are unsure how many testers you need, whether login access matters, or where Play Console is blocking you, send a short note. Support will respond with app-specific guidance.

Your app is ready. Do not let closed testing slow down launch day.

Create an account, submit your app details, and start a campaign with real devices, human support, and a clear report.