Back to Free Tools

Vibe-Code Production Readiness Grader

Built an app in Lovable, Bolt, Cursor, or Claude Code? Check off what you have verified below to score launch readiness (0–100), expose hidden security risks, and export your prioritized fix list.

12 Engineering Checks Zero Login or Email Gate Shareable URL & Markdown Export
Verified: 1 / 12 Checks

Security & RLS

0 / 3 passed

Payments & Auth

0 / 4 passed

Data & Reliability

0 / 3 passed

Ownership & Deploy

1 / 2 passed
Production Readiness ScoreHigh Production Risk
6/ 100

Critical blockers remaining: 4 (blocks safe launch)

Fix Critical Exposures Before Opening Public Payments

Your prototype has severe database, secret-key, or webhook exposure. Hand the repo to senior engineers for a 2–4 week hardening takeover before launching to paying users.

Top Fixes to Ship First (11)

PostgreSQL Row-Level Security (RLS) enabled on every public table

Run ALTER TABLE <name> ENABLE ROW LEVEL SECURITY and add tenant/user_id scoped USING (auth.uid() = user_id) policies.

Zero service-role or admin API keys inside client bundles

Audit client JS chunks and env prefixes (NUXT_PUBLIC_ / VITE_ / NEXT_PUBLIC_) and move privileged calls to server endpoints.

Cross-tenant isolation tested with two separate user accounts

Verify GET, PATCH, and DELETE endpoints return 403/empty results when invoked using another authenticated user token.

Stripe webhook signatures verified server-side from raw request body

Verify stripe.webhooks.constructEvent(rawBody, sig, webhookSecret) on a dedicated server route before granting access.

Payment fulfillment and credit grants are idempotent

Store processed Stripe event IDs with a unique database constraint so retries exit cleanly without double-provisioning.

Production OAuth & magic-link redirect URLs pinned away from localhost

Pin exact production callback URLs in Supabase/Auth config and verify magic links end-to-end on mobile and incognito.

Server API routes validate schemas, rate limits, and payload sizes

Enforce Zod/runtime schema checks, payload caps, and per-user/IP rate limiting before triggering expensive backend work.

Database changes live in versioned SQL migrations with foreign-key indexes

Export reproducible SQL migrations and add B-tree indexes on user_id, organization_id, and high-traffic filter columns.

Transactional emails & auth links send from custom domain (SPF/DKIM/DMARC)

Connect Resend or Postmark with verified SPF, DKIM, and DMARC records on your custom domain.

Server logs and unhandled client errors captured with alerts

Wire Sentry or structured server logging across Nitro/Next API routes and payment handlers.

Custom domain SSL, Terms/Privacy links, and funnel event tracking active

Publish privacy/terms pages, verify SSL on apex + www, and track signup/checkout conversion goals.

Frequently Asked Questions

Why can an app with 70% checks still land in the High Risk band?+

If two or more critical security gates fail—such as disabled PostgreSQL RLS or exposed service keys—your raw UI checklist progress does not protect live user data from public dumping.

Does this audit transmit or store my source code or answers?+

No. Every check and report export runs 100% client-side in your browser, with optional compact URL bitmask sharing.

How long does it take Tessellate Labs to clear a failed audit?+

Most AI-generated Lovable, Bolt, or Cursor applications pass full RLS hardening, webhook idempotency, and production deployment in 2 to 4 weeks under our $5,000 Vibe-Coding Rescue Sprint.