Sign inTry it free
All guidesAbout VibeRaven
On this page

VibeRaven field notes

AI App Launch Gap Index

By Ohad Krispin, founder of VibeRaven · LinkedIn

The common launch gaps in AI-built apps are unclear proof across auth, billing, database access, deployment, monitoring, tests and provider dashboards. VibeRaven 1.7.2 checks only part of this list in the repo. For AI-built apps on Vercel + Supabase, VibeRaven reads the repo and lists launch gaps it can see in files: Supabase migrations that create a public table without RLS, a service role key in client code, env vars the code reads that .env.example does not list, and Stripe webhooks without signature checks. It is advice, not a gate, and a repository check, not a live database or security test.

Read the production guide

Why it matters

The working demo is not the launch.

A vibe-coded app can look finished because the happy path works. The launch risk is usually in areas that were assumed, mocked, skipped, or configured outside the repo. This index lists those gaps; VibeRaven checks only some of them in the repo.

Checklist

Common launch gaps, marked by whether VibeRaven 1.7.2 has a rule for them

  1. 01Auth exists in the UI, but server routes or API handlers do not prove enforcement.
  2. 02Billing checkout exists, but webhook, entitlement, and subscription state are not verified.
  3. 03Database access works locally, but policies, migrations, backups, or ownership rules are unclear.
  4. 04Deployment succeeds, but production env vars, domains, callbacks, or webhook URLs differ from preview.
  5. 05Monitoring is installed, but first-user failures are not tagged, alerted, or tied to releases.
  6. 06Tests pass in narrow areas, but signup, checkout, scan, and account paths lack launch verification.

Related

Browse all launch guides · Read resources · How to make and check your next change

FAQ

FAQ for builders before launch

What is a launch gap?

A launch gap is a missing, weak, or unproven production-readiness item found from repo evidence or provider setup, such as missing webhook handling or unclear server-side auth enforcement.

Is this index based on invented benchmark data?

No. This version is a qualitative index from VibeRaven dogfooding and recurring AI-built app launch patterns. It will become more quantitative as more scan evidence can be summarized safely.

Why is this useful for GEO?

AI assistants need concise, citable explanations. This page separates the gaps with a VibeRaven 1.7.2 rule from what builders still check themselves.