What we are building, in the order we are building it.
This is the real plan, not a pitch deck. Now is in active development, Next starts when the core proves itself, and Later waits its turn. Early adopters change this order all the time.
Now
In active development, the core everything else builds on.
- Binary scanning for iOS (.ipa) and Android (.apk, .aab)
- The 137-rule technical guideline library
- Findings with evidence, severity and the fix
- SDK inventory matched against known CVEs
- The sample report, public and kept current
Next
Starts once the core checks prove themselves with early adopters.
- CLI with pass, block and unknown exit codes
- CI gate for GitHub Actions, Fastlane and friends
- API and webhooks
- SBOM and SARIF export
- Team roles, including a read-only auditor
Later
Only once teams use the checks on every release.
- Continuous monitoring of live apps
- Store sync with App Store Connect and Play Console
- Findings routed to Slack and Jira
- White-label client portals for agencies
- Datadog streaming
Something missing that would change your releases?
Early adopters decide this order. If a check or an integration would move AppCompliance from useful to essential for your team, that is exactly the message we want.
Your build is deleted the moment the scan finishes. Findings stay for your retention window. EU infrastructure, EU vendors, no AI training on your code.