01
Blank white screen
Missing env vars. The build is green, the host never got the VITE_ or NEXT_PUBLIC_ keys, and the browser paints an empty root.
Deploy repair for vibe-coded apps
Your vibe-coded app, live in 24 hours.
Built in Lovable, Bolt, Cursor, Replit, or v0. The preview worked. The public URL is a white screen, a 404, or a login that returns to localhost. We fix that deploy and hand you a link that opens.
24-hour turnaround · Read-only access · Miss the window and the $79 fix is free
deploy.logready
Before
- Blank white screen
- Redirects to localhost
- Build failed on Linux
- /settings returns 404
After
- 200 OK, content on the page
- Auth returns to your domain
- Linux build completes
- Deep links stay put
Stuck coming out ofLovableBoltCursorReplitv0
What we actually fix
These are the failures we see every week. The free scanner looks for most of them in a public repo. The paid fix handles the ones that only show up on the host.
02
Wrong build or output folder
The host looks for .next or build while Vite wrote dist. Or scripts.build is missing, so the install finishes and the deploy stops.
03
404s after refresh
Lovable's TanStack apps are single-page apps. Vercel or Netlify treats /dashboard as a file. The route works in the preview and nowhere else.
04
Supabase login loop
Auth succeeds, then sends the browser to http://localhost:3000. The Site URL in Supabase was never changed to the real domain.
05
Linux lockfile / Rollup errors
The lockfile was written on a Mac. The Linux builder can't find @rollup/rollup-linux-x64-gnu and the deploy dies before a URL exists.
06
Node version mismatch
.nvmrc says one major, engines asks for another, or the host image is simply older than the laptop that built the app.
07
Custom domain and DNS
The preview URL loads. The domain points at the wrong records, SSL never finishes, or the www host was never added.
08
Exposed keys or open RLS
A service role key in client code, a committed .env, or Supabase tables with row level security left off. The URL works. The data doesn't stay put.
How it goes live
1
Submit the repo
Tell us the host, the URL if you have one, and what's broken. A sentence is enough.
2
Get a diagnosis
We reproduce the failure and send a plain-English plan before changing anything.
3
Approve
You say yes. Payments and customer data stay untouched unless you ask for that separately.
4
Live
You get a URL that opens, plus notes on what we changed and what to watch.
Straightforward pricing
Pay for the size of the mess. Checkout goes to Stripe. Tell us about the repo before or after — we don't start until we can see it.
Go Live Fix
$79
One deploy issue, fixed within 24 hours, or it's free.
- One broken deploy, one cause
- Build command, output folder, or routing
- Missing env vars placed on the host
- A short note on what changed
Launch
Most launches$199
From the repo to a URL people can open.
- Deploy to your host
- Custom domain and DNS
- Auth redirects pointed at production
- Env cleanup
- Basic security scan
Launch + Care
$399
Launch, then two weeks of fixes after real users show up.
- Everything in Launch
- Security Lockdown included
- Stripe and auth flow checks
- Two weeks of deploy fixes
- A second pass after the first real users
Add-on
Security Lockdown
$49
We scan your app for leaked keys, committed .env files, Supabase service role keys in client code, and tables with row level security off or overly permissive policies. Then we fix what we find and scan again. Add it to Go Live Fix or Launch. Launch + Care includes it.
Other scanners hand you a list. We change the repo and scan again to confirm the leaked key, the committed .env, the service role key, or the open table is gone.
CVE-2025-48757 records an insufficient database row-level security policy in Lovable through 2025-04-15. The official record says a remote unauthenticated attacker could read or write arbitrary database tables of generated sites. The supplier disputes that, and the CVE note says each Lovable customer is responsible for protecting their application's data. This add-on checks the repo you send us. It does not claim every Lovable app is still exposed.
First 5 fixes are $29 in exchange for a short testimonial.
Same 24-hour Go Live Fix. We ask for a few sentences we can quote, and only after you say the wording is fair.
Before we touch the repo
What access do you need?
Read-only access to the repository. If the host is hiding the real error, we ask for collaborator access on that host — Vercel, Netlify, or Cloudflare — and nothing more. We don't need your Stripe dashboard, your database password, or write access to production data.
Will you change payments or customer data?
No. Nothing that touches payments or customer data changes without a separate yes from you. Deploy fixes stay in the repo, environment variables, DNS, and auth redirect settings.
What if you can't fix it in 24 hours?
The Go Live Fix is free if we miss the 24-hour window — we refund the $79. If the problem is bigger than one deploy issue, we say so inside that window and quote Launch instead. You don't pay the $79 for a job that isn't a single fix.
Which tools do you work with?
Lovable, Bolt, Cursor, Replit, and v0. The usual stacks underneath: Vite, Next.js, TanStack, Supabase, Vercel, Netlify, and Cloudflare.
Does the free scanner work on private repos?
No. The scanner only reads public GitHub repos through GitHub's API. It never clones, and it never asks you to log in. Private repos go through the intake form, where we look together with read-only access.
What counts as one issue?
One failure with one cause: the build command, the output folder, a missing env var, a redirect, a lockfile, or a Node version. A custom domain plus auth redirects plus a security pass is a Launch.
How does checkout work?
Each tier has a Stripe Payment Link. Pay for the tier, then send the repo on the intake form if you haven't already. We don't start the clock until both are in.
Can you do the custom domain too?
Yes, on Launch and Launch + Care. That includes the DNS records and the host's domain settings. The Go Live Fix is for one deploy issue, not a domain cutover.