Vibe Coding

An app built with Lovable, Bolt, v0, Replit Agent or Cursor usually works. The signup works, the dashboard works, the checkout works, because those are the things a prompt describes. What nobody prompts for is the configuration around them, and that is where the risk sits: whether a second user can read the first user's rows, whether a payment key ended up in the JavaScript every visitor downloads, whether the backup has ever been restored, and who finds out when it breaks on a Sunday.

1 free tool · no sign-up · no ads

Work through the non-functional checks before you launch, filtered to your stack and to the risk level you care about.

Which tool do I need?

  • Decide whether an app is safe to launch

    Work through the non-functional checks by theme, filter to critical items for the short answer, and export what is left.

    Launch Readiness Checklist

  • Answer "can we launch this week?"

    Filter to critical items only. Nine checks across data access, secrets and backups give the short answer.

    Launch Readiness Checklist

  • Take over an app someone else vibe-coded

    Run the full pass with every stack shown, then export the gaps as a Markdown worklist for the issue tracker.

    Launch Readiness Checklist

About Vibe Coding

These tools cover only that side. They do not help you build features, because the AI already did that well. They are checklists and reviews for the operational, security and durability work that turns something that demos into something you can leave running in front of real people. Everything runs in your browser, so you can work through a list about your own app without sending anything anywhere, and export the remaining items as Markdown to paste into an issue tracker.

The checks are specific rather than general advice. "Enable row-level security" is not useful on its own; knowing that enabling it and writing a policy are two separate settings, and that a table with policies but the switch off is still wide open, is what actually prevents the leak.

Frequently asked questions

What is vibe coding?

Building software by describing what you want to an AI tool and accepting most of what it writes, rather than writing the code yourself. It produces working features quickly. The gap it leaves is the configuration and operational work around those features, which is what these tools cover.

Is an app built this way safe to put in front of users?

It can be, but not by default. Most of the real risk sits in two places: row-level security on the tables holding user data, and secret API keys that ended up in the browser bundle. Both are checkable in an afternoon, and both look completely normal from inside the app.

Do these tools look at my app or my code?

No. They are checklists and calculators that run in your browser; nothing is uploaded, scanned or stored. You read each check, confirm it against your own project, and tick it. The export is produced on your device.

Which platforms do the checks apply to?

The themes apply to any app that talks to a database from the browser, which covers Lovable, Bolt, v0, Replit Agent and hand-written projects alike. Items specific to Supabase, Firebase, another hosted database or serverless functions are tagged so you can filter to your stack.

I am not a developer. Can I still use these?

Yes. Each item says what goes wrong in plain terms and what to do about it, without assuming you wrote the code. Some fixes will need help, but knowing which problems you have, and which are launch-blocking, is the part these tools give you.