Verdict-first reporting
Every report opens with an evidence-supported release assessment, including Inconclusive when workflow coverage is insufficient.
FeaturesBuilt for Android release review.
Built for Android release review.
Not generic QA.
Caraxe keeps the scope bounded: evidence first, regression memory across builds, and a release decision teams can act on.
Build-over-build memory
Findings stay threaded across builds so teams can see what is new, recurring, resurfaced, escalated, or resolved.
Reproducible evidence
Findings carry a concise evidence bundle, with trace-backed reproduction context whenever the recorded action path supports it.
Impact taxonomy
Customer-readable issue buckets map directly to engineering ownership and release risk.
Systemic insight detection
Repeated patterns across screens are grouped as one operational insight instead of noisy duplicate findings.
Trust by design
Private artifacts, pixel redaction, disclosed AI processing, and findings grounded to runtime evidence.
Also included
The details that make the report usable.
Screenshot diff slider
Compare current and baseline screens without opening a second tool.
Zero-setup device
The device path is implemented; production capacity and operating recovery checks remain launch gates.
API and CI gating
Integration surfaces exist in code; automated release gating stays closed until the core is certified.
Team workspaces
Workspace and role surfaces are implemented; public multi-team operation is not yet open.
Calibration loop
Feedback capture is implemented; measurable cross-app calibration value remains a certification question.
Replay reviews
Replay behavior is implemented; speed and cross-app reliability certification remain open.
Help validate it on real release work.
Private validation is in progress. We are accepting a small number of Android teams whose apps fit the current supported scope; public access waits for multi-app certification.