Stuck on a temporary URL (*.lovable.app, *.vercel.app).
● If you built it with Lovable · Claude Code · Cursor · Antigravity · Codex (ChatGPT) · Gemini
Your AI-built site — is it safe to launch.
Built with AI? I get you unstuck,
and before launch a developer goes carefully through 12 areas.
Free scan — just paste the URL
1-minute scan / full report by email (web view) / no payment
- 1 Paste the URL and you'll see results here within a minute
- 2 Leave your email and I'll send the full report
- 3 Want a quote? Reply to that email, or use the contact form below
Scanning
What we can see right now
This only covers what can be seen from outside. The 8 areas that need an inside look are covered in the pre-launch check.
0MUST
0SOON
0NOTE
The full report goes out by email and opens right in your browser.
Report link sent.
Check your inbox. If you want a quote, reply to that email or use the contact form.
— what you get back after a pre-launch check (sample report)
🔴 Fix 3 things
and you can launch.
All three are same-day fixes. The rest can wait until two weeks after launch.
0MUST
0SOON
0NOTE
Tools: Lovable + Supabase · sample
- 01Row-level security (RLS) is offNo symptoms — anyone can open other users' data by editing the URL · Add 3 policies
- 02OpenAI key is in the browser bundleA surprise bill one day · Move it to a server function and rotate the key
- 03Running on a temporary domain (*.lovable.app)The temp URL ends up on your cards and ads · Connect the domain and unify www
- 04Contact form has no spam protectionHundreds of spam a day · Add Turnstile
- 05No error loggingYou only find out when a customer says "it's broken" · Sentry free plan
01
Sound familiar?
It's almost done, but it won't deploy.
Login or the database suddenly broke.
Pasting the error into the AI doesn't fix it.
It runs, but you're not sure it's safe to open.
You'd like someone to look before real customers do.
You added payments and can't tell if money arrives.
Not even sure whether it's a test key or a live key.
02
"It works" and "it's safe" are different things
What the AI built
Sign up and you see your order list. There's a login screen. It works.
What you actually need
Changing the number in the URL must not show someone else's order. This never shows on screen — you have to try it.
In 2025, 170+ apps built with one AI builder exposed user data. Not the tool's fault — nobody checked once before launch.
03
The 12 areas we check before launch
I collected where AI-built sites actually broke, and it came to 12 areas. Eight of them can't be seen on screen, so I check them inside the project.
Needs an inside look · 8In the pre-launch check I read the code and click through
01Data permissionsWhether other users' data can be exposed
02Keys in the browserWhether API keys or secrets sit in client-side code
03LoginWhether sign-up, password reset and logout work and can't be bypassed
04PaymentsWhether the server verifies amounts, and whether a test key is live
05Forms & uploadsWhether inquiries actually arrive and spam or risky files are blocked
06Deploy & operationsWhether backups and error alerts exist, and whether you own the project
07Transport & certificateshttps enforcement, certificate expiry, security headers
08AI featuresWhether there is a spending cap, and whether personal data stays in chat logs
Visible from the outside · 4In the free scan the Ller scanner goes first
09Speed & mobileWhether it's slow or shifts around on a phone
10Search & sharingSearch indexing and link previews when shared
11Legal pagesWhether privacy policy, terms and business details are published
12PlaceholdersWhether lorem ipsum, sample phone numbers or dead menu links remain
Things visible from outside, like temp domains and https, are scanned as well.
04
Pricing
01 · UNBLOCK
Unblock one issue
₩110,0001 day · 1 revision
When the deploy fails, the domain won't connect, or the database or login throws errors. One stuck problem, solved.
- ✓ I find the cause and fix it (no rebuild)
- ✓ I add a rule to your AI rules file so it doesn't happen again
- ✗ The 12-area check isn't included
≈ 1 hour internally
02 · CHECK + FIX● Most chosen
Pre-launch check + fix
₩330,0004 days · 2 revisions
When you're not sure it's ready to launch. I go through all 12 areas and fix the 3 must-fix items myself.
- ✓ 12-area check — I read the code and click through
- ✓ 🔴 3 must-fix items fixed and deployed (₩55,000 per item beyond 3)
- ✓ Report — symptom, cause and fix for every item
- ✓ AI rules file — set up so the same problems don't come back as you keep building with AI
≈ 4–5 hours internally
03 · PRODUCTION
Production ready
₩990,00010 days · 3 revisions
When real customers are about to arrive and you're worried it dies quietly. Check and fix, plus the operational safety net.
- ✓ Everything in Pre-launch check + fix
- ✓ Automated DB backups, verified all the way to a restore
- ✓ Uptime monitoring, and I watch it myself for 2 weeks
- ✓ Error logging with alerts, and a deploy pipeline (CI/CD)
- ✓ Spam protection on your forms (Turnstile)
- ✓ Separate dev and prod environments where needed
- ✓ Two weeks of free support after launch
≈ 12–15 hours internally
Why this price · 1The price list is the default
It can change with the size or structure of your site. If so, I let you know before we start and we agree on it first.
Why this price · 2I don't sell checks alone
A report that says "there are problems" is useless if nobody fixes them. That's why ₩330,000 includes the fixes. Abroad, a check alone currently runs $500–1,500.
Why this price · 3We agree the scope first
We decide how many items and how far before I start. Beyond 3 fixes it's ₩55,000 per extra item, and anything bigger we discuss separately.
VAT included · bank transfer, Kmong or Fiverr · invoice available · if the same cause breaks it again within two weeks, I fix it free · code is deleted after the job and you get an NDA
05
How it works
01 · FreeFree scan
Paste the URL and results come back within a minute. Leave your email and I send the full report.
02 · TogetherAgree the scope
We go through the report together and decide how far to go.
03 · WorkCheck & fix
I check the 12 items myself, read the code, fix what needs fixing and deploy.
04 · DoneHandover
I confirm the site runs well and hand over the report, a log of every change, and an NDA.
06
Contact
A few lines is enough.
What you built it with, and where you're stuck.
- 01I read every message myself and reply by email
- 02If you want, we agree a quote and the scope together
It's fine to take the free scan and stop there.
07
FAQ
Does it matter what I built it with?+
No — any language or website builder works. Each tool has its own typical failures, so tell me what you used and I get to it faster.
Do you need my code? Do you keep it?+
I do need to look at the project to fix things properly. Everything is deleted when we're done, and you get an NDA as well.
Do you guarantee security?+
I can't promise perfect security. What I do is find and fix the things that would actually cause problems right now. That's different from professional security work like penetration testing.
What if there are more than 3 must-fix items?+
Three are included, and each extra one is ₩55,000. We agree the count before I start.
What if it breaks again?+
If it's the same cause within two weeks, I fix it free. A different cause is an Unblock job.
What if you say it needs a rebuild?+
The report explains why, and I lay out three options: partial fix, rebuild, or launch as-is with the risk spelled out. Rebuilds are quoted separately.
Invoice?+
Yes.
Do you help after launch?+
Production ready includes two weeks of questions and fixes after launch. If you want ongoing maintenance after that, just say so.
Just send
the URL.
The scan takes a minute and the report comes by email. Quotes only when you ask.