Automated testing · mobile · web & api · games

Find out where your product breaks before your users do.

Recon Node runs your app, your API and your game build through the same messy conditions real people put them through — bad networks, old devices, wrong inputs, long sessions — and hands you a plain list of what failed and how to reproduce it.

Get early access Run a live check No signup needed to try it
Run RN-0417 · full sweep scanning
Mobile / android · ios
Web & API / http · schema
Games / build · session

01 · What you can point it at

Three kinds of target, one run history.

Web and API checks are live now — paste a URL and try it. Mobile follows, then games. One dashboard throughout — you will not be relearning the product each time.

Mobile appsIn build

Upload an APK or point at a TestFlight build. Recon Node installs it on a device matrix and drives it like a first-time user who taps the wrong things.

  • Cold start and ANR watch
  • Permission and consent flows
  • Deep links and back stack
  • Offline and flaky network
  • Rotation, low memory, small screens

Web apps and APIsLive now

Give it a URL or an OpenAPI spec. It walks every route, submits every form badly, and checks that your contract still says what it said last week.

  • Status codes and error shapes
  • Auth, session and rate limits
  • Schema drift against the spec
  • CORS, redirects and TLS chain
  • Core Web Vitals on real page loads

GamesOn the roadmap

A scripted player runs your build for as long as you want. It measures what a human would only notice after an hour of play, and it never gets bored.

  • Frame time and dropped frames
  • Input latency by device
  • Level load and asset streaming
  • Save and load integrity
  • Memory growth over long sessions

02 · How a run works

Point it, leave it, read the report.

STEP 01 — DISPATCH

You choose a target and a check set

Pick the build, the environments and the checks you care about. Save it as a preset and it runs on every push, or nightly, or on a schedule you set.

STEP 02 — SWEEP

Runners drive the product in parallel

Each environment gets its own runner. They record video, network traffic, logs and timings, so a failure comes with the evidence attached rather than a line number.

STEP 03 — REPORT

You get findings, not a wall of logs

Findings are grouped, deduplicated against previous runs and marked new, still open or fixed. Repeat noise stops appearing after the second run.

03 · What a report looks like

Every finding comes with a way to reproduce it.

Run RN-0417 Target Northgate Storefront Duration 11m 06s Findings 6 open · 2 fixed
Critical App closes when the device rotates during checkoutReproduced 3 of 3 · video + logcat attached Pixel 6a · Android 13
Critical POST /v1/checkout returns 422 with an empty error bodySpec expects a message field · first seen this run api.staging · v2
Major Frame time hits 41ms in the level 3 arenaBudget is 16.7ms · sustained for 8 seconds Build 214 · mid-tier GPU
Major Cold start takes 4.2s on a clean installSlower than the last 5 runs · trend attached Redmi Note 12 · Android 12
Minor Invite deep link lands on a 404 instead of the app/invite/:code · web fallback missing Chrome · Android
Minor Save file fails to load after quitting mid-level1 of 20 attempts · low reproduction rate Build 214 · Windows

04 · Pricing

Start free. Pay when runs become part of your release.

Solo
Free
  • 1,000 web & API minutes
  • 2 targets
  • 7 days of run history
  • Deduplicated findings
  • No card required
Studio
$19 / month
  • 25,000 web & API minutes
  • 30 device minutes included
  • 15 targets, 5 seats
  • 90 days of history and trends
  • Run on every push
Team
$99 / month
  • 250,000 web & API minutes
  • 200 device minutes included
  • Unlimited targets
  • Unlimited history
  • Private runners on request

Web and API minutes are cheap and generous. Device and game minutes cost real money to run, so they are metered separately — $0.30/min on Studio, $0.22/min on Team. No pooled credits, no surprise overage bill.