Verify what an app is actually built on before you invest — its real SDK inventory, third-party dependencies, and the evidence behind every claim.
Start freeA data room says 'proprietary stack'. The APK may say otherwise — three analytics vendors, a deprecated push SDK, an ad network in a product the deck calls subscription-only. SDKGPT reads the binary, so technical claims get checked against ground truth.
Every detection carries its evidence: the matched signal, the app version, the rule that fired. When a number goes into an investment memo, you can show the chain it stands on.
| What we surface | What it can mean |
|---|---|
| Multiple analytics SDKs | Parallel tracking stacks — integration debt or undisclosed partners |
| A deprecated or unmaintained SDK | Security and compliance exposure the team hasn't mapped |
| Ad SDKs in a 'subscription-only' app | Monetization reality versus the stated model |
| Region-specific SDKs | Market dependencies worth pricing into the deal |
Patterns like these are where technical diligence questions come from.
No. Every detection comes from parsing the distributed APK — the binary the store actually ships. If an SDK isn't in the binary, it isn't in our data.
We always reflect the latest store version, and detection history accumulates as new releases get parsed — enough to see when a dependency entered the stack.