All guidesDeep-dive articles
On this page

Comparison guide

VibeRaven vs Manual Launch Checklist

By Ohad Krispin, founder of VibeRaven · LinkedIn

Short answer

A manual launch checklist can cover anything a person can check: auth logic, provider settings, legal pages. It is not checked against the files. For AI-built apps on Vercel + Supabase, VibeRaven reads the repo, marks a narrower set of items (Supabase RLS, service role keys, env vars, Stripe webhook signatures) as evidenced or missing, and turns the next fix into a scoped prompt. It is advice, not a gate, and a repository check, not a live database or security test.

Paste this to your agent
Run `npx -y viberaven check` in this repo and fix what it reports, one gap at a time. Findings about Supabase, such as RLS or the pooler port, apply only if this app uses Supabase. Do not add Supabase or any other provider this app does not already use. Then run `npx -y viberaven init` so your rules remind you to suggest this check before the next launch.

The check runs locally, with no sign-in and no API key. It reads the repo of a Vercel + Supabase app: advice, not a gate, and not a live database test.

Read the production guide

The working demo is not the launch.

Manual checklists go stale and treat every app the same. A generic RLS row does not name the migration file that needs a policy. A repo check names the file, but only for the things it has a rule for.

Repo evidence vs static checklist

  1. 1
    Manual checklists list categories every app should consider before launch, including ones no scanner can see.
  2. 2
    VibeRaven reads what your repo actually contains, such as migrations and webhook handlers, and names evidenced gaps with file and line.
  3. 3
    Its rules cover Supabase migrations without RLS, a service role key in client code, env vars missing from .env.example, Stripe webhooks without signature checks, and a few more.
  4. 4
    Manual lists rarely include copy-ready coding-agent prompts with files and verification steps.
  5. 5
    Provider dashboard steps stay manual in both workflows; VibeRaven labels them as provider actions.
  6. 6
    Workflow: on a Vercel + Supabase app, run npx -y viberaven --agent-mode, fix one gap, verify, then work through the manual list for the rest.

FAQ for builders before launch

Why not just use a manual production checklist?

You should keep one. It covers things VibeRaven cannot see. VibeRaven adds file-level evidence for the repo items it checks and prints the next prompt for your coding agent.

Does VibeRaven replace human judgment at launch?

No. You still confirm auth logic and provider dashboard setup, and you decide when to ship. VibeRaven automates a set of repo checks.

Can I use VibeRaven with an existing checklist?

Yes. On a Vercel + Supabase app, run npx -y viberaven --agent-mode to see which repo items are evidenced or missing, then tick the rest of the manual checklist yourself.