New Intake

Stage the target first, then let the private workspace carry the analyst story.

Upload a binary or capture the package identifier. The clean-slate workflow keeps this step public, then routes the operator into login, pricing, and the new findings-first workspace.

Stage 1

Target intake

Checking your access before we route the upload journey.
Binary type

Choose a binary from your machine, or skip this if you are staging the app by identifier.

Package or bundle identifier intake works even when the binary is not uploaded yet.

Binary details are staged in this browser for the upgrade gate preview. New here? Request access

After Intake

What unlocks next

Private findings

Evidence, impact, remediation, and timeline in a single route.

App context

Coverage, endpoints, objective, and linked signals per monitored target.

Dynamic lab

Runtime validation can pick up once a finding needs deeper confirmation.

Supported Inputs

APK, AAB, IPA, or identifier-only intake

The rebuilt flow is happy to start from either a real binary or a precise package/bundle reference.