MoeenThe Overnight Break-In Pick your night

Give me one night to break into your app. The film is in your inbox by 9 a.m. your time, or I pay you $250.

Free for AI-built apps with paying customers. You get every way in, in plain words, with the exact fix for each one. If you can't follow it, I walk you through it. Still not clear, and the $250 is yours.

One app a night, two nights a week. The next open night is a Tuesday or Thursday. It takes no card, no password and no sales call.

The clock starts when your permission slip is signed and my test account is in, by 6 p.m. your time. One bet per app. If I can't get in, that is your result, and you get it in writing. The whole bet

Try the key

Try the key.

This is my test app, Fernhill Cleaning. The customers are invented. The database and the request are real.

So is the green check. It asks whether every table has row-level security switched on, and all three do. It never reads what the rules say.

You're signed in as Ivan, one of its customers. Your screen shows your booking, and only yours. The screen is polite.

Fernhill Cleaning Security check passed

Signed in as Ivan Alder

Your booking

Ivan Alder

70 Alder Lane

Door code 4707

One customer. One booking. Yours.

One street

How that worked. One street, and you'll never unsee it.

  1. A street of small houses at blue hour, every window lit, every door shut.

    1The lock

    Your app is a street. Every customer has a house.

    Your AI put a lock on every door. That's all the green check looked for: a lock on each one.

  2. Close on one front door. The brass plate under the lock reads: Logged-in users can view bookings.

    2The rule

    Here's the rule your AI wrote on those locks.

    Sounds right. Except every customer is a logged-in user.

  3. From above the rooftops: front doors standing open down the street, warm light on the steps.

    3The key

    So one key opens every door on the street.

    Your screen never showed it. The database only asks one thing: are you logged in?

That was one door.

20 credits for 10 paid
What happens when a payment arrives twice. In my test app, the same payment sent twice paid out twice. My test app
$4,000 in about two hours
What happens when a loop gets stuck. One founder got that bill. Public post, r/lovable, 9 June 2026

The Lock Check

Check your lock in 60 seconds.

Ask your AI one question tonight. Paste its answer here and this page reads the rule for the one-key bug. It reads; it doesn't try the door. It runs in your browser, and nothing you paste leaves it.

1Ask your AI this, word for word.

Can one customer read another customer's data? Show me the exact rule (the RLS policy) that decides it.

Or try or .

Verdict

Waiting for a rule.

Paste what your AI said. I'll read the line that decides it.

The street in deep night under a full moon. Windows dark, street lamps on.

While you sleep

The Overnight Break-In.

Free, for AI-built apps with paying customers. One app a night, two nights a week.

  1. Tonight

    Five minutes of yours.

    • Pick a night.
    • Sign the one-page permission slip.
    • Add my test account.
  2. Overnight

    I go at your app three ways.

    • As a stranger.
    • As a customer.
    • As a customer with a grudge.
  3. By 9 a.m. your time

    Four things are in your inbox.

    The Break-In Film
    A private screen recording of every way I got in.
    The Fix List
    Every hole, ranked by what it could cost you. Each fix is written as a prompt your own AI can run, and marked: your AI can close this, or this needs hands.
    The Verdict
    Would I put my own card in it? Yes, or not yet.
    Your Hold Quote
    One fixed price to close all of it, written down before you decide anything.

    From my test app. Two minutes to read.

A scan reads the locks. I try the doors.

A scan gives you a list of warnings and a green check. You've seen that check already.

A break-in gives you a film of your own app opening, the exact fix for each way in, and a person who signs what he found.

One promise. The 9 a.m. Bet.

The 9 a.m. Bet

$250

Late, or still unclear after I walk you through it: I pay you $250.

And you still get all of it.

Moeen

  1. On time. By 9:00 a.m. your time, the morning after your night, the film, the Fix List and the Verdict are in your inbox. At 9:01 with any of them missing, I owe you $250, and you still get all three.
  2. Clear. If any part of it doesn't make sense to you, tell me which part, in writing, within three days. I walk you through it within one working day, on a call or in a recording made for you, whichever you prefer. Still not clear after that: I pay you $250.
  3. Finding nothing counts. If I can't get in, the film shows what I tried, and you get a signed letter. That is a delivered night.
  4. Your side. The permission slip signed and my test account in by 6 p.m. your time, and your app up and my account working that night. If either stops, the night moves, and that isn't a miss.
  5. My side. If I have to move your night, I tell you before 6 p.m. your time and you choose the next one. I can do that once. Move it twice, and I owe you the $250.
  6. One bet per app, paid within 7 days of your message.

