VibeRaven

VibeRaven for teams

For companies, agencies and teams shipping AI-built apps on Vercel + Supabase: we set VibeRaven up with you on every repo, add the GitHub Action, race-test your database rules with two users at once on real PostgreSQL (the same free, open-source npx -y viberaven race you can run yourself), and send the findings to your coding agents. You work directly with Ohad Krispin, who builds VibeRaven.

How we work with you

  • Tell us about your apps: your repos, your stack, and who ships.
  • We set it up together: checks on every repo, the GitHub Action, and race tests on your database rules, with two users at once on real PostgreSQL. The race test is the same free, open-source npx -y viberaven race you can run yourself.
  • Your agents keep it running: findings go to your coding agents, and we review what matters with you.

What we check

  • Tables without row level security, and policies that let anyone read, update or delete.
  • Database rules tested with two users at once, on real PostgreSQL.
  • Service role or secret keys reaching the browser, and security definer functions anon can call.
  • Stripe webhooks without a signature check, and env vars that differ between environments.

What is not included

  • No penetration test, no live attack and no compliance certificate.
  • No access to production databases unless you give a read-only Supabase connection.
  • The fixes themselves, which are quoted separately.

Limits

VibeRaven is advice, not a gate. Without a read-only connection it is a repository check, not a live database or security test, and a clean report does not prove an app is secure.

What does it cost?

We agree on it together after a first call, based on your team and your apps.

Why does this matter?

In 512 public Lovable repos we read, 1 in 6 let signed-out visitors update or delete a whole table.