The questions people actually ask, answered without jargon.
Caraxe is an automated testing tool for Android apps. You upload an APK, or send one from CI, and Caraxe explores the app like a real person: it moves through screens, taps controls, fills forms, and watches what actually happens. At the end you get one verdict for the build: release, hold, or block, with the evidence attached. There are no test scripts to write or maintain.
Caraxe uses machine intelligence to decide where to go and what to try inside your app, the way a curious person would. We describe it as automated, scriptless testing, because that is the part that matters: you write nothing, and it explores on its own. Every finding it reports is backed by captured screens, actions, and device records, so you never have to take the software's word for anything.
Those frameworks run scripts you write, and they are good at protecting the paths you already know about. Caraxe writes nothing: it explores the build itself, which is how it reaches the paths nobody scripted. Most teams treat them as complements: keep your scripted suite for the known flows, and let Caraxe cover the gaps between them.
No. Device farms run your tests on many devices; if you have no tests, they have nothing to run. Caraxe brings its own exploration, so it works on builds that have no test suite at all.
One report per build: the verdict (release, hold, or block), the findings ranked by what to fix first, which workflows were covered and how confident the review is in each, and reproduction steps where the trace supports them. When coverage cannot support a release call, the report says inconclusive rather than guessing.
Android, both native and React Native builds, at launch. iOS comes later.
Caraxe is in private preview with founding design partners. The public benchmark and pricing publish at launch. Join the launch list on the homepage and you will get one email when it opens.