And if I can't get in?

Then your app held, and you have it in writing: what I tried, on which night, and that it stayed shut. Show it to your customers. There is no Fix List, no quote and nothing to buy.

Why is it free?

Finding out should be. Making it hold is the job.

Pick your night

How I work

A one-page permission slip is all it takes.

  • I use my own test accounts and never ask for a password.
  • Where I can, I prove a way in with two test accounts of my own and a count of what's exposed. If a real customer's record comes back anyway, I stop there. It's blurred in your film, and I keep no copy.
  • Nothing I find is ever published.
  • Your repo, your accounts and your keys stay yours. So does every line I write in them.

Not for apps without paying customers yet (the Lock Check is yours, free, tonight), or anyone who wants a rewrite.

The fair question

The Fix List is free. So why would you pay me?

Your AI can run every prompt on that list. It also wrote the rule that failed, and told you it was done.

  1. Somebody who didn't write it has to check it.

    Your AI stops when the work looks done. Then it checks its own work and likes what it sees. I re-run the break-in myself after every fix, until it fails.

  2. A fix has two halves.

    Shutting the door is the first half. The second is that the customer who pays you still gets in. A check that only asks “is the door shut?” passes both of these. Run it.

  3. Your AI can't sign anything.

    When a bigger customer asks how you protect their data, “my AI says it's fine” is not an answer. A dated letter with a person's name on it, and a film of every break-in failing, is. If they've sent you a questionnaire, I answer its testing questions with you.

Same door. Three rules. Run the check.

My test app again. The check tries the break-in, then signs in as Ivan, who pays.

ruleusing (auth.uid() is not null)

FAIL  a customer cannot read another customer's booking (140 rows returned)
FAIL  a customer can read their own booking (140 rows returned)

The door is open. Ivan asks for his booking and gets everybody's.

Real output from my test app, each rule run against the same 140 bookings.

At 9 a.m. you pick a road.

All three start with the same free night. The Fix List is yours on every one of them.

  1. On your own

    $0

    Your AI closes it. Checking it is on you.

    • You paste the Fix List prompts into the AI you already use.
    • It tells you it's done.
    • Whether it is, both ways, is yours to find out. So is everything the night couldn't reach.
  2. The Second Night

    $750

    Your AI closes it. I check it.

    • When your AI says done, I come back for a second night and re-run every break-in, both ways: strangers out, customers in.
    • Whatever still opens is back with you by 9 a.m., with the reason. One more re-run is included.
    • A hole marked “needs hands” I close myself: from $400 a hole, due after you've watched it fail.
    • When everything holds, you get the Hold Letter, signed and dated, with the film of every break-in failing. If a customer has sent you a security questionnaire, I answer its testing questions with you.
    • Then I keep watch for four weeks: every break-in again, every week, while your AI keeps changing things.
    • If your AI can't close it, the $750 comes off a Hold Sprint.
  3. The Hold Sprint

    $2,500

    I close it. You watch it fail.

    • I close every hole myself, in your repo. The worst one on day one, all of it inside 10 working days.
    • I go inside, where the night couldn't: the tables, rules, keys and payment paths named in your quote.
    • Half to start. The other half only after you've watched every break-in fail.
    • Anything I close stays closed for 90 days, or I close it again, free.
    What's in the sprint

After the night

The Hold Sprint.

I close every serious hole myself, in your repo and your accounts, without a rewrite.

You're not paying me to type. Your AI types faster than I do. You're paying for one person to be responsible for the result: every door found, closed, proven closed, and still closed after your AI's next change.

$2,500

Fixed, for most apps. The worst hole closes on day one, the rest inside 10 working days of getting access.

Your exact price is in your Hold Quote, fixed before you say yes. It names every break-in I close and every part of your app I go through. What I find inside those parts is included. Anything outside them is priced before I touch it.

The quote holds 7 days. After that your app has changed, and I re-test first.

I run one sprint at a time. The next open start is a Monday.

I find what the night couldn't
From outside I find the doors a stranger can reach. In the sprint I go through the tables, rules, keys and payment paths named in your quote, from the inside. On my test app that pass found a second way to be paid twice, one no customer could reach: a payment message delivered twice.
I close it without locking anyone out
Every fix is tested both ways, strangers out and paying customers in, on a copy of your app wherever your platform allows one. Where it doesn't, I change one rule at a time, in your quietest hour, with the way back ready.
I leave a test for every hole
It re-runs the break-in on every change, wherever your platform can run tests. The next time your AI says done, something checks.
I write your AI its rulebook
The Agent Rulebook: what your AI reads before it touches access or payments, so it stops reopening doors.
I put a ceiling on the bill
Spending limits and alarms on the paid services your app calls, so a stuck loop wakes you up instead of charging you.
I sign it
The Proof Pack: the before-and-after film and the Hold Letter, one dated page that says what I tried and what held. Send it to the customer who asks.

Pay on Proof

Half to start. The other half only after you've watched every break-in in your quote fail. I send you the recording. If five working days pass without a word, it stands.

Closed, or you don't pay

If a break-in from your Hold Quote still works when I'm done, I keep working at my cost for 14 days. Still open after that, and I refund the first half.

The 90-Day Hold

Anything I close stays closed for 90 days, or I close it again, free. It covers what I closed, for as long as the tests I left are still in place.

What done looks like. From my test app, after the fix: strangers and other customers are out, and the paying customer still gets in.
PASS  a customer cannot read another customer's booking
PASS  a customer can read their own booking
PASS  the same payment event twice adds credits once
PASS  an anonymous caller cannot post a payment event

Then Night Watch, if you want it. Your AI keeps changing your app. Every week I re-run every break-in against the live app and tell you what moved, with a dated note each month that you can forward. $450 a month, cancel anytime. The first month is included with a sprint started within 7 days of your report.

Who's breaking in

I'm Moeen.
I check what the AI calls done.

I break into AI-built apps, with permission, before someone does it without. I build with the same AI tools you do, and they tell me it's done too, so I check. I work alone, on one app a night, while you're asleep. That's why it's in your inbox by 9 a.m.

I won't redesign your app. I won't call it secure, because nobody honest will. I'll tell you what I tried, what opened and what held, and I'll put my name under it.

Moeen email

Questions

What founders ask me first.

Why would I pay you when my AI can fix it?

Let it. The prompts are on your Fix List, free. Then ask who checks. Your AI wrote the rule that failed and passed its own check. I re-run every break-in myself, both ways, sign what held, and keep watch for four weeks. That's the Second Night, $750. If you'd rather not touch it at all, I close everything in the Hold Sprint, and the second half is due only after you've watched every break-in fail.

What's the catch with the $250?

No catch, and the conditions are short. The permission slip is signed and my test account is in by 6 p.m. your time. Your app is up and my account works that night. One bet per app. And if something isn't clear, you tell me which part within three days, so I can walk you through it first. Then: the film, the Fix List and the Verdict are in your inbox by 9:00 a.m., or I pay you $250 and you still get them.

What if you find nothing?

Then your app held, and you get it in writing: what I tried, on which night, and that it stayed shut. That's a delivered night, so the bet doesn't pay, and there's nothing to buy. If you want it checked every week after your AI's changes, that's Night Watch.

Is it safe to let you in?

Yes. You sign a one-page permission slip first, so what I do that night is written down. I come in the way a stranger would, through your sign-up page, with my own test accounts. Where I can, I prove a way in with two accounts of my own: one reads the other's record, and I count how many more would come back. If a real customer's record comes back anyway, I stop there, it's blurred in your film, and I keep no copy. Nothing I find is ever published.

What access do you need?

For the night, the address of your app. If anyone can sign up, that's all. If sign-up is closed or paid, you add my test account. I don't need your passwords, your repo or your keys, because a stranger wouldn't have them either. For a Hold Sprint I work in your repo, on a branch you can read. Everything I write there is yours.

I'm not technical. Will I follow any of it?

You'll follow the film. You watch me sign up, ask for something that isn't mine, and get it. The Fix List is in plain words, ranked by what each hole could cost. If any of it loses you, I walk you through it, on a call or in a recording. If it still isn't clear after that, I pay you $250.

What does it cost after the free night?

Nothing, unless you want it to. The Fix List is yours to run. The Second Night is $750 and includes four weeks of Night Watch; a hole that needs hands, I close from $400. The Hold Sprint is $2,500 fixed for most apps, and your exact price is written in your report before you decide. After that, Night Watch is $450 a month and you can cancel it anytime.

What if your fix breaks something?

Every fix is tested both ways, strangers out and paying customers in, on a copy of your app wherever your platform allows one. Where it doesn't, I change one rule at a time, in your quietest hour, with the way back ready. If something I closed opens again inside 90 days, I close it again, free.

Will you rewrite my app?

No, and I won't redesign it. I close holes in the code you have, in your repo. If you want a rewrite, I'm the wrong engineer.

Why should I trust you?

Don't take my word for it. Watch the film: a real break-in on my own test app, start to finish. Run the Lock Check on your own rule. Then give me one night. It costs you nothing, and if I waste your morning, I pay you $250.

Sunrise at the far end of the street. Every door shut.

By morning

Pick your night.

One app a night, on Tuesday and Thursday nights. Pick one and tell me four things about your app. It takes a minute, and I confirm every night by email before it starts.

Your night
Built with
Paying customers, roughly

Free. I'll write to you to confirm it.

A sample morning

From my test app, Fernhill Cleaning. The customers are invented. The results are real.

From: Moeen8:41 a.m.

Fernhill Cleaning: I got in. Two ways.

The Verdict

Would I put my own card in it? Not yet.

The Break-In Film

Watch it: 6 minutes, private link. You'll see me sign up as a new customer, ask for everyone's bookings, and get them. Then you'll see me pay once and collect twice.

The Fix List

1Any customer can read every customer's booking.

Could cost you
140 home addresses and door codes, to anyone who signs up.
How I got in
I signed up, asked the database for all bookings, and got 140 of 140.
Prompt for your AI
Replace the bookings select policy with one that checks ownership: using (auth.uid() = customer_id).
Who can close it
Your AI can close this. When it says done, this is the first break-in I run again on a Second Night, both ways.

2A customer can collect twice on one payment.

Could cost you
Free credits for anyone who repeats one step. I paid for 10 and left with 20.
How I got in
I bought one pack of 10 credits, then sent the app's own “I've paid” step a second time. Balance: 20.
Prompt for your AI
Make confirm_purchase collect each purchase once: mark it collected and read it in a single step, so two fast clicks can't both win.
Who can close it
This one needs hands. It changes how payments are recorded, and a fix that is nearly right stops crediting people who paid.

What held. A stranger with no login cannot collect a purchase or post a payment event. I tried both.

What I couldn't reach from outside. The payment messages your payment provider sends, and the rules on your other tables. That's the inside pass.

Your Hold Quote

$2,500, fixed.

The Hold Sprint. I close holes 1 and 2, and I go through bookings, customers, purchases and the payment functions from the inside. What I find in those is included. Worst hole on day one, all of it inside 10 working days. Half to start, the other half after you've watched both break-ins fail.

Or $1,150.

The Second Night, with hole 2 by hand. Your AI closes hole 1. I close hole 2 myself. Then I run both again, both ways, sign your Hold Letter and keep watch for four weeks.

Both prices are good until seven days from today. The Fix List is yours whichever you choose.

Moeen

Pick your night

A sample Hold Letter

Written from my test app, Fernhill Cleaning. A real one carries your app's name, your dates and a link to your film.

What I tried, and what held.

The letter

On the night of 10 November 2026 I tested Fernhill Cleaning three ways: as a stranger, as a customer, and as a customer acting in bad faith. I found two ways in.

Scope
The live app, from outside: with no login, and with two customer accounts of my own.
Method
By hand. I tried to read, change or take what each of those should not be able to.
Finding 1
Any customer could read every customer's booking. Closed 12 November.
Finding 2
One paid purchase could be collected more than once. Closed 12 November.
Re-run
On the night of 13 November I ran both again, from outside, on the live app. Both failed. Paying customers could still read their own bookings and collect their own purchases.
Evidence
A film of both nights, on a private link I share with the person you name.
Not covered
Anything I did not try, and anything changed after 13 November.

This letter says what I tried and what held on that date. It is the record of a test, with my name on it. It is not a compliance certificate, and I won't call any app secure.

Moeen

What it answers when a customer asks

“Has an independent party tested the application in the last 12 months? Give the date, scope and method.”
Yes. The letter gives the nights, the tester, what was in scope and how each attempt was made.
“Can one customer access another customer's data?”
Tested. Finding 1, the date it was closed, the date it was run again, and the film of it failing.
“How are vulnerabilities remediated and re-tested?”
Each finding carries the date it was closed and the date it was run again by someone who did not write the fix.
“How often is testing repeated?”
Weekly while Night Watch runs, with a dated note each month.

If a customer has sent you a questionnaire, I write these answers with you. This is a tester's record with a name, dates and a recording. It is not a compliance certificate such as SOC 2, and I don't present it as one.

Pick your night