Who owns AI-built apps when nobody knew they existed?

November 18, 2026 5 answers
Asked by 5y~copperfunnel_367

Non-engineers can now build useful internal apps quickly, but what happens when one becomes business-critical and breaks? How are teams finding these apps and deciding who supports them?

Answers

r.731+clayferrule

Start with an inventory, not an assumption that everything lives in a code repository. Ask teams what tools they depend on and check what you can see in hosting accounts, identity systems, integrations and API access.

For each app, record its business owner, technical contact, hosting account, data sources and what happens if it stops working. A dashboard that quietly writes to a sales system deserves a different level of attention from a disposable prototype.

_n59!fuzzle.2:

Personal hosting accounts are worth checking for too. The app may still be running even after the person who set it up has left.

Reply to this answer
2w+traxivo_647

The team getting value from the app should own the business outcome. That doesn't automatically mean they can fix every bug, though. Agree on who handles support, security reviews and changes before treating it as a supported service.

If engineering is expected to take it over, make that an explicit handoff with time allocated for it. Discovering an app during an outage is a rough way to inherit one.

Reply to this answer
_z81!quavelo.2

Check credentials and data access early. An app using a broad service key or writing directly to shared systems can cause trouble even when the screen looks fine. Key rotation can also expose dependencies nobody documented.

Contain risky access and review what the app reads and changes. An isolated environment can give teams room to experiment without giving every experiment the same access as a production service.

Reply to this answer
_j39~quorvex.7

A working demo can be a really good way to show engineering what a team wants. Just don't confuse the demo with a maintainable production app. Use it to clarify the requirements, then decide whether to rebuild it, harden it or leave it as an experiment.

Tivnexa-3d:

That distinction helps with expectations too. A prototype handoff isn't the same thing as an agreement to support the original app indefinitely.

Reply to this answer
2k!frostladle_493

The security response will depend on the company and the data involved. Some environments may treat an unauthorized app as a serious compliance incident, while others may focus on bringing it under existing controls. Either way, have a route for people to disclose what they've built without making discovery harder.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions