---
title: "Discussion on \"20 things to check before you launch an AI-built app\" | Hashnode"
description: "Discussion on \"20 things to check before you launch an AI-built app\". AI coding tools are very good at producing an app that works. They are much less reliable at producing an app that is safe to put on the public internet. The reason is simple: the model optimises for"
url: "https://hashnode.com/posts/20-things-to-check-before-you-launch-an-ai-built-app/6ae3a2496ffbf3070ac7e56e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [20 things to check before you launch an AI-built app](https://arknetdigital.hashnode.dev/20-things-to-check-before-you-launch-an-ai-built-app?utm_source=hashnode&utm_medium=feed)

AI coding tools are very good at producing an app that works. They are much less reliable at producing an app that is safe to put on the public internet. The reason is simple: the model optimises for

Oct 29 · 10 min read · arknetdigital.hashnode.dev  
Read the article

-   [#security](https://hashnode.com/tag/security)
-   [#webdev](https://hashnode.com/tag/webdev)
-   [#ai](https://hashnode.com/tag/ai)
-   [#nextjs](https://hashnode.com/tag/nextjs)

## Written by

[ArkNet Digital](https://hashnode.com/@arknetdigital)

@arknetdigital

  
[View profile](https://hashnode.com/@arknetdigital)

Practical AI playbooks, prompt packs and code templates for builders and small businesses.

Practical AI playbooks, prompt packs and code templates for builders and small businesses. https://veroputech.gumroad.com

## Responses 2

Markdown supported · ⌘↵ to post

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

[Oct 30](https://hashnode.com/posts/20-things-to-check-before-you-launch-an-ai-built-app/6ae3a2496ffbf3070ac7e56e/comment/6ae40466ca0d0190fc2a8f92)

The two account test for Supabase row level security is the item I would move to the top. It takes ten minutes, needs no tooling, and it is the check AI built apps fail most often, because the generated policies usually look reasonable until a second user tries to read the first user's rows.

Secrets ending up in NEXT\_PUBLIC\_ variables is a close second. The code works, the key ships to every browser, and nothing warns you.

I am glad the list includes cost caps under rate limits. With LLM features, an unprotected endpoint is a billing problem before it is a security problem, and OWASP's unbounded consumption entry exists for that reason.

The backup point is phrased well. A backup you have never restored is a hope, not a backup. For founders, I would suggest treating this whole list as one fixed hardening pass before launch, with every item either verified or written down as a known risk.

[ArkNet Digital](https://hashnode.com/@arknetdigital)

[Oct 30](https://hashnode.com/posts/20-things-to-check-before-you-launch-an-ai-built-app/6ae3a2496ffbf3070ac7e56e/comment/6ae40466ca0d0190fc2a8f92#reply-6ae4a53b0b80cc69a2d0bd24)

Thanks, agreed. The two-account test is the fastest high-value check, and catching billing problems before they become security problems is a great way to put it. Writing each skipped item down as a known risk is a good addition too.
