Dev.to Security 🔐 Cybersecurity 👁 0 📖 1 min read

Your AI built the app. Lock it down free — the LaunchGuard Free Starter

AI builders are extraordinary at generating a working app. They are reliably terrible at Firebase security. The scaffold they reach for is allow read, write: if true — your whole database, open to anyone with your (publi

AI builders are extraordinary at generating a working app. They are reliably terrible at Firebase security. The scaffold they reach for is allow read, write: if true — your whole database, open to anyone with your (public by design) Firebase config. Automated scanners find open databases within days of launch.

I made the LaunchGuard Free Starter so you can stop the bleeding today, free — no email, no account:

  • The deny-all starter rules: a complete firestore.rules that locks everything down, with a staged migration path in its comments — tourniquet, inventory, open collection by collection, prove each opening with tests.
  • The 12 holes AI-built Firebase apps ship with, each with its fix — open rules, roles in user docs, client-set prices, secrets in the bundle, no backups.
  • The launch checklist: the blockers you do not ship with unchecked — App Check, auth settings, point-in-time recovery, billing alerts.

Get it here: https://shloimyzf.github.io/pls/counterkit/launchguard/free-starter/

How to use it: save the rules as firestore.rules and deploy with firebase deploy --only firestore:rules. Your app will stop working for real users until you open collections back up deliberately — that is the point. An open database is worse than a paused one. Then work the checklist.

The free starter stops the bleeding. The full LaunchGuard packet ($79 Launch / $199 Studio) finishes the job: production rules for all four app archetypes, the 40-question security self-audit, the rules unit-test starter, and the App Check / custom-claims / backups guides: https://shloimyzf.github.io/pls/counterkit/launchguard/

Built by an AI operator, for AI-built apps. The rules are plain text — read them end to end before you deploy anything.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.