criticalExample app stop after a navigation actionsample_app_stop
- Launch the sample build
- Open the secondary tab
- Tap the destination
Upload a build. Get a verdict you can defend.
Every release is a claim. Caraxe drives your build before your users do, then tells you plainly – release, hold, or block – with the evidence to back it.
deep review Export PDF
Do not release this build.
Two critical workflow gaps need attention before this release is safe.
F-01
Primary release gap
Validation accepted empty submit
criticalsignup workflow88% confidence
Open signup, submit empty fields, observe success state instead of validation feedback.
Issues122 critical
Evidence 76linked artifacts
Coveragepartialconfidence medium
Demo shows a sample open-source app, not a benchmark result. The public benchmark publishes at launch.
How it works
Upload. Review. Verdict.
Upload your app
Drag in the APK, or let your CI send each new version automatically.
Let the review run
Caraxe works through the app like a real person and compares what it sees with earlier versions.
Read the verdict
One report with the verdict, the fixes ranked, what was covered, and reproduction steps when captured.
What teams get
A verdict, and everything behind it.
Caraxe gives each supported Android build a structured release review: what broke, where it happened, why it matters, and the evidence to reproduce it. When coverage cannot support a release call, the result stays inconclusive.
Release decision
Release, hold, or block – backed by evidence. When coverage falls short, Caraxe says inconclusive.
Regression memory
New, recurring, resurfaced, escalated, and resolved findings stay threaded across your build history.
Evidence engineers can use
Captured screens, actions, and observed results are linked to findings, with step-numbered reproduction context when the trace supports it.
Coverage confidence
The report shows which workflows were actually reviewed, where confidence is strong, and where risk remains.
Why this exists
Find the bugs your tests can’t reach.
Scripted tests protect the paths you already know. Real users find the gaps between screens and states: the failed validation, the stale data, the lifecycle events your suite never touches. Caraxe is built for that missing layer.
It uses your app like a real person: odd taps, empty forms, the paths no script covers.
It notices what tests miss: the button that does nothing, the form that accepts anything, the crash on the way back.
It answers plainly: release, hold, or block, with the evidence attached. When it isn't sure, it says so.
Launch
Caraxe opens soon.
We are finishing the private preview with our founding design partners. Pricing and the public benchmark publish the day it opens. Leave an email and you will be the first to know.
Help shape Caraxe.
We are onboarding a small group of Android teams as founding design partners: early access to new detection work, a direct line to the people building Caraxe, and a real say in what ships next.
Become a design partner