How to inventory the AI-built apps your team already shipped
Verified 24 August 2026
Reviewed by Elon Salfati, Founder
The direct answer
Inventorying AI-built apps means finding every app someone shipped outside the formal software register. Check the repository list and hosted-tool accounts, ask each team what runs its recurring work, then record one page per app: owner, runtime, data touched, access, and the last proven restore.
Start with the work, not the software list.
Ask every function which app runs a weekly report, approval, reconciliation, or customer task. AI made building an app a side task, so many useful tools never entered procurement or the formal application portfolio.
Search the two places an app can hide.
Repository-backed apps appear in the organization and member repository list. Hosted apps appear in platform accounts, identity grants, expense records, and team interviews. The same app can leave traces in more than one place, so deduplicate by purpose and owner.
- List organization and member repositories.
- Review hosted-tool accounts and identity grants.
- Ask function leads what their teams built and still use.
- Check recurring software spend and shared credentials.
The inventory is complete when every app has an answer.
A name alone is not an inventory. Record who owns the app, where it runs, what data it touches, who can access it, and whether a restore has ever passed. Retire the app, assign it to an internal team, or place it under custody.
Sources
Primary documentation opened and checked on 24 August 2026.
- 1. About repositories
GitHub Docs
Repository ownership, permissions, revision history, and collaboration.
- 2. Claude Code overview
Anthropic
What Claude Code reads, edits, runs, and automates inside a codebase.
- 3. Guide to Enterprise Patch Management Planning
NIST
Patch management as identifying, prioritizing, acquiring, installing, and verifying updates.
Next step
Keep the register even if custody is not the answer.