How to manage untracked internal tools built with AI
Non-developers are using AI coding agents to build internal apps and deploying them off the company record on personal laptops, cloud accounts, or third-party platforms. Because these apps scatter across untracked locations when IT denies permission, managers are forced into an endless game of whack-a-mole to find and stop them.
What the numbers show
Counted from the threads quoted below. How we count
- People have been saying this in most months since September 2026.
- This comes up 137.6× more often in r/ITManagers than across the site as a whole.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
How to manage untracked internal tools built with AI
- 1Tenant restrictions and applockerDid this help you?
- 2Enforcing strict zero-tolerance policies that threaten termination for unauthorized app deployment or LLM data sharing.Did this help you?
- 3Running employee-built apps through standard IT architecture reviews, Release Management, and infosec scans.Did this help you?
- 4Implementing lightweight intake processes requiring a named owner, SSO integration, and a data access summary.Did this help you?
- 5Building internal platforms with automated guardrails, secret management, and GitHub lifecycles to safely host the apps.Did this help you?
- 6Limiting access to AI developer tools like Cursor to specific users and requiring manual code reviews before production use.Did this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“non-developers have started building internal tools with AI coding agents, and then ask to run them at work. The usual answer from IT is “no,” which makes sense, but the apps don’t go away. They end up on someone’s laptop, a personal cloud account, or a shared drive.”source ↗
“We found that worse than these apps running on laptops, etc is these services end up running on third party platforms, or hosting on GitHub pages under personal repos and such.”source ↗
“Yes. We are seeing this. It varies from company to company, but at AI first organizations, adoption is large. At my org, we have at least hundreds, if not thousands of these apps.”source ↗
“The biggest fear is people building with personal AI, and deploying in untracked locations, especially off company record.”source ↗
Where this came up
People with this problem also raised
- 3Unauthorized third-party software integrations on client networks
- 7How to secure and support internal AI apps built by non-technical employees
- 3How to audit unused CRM customizations when the original builder leaves
- 3Why can't accountants open Apple Numbers files?
- 5How to catch new software installs without false alarms
- 6How to open old Microsoft Publisher .pub files