Push the build, get a report you can check
You drop a build into the queue over the API and set the slot count and the fee yourself. Behind every report there is a run record that cannot be edited.
Why proof
You cannot tell whether it was run
An outsourced test report is usually a table and a few screenshots. Nothing in it shows that the case was actually executed.
You cannot tell where it was run
The "works on my machine" argument looks settled and then comes back, because nobody wrote down the environment. A fingerprint closes it.
Retesting is expensive
On a second round the testers who ran the first one are offered it first, so you are not explaining the cases again.
Who holds your build, and for how long
Every tester who takes a job accepts the confidentiality undertaking before the build opens. The moment they accept is written into their account's record.
- The build, screenshots, test steps, your release date and the faults found are all confidential; none of it leaves the platform.
- A tester uses the build only for the job given. Reverse engineering and any use outside that job are prohibited.
- When the job closes the tester deletes the build and its files from their device. The run record stays with us.
- The obligation does not end with the job; it runs until the build is public, and for at least three years.
- A breach cancels the job, withholds the fee and suspends the account. Your right to pursue direct losses through the courts is unaffected.
Integration
Putting a job in the queue is one request to one endpoint. Your pipeline can open a job automatically whenever it produces a build, and the cases travel in the same request.
- Build, case list, required environment profile and slot count go in one request
- A webhook fires when a report is ready
- The run record and the attached evidence arrive with the report
- A report you reject carries your reason back to the tester and opens a dispute window
What you pay
You pay the fee you written on the job plus the platform fee. We take no commission from testers, and a job whose slots never fill costs nothing.
| Item | Note |
|---|---|
| Tester fee | The amount you put on the job, per accepted report |
| Platform fee | 18% of the tester fee, falling with monthly volume |
| Job with unfilled slots | No charge |
| Retest | Platform fee halves on a second round of the same build |
Try it with one build
Setup takes one call. We open the first job with you and write the cases together.