const suite = await qainly.create({
  plan: "premium",
  apps: slots,
});

await tester.install(build);
await tester.runDay(1);
assert.ok(evidence);

escrow.hold(payment);
assign.testers(12);
release.onComplete();

For publishers

Launch better apps with professional QA

Hire verified testers, fund escrow once, and monitor real Android testing progress—day by day.

Pay once · unlock slots

12 testers auto-assigned

14 calendar days

Escrow until milestones

Product & engineering

Replace ad-hoc chats with a QA workflow

One place for slots, assignments, evidence, and releases.

Verified testers install your closed-track build on physical Android devices across manufacturers and OS versions.

See assignments, daily submissions, and engagement across a structured 14-day testing cycle.

Bugs, UX notes, crash flags, and recordings—organized so your team can ship fixes faster.

Pay into escrow, watch progress, and release when milestones clear. Transparent for everyone.

Day-by-day visibility

Mark Play Console invites, watch daily uploads, and rate testers when the cycle ends. Your dashboard stays the source of truth.

Campaign day map

Day 6 of 14

D10

D11

D12

D13

D14

Done Today’s task open Calendar-locked

How publishers ship

Quick, Basic, or Premium. Checkout unlocks your app slots and starts escrow.

Package names, install notes, Closed Testing track—then 12 testers auto-assign.

Calendar-locked tasks on real Android devices. Late help routes to admin first.

Admin review clears the day. Escrow releases to tester balance on approval.

Escrow

Funds sit in escrow after checkout. Testers and the platform share only after milestones pass review.

Escrow ledger

Held until milestones clear

Quick / Premium50% · 50%

Basic60% · 40%

Funds sit in escrow after checkout. Testers earn as daily evidence clears review—publishers never pay twice for the same milestone.

Testers join your legitimate closed testing track. QAINLY never facilitates fake installs or policy bypasses.