Rescue Audit · fixed scope · fixed price

Rescue Audit for Lovable, Bolt and Cursor apps on Supabase. $99, 72 hours.

A backend engineer goes around your UI and talks to your database, auth and Stripe webhook the way an attacker would. You get a ranked report: what leaks, the request that proves it, and the fix.

Sample report · Folioport · ranked findings4 of 11
  1. F-01Anyone with the public key reads every agency's invoices and client emailsCritical200 before, now 401
  2. F-02The service_role key ships in the JavaScript bundleCritical2 keys before, now 0 keys
  3. F-03A client contact marks her own invoice paid, for $1, from the browser consoleCritical200 before, now 0 rows
  4. F-04A forged Stripe webhook marks an unpaid invoice paidCritical200 before, now 400

Each row opens into the request, the response and the fix. See finding F-04 in full

  • $99fixed, launch price
  • 72 hfrom access to report
  • Read-onlyaccess, your own test accounts
  • Creditedin full to the sprint
  • 1 dayreply time, business days

You probably need this if…

  • Your app has real users, or real payments, or launches this month.
  • You switched off RLS, or used the service key, to get past an error.
  • Stripe “works” but you’ve never tested a duplicate or forged webhook.
  • Users of different companies share one database.
  • The builder’s security scan passed, and you’re not sure what it checked.
  • You’ve been in a fix-one-break-two loop with the AI for days.

From a free leak test to $149 a month, priced before you start

Start free, or start with the $99 audit. Every sprint gets a fixed quote from the audit before any work starts, and the audit fee counts toward it. Anything outside these is $30 an hour.

Launch pricing: these prices hold for my first five reviewed clients, then go up.

Rescue services compared: price, time, what you get and what is not included
ServicePrice and timeWhat you getNot included
Free leak test + checklistDownload leak-test.mjsPrice and timeFree10 minutes, you run itWhat you get
  • Two-user RLS leak test you run on your own project: one file, Node 20+
  • The 28-point checklist
17 KB · Node 20+ · nothing to install

SHA-256 (check it with shasum -a 256 leak-test.mjs)e37d63692a0ed0071a2bc2861c80d8f4ff2c6986080e499685aa75cb3b158828

Run it against a project you own
node leak-test.mjs --i-own-this-project \
  --url https://<ref>.supabase.co \
  --anon-key <publishable key> \
  --user-a a@you.dev:pass \
  --user-b b@you.dev:pass
Not includedStorage, Edge Functions and webhooks (it checks tables and functions)
RecommendedRescue AuditBook the Rescue AuditPrice and time$99fixed, credited in full to a fix sprintWritten report within 72 hoursWhat you get
  • RLS policy review and a two-account leak test
  • Secrets and key exposure
  • Stripe webhook signature and idempotency
  • Auth flows and server-side checks
  • Error handling and rate limits
  • Ranked report in plain language, with a fix per finding
  • 30-minute call
Not includedCode changes (that’s the sprint)
Fix sprintAsk about a fix sprintPrice and timefrom $600typically $600–1,500, a fixed price quoted from the audit1–2 weeksWhat you get
  • Everything the audit found, fixed
  • RLS rewrite with leak tests in CI
  • Server-only keys, verified idempotent webhooks
  • Auth hardening and error tracking
  • Migrations workflow, staging and production split
  • Handover doc
Not includedNew features and redesign (quoted separately)
CareAsk about CarePrice and time$149per month, cancel any timeOngoing, up to 4 h of fixes a monthWhat you get
  • Monthly security re-test with the leak test
  • Dependency and Supabase upgrades
  • Alerts to you
  • 1-business-day response
Not includedLarge features

How the 72 hours work

  1. You share read-only access

    Repo link, Supabase project URL and anon key, and two test accounts.

  2. I test from outside first

    Like a stranger with your public key, then as each test account. Then I read the code.

  3. Report and a 30-minute call

    Within 72 hours: every finding ranked, with the request that proves it and the fix.

  4. Fix it, or have it fixed

    Do it yourself from the report, or I fix it in a fixed-price sprint. The $99 counts towards it.

A finding, as it appears in your report

This is finding F-04 from the Folioport case study. Each finding in your report has the same parts: what an attacker needs, the exact request, what came back, and the fix. Switch to After to see what the fixed version answers.

Read the other ten Folioport findings

Finding F-04, severity Critical.

A forged Stripe webhook marks an unpaid invoice paid

An attacker needsThe webhook URL. No key, no login, no signature.

Requestas sent to the before app
POST /functions/v1/stripe-webhook
Content-Type: application/json

{"id":"evt_forged_0001",
 "type":"checkout.session.completed",
 "data":{"object":{"amount_total":0,
   "metadata":{"invoice_id":"e3f4828b…"}}}}
Response from
200 OKLeaked
{"received":true}

# then GET the invoice:
[{"number":"NLS-1019","status":"paid",
  "total":5580,"paid_at":"2026-11-22T16:05…"}]

What leaked: NLS-1019 ($5,580) went from sent to paid with a $0 payment row, and the client was emailed a $0 receipt.

400 Bad RequestFixed

Hardened route: POST /api/stripe/webhook, same body, no or fake signature

{"error":{"code":"invalid",
  "message":"Webhook signature verification failed", …}}

Why: The signature is checked on the raw body before anything is parsed. NLS-1019 stays unpaid.

Fix: The webhook verifies Stripe-Signature on the raw body before it parses anything, then compares amount and currency.

Failure mode FM7, FM8Transcript, before: evidence/before/fm07-forged-webhook.mdTranscript, after: evidence/after/f-04.md

Who does the audit

I’m Jagrit Vats, a backend engineer. At work I build Java/Spring services on Kafka. On the side I run TeamTakes, a live multi-tenant Supabase app with RLS and a cross-tenant leak test in CI. I don’t redesign your product into something new; I make the one you built safe to put in front of customers.

What the free scanners check, and what they don’t

Supabase’s Security Advisor and Lovable’s security scan are worth running, and I start from them. They check configuration. They don’t act like a customer, or like a stranger.

Security Advisor and the builder’s scan

  • Is RLS switched on for each table?
  • Does each table have a policy?
  • Are views or functions marked SECURITY DEFINER?
  • Are foreign keys indexed?

What this audit adds

  • Signs in as two customers and tries to read each other’s invoices
  • Forges and replays a Stripe webhook
  • Calls your Edge Functions without a token
  • Edits prices, roles and statuses from the browser console

Questions founders ask before booking

Do you need my production database?

No. Read-only access to the repo, the project URL and public key, and two test accounts. A staging copy is better if you have one.

Will I have to stop using Lovable?

No. Fixes go into your GitHub repo in the same stack. Lovable keeps syncing.

What if you find nothing?

Then the report says so, with the requests I tried. You still get the checklist review and the call.

Do you sign an NDA?

Yes, a mutual NDA is standard.

Can you fix things too?

Yes: a fix sprint from $600, at a fixed price quoted from the audit. The $99 is credited. Anything outside a sprint or Care is $30 an hour.

What’s not covered?

Storage of regulated data (HIPAA, PCI scope), penetration testing of your hosting provider, and native mobile apps.

How do I pay?

Invoice by email, card or bank transfer. Half before, half on delivery for sprints.

Send the URL of your app and what it’s built with.

I reply within one business day with a start date and a payment link. Or write to rescue@jagritvats.com directly, or see more of my work at jagritvats.com.