Caraxe reviews your Android build and returns a verdict: release, hold, or block.Your app passes every check. It looks ready.Then a real person taps something you never tested, and it stops.Caraxe covers that gap. Here's how.

open-source Android app · demo walkthrough

tap · x983 y2232 – launch · onboarding surfacetap · x799 y1728 – tap · sort_by dialogtap · x540 y2184 – type · todo.txt editortap · x400 y2256 – tap · bottom navigation

demo session · open-source Android appsurface 92c76d3992c6c696 · visitedworkflow onboarding · enteredsurface 903d6be15dc4817b · visitedcontrol sort_by · exerciseddialog · dismissed cleansurface d029147971d57f51 · visitedinput text · typed + committedfinding_type none · screen cleansurface b825797754a06cf1 · visitedwalkthrough mode · illustrativecontrol bottom_nav:to-do · tapobserved event · app stopevidence bundle · action + screen + device recordrelease outcome · coverage considered

Illustrative device record · not a live runILLUSTRATIVE DEVICE EVENTProcess: example.test.appState transition ended unexpectedly at example.test.app.NavigationHandler .onMenuItemSelected(SampleSource)Sample record · not a live runsample evidence · no benchmark result

criticalExample app stop after a navigation actionsample_app_stop

Launch the sample build
Open the secondary tab
Tap the destination

warningExample navigation label truncatesvisual_regression

Launch the sample build
Inspect the bottom navigation

warningExample control is missing an accessibility labelaccessibility_label_missing

Open the sample screen
Inspect the primary action

illustrative release review · sample build

coverage confidence

BLOCK

Your tests pass. Your build looks safe.
Watch how Caraxe turns an observed app stop into a release record. Illustrative, not a benchmark result.

Caraxe exercises a sample Android workflow

Illustrative device record · not a live run

ILLUSTRATIVE DEVICE EVENT
Process: example.test.app
State transition ended unexpectedly

Caraxe links the action, screen, and device record

BLOCKoutcome: BLOCK – with coverage and evidence attached

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.

Apply for beta access See a sample report

deep review Export PDF

Release verdictBLOCK

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 is published on the evidence pages.

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.

See the full workflow

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.

Published results

We publish our results, including the misses.

Before asking anyone to trust a verdict, we put our own record in public: how the review scores on a controlled benchmark, what happened against real reported bugs in real apps, and how every result is checked before it appears.

The benchmark: seeded bugs, scored runs, and the rounds that got worse before they got better.Real apps: thirteen bugs registered in advance, and where each one stands, including the misses.Verification: how results are checked before they are published.

Private beta

Help shape what comes next.

Solo Android developers, small teams and agencies: apply to test an eligible app and share feedback on Caraxe. Applications are reviewed and invitations are sent in batches. Applying does not guarantee access.

Apply for beta access

Pilot terms are provided before participation.

Just want the launch update?

Join the separate launch list for one email when public access opens. This is not a beta application.