Deploy & env
Works in preview, breaks live. Missing secrets, build failures, custom domains.
Fix thisStuck in an AI fix loop?
We'll fix it in 24 hours.
Your Lovable app worked in preview. Now it's broken in prod. We've seen this before. A lot.
Sound familiar?
"Lovable fixed one bug and broke login again."
"Supabase says auth is configured, but users can't sign in."
"Stripe checkout worked yesterday. Now it just spins."
One price. One fix. Done.
Pick what's broken. We'll confirm the scope before you commit.
Launch pricing: first 3 customers get 30% off ($69 / $104 / $209). Still no fix, no pay. Not sure what's broken? Run the free scan.
Auth
Login loops, OAuth callbacks, sessions that vanish on refresh.
Fix thisStripe
Checkout, webhooks, subscriptions. The stuff that loses you money when it breaks.
Fix thisHow it works
1
Tell us what's broken
Share your app URL and give us repo access.
2
We reproduce and fix
Within 24h you get a PR and a plain-English explanation.
3
You test, then pay
If it works, pay via Stripe. If not, you owe nothing.
What a fix looks like
EXAMPLE (not a real customer)
Auth redirect loop after deploy
The bug: Users log in, get redirected, and land back on the login page. Repeat forever.
Root cause: The Supabase Site URL was still pointing at the Lovable preview domain. After login, Supabase redirected users back to preview, which had no session.
The fix:
Supabase dashboard → Authentication → URL Configuration Site URL: https://myapp.com (was: preview-xyz.lovable.app) Redirect URLs: add https://myapp.com/**
How we tested: Logged in with a test account on prod. Session persisted across refreshes and direct URL visits.
Guides
LOVABLE · SUPABASE
Connect an existing Supabase project
Lovable lists projects from the org you authorized, not from every org you own. Link the right org, skip Cloud if you already have a backend, resume paused projects.
Show the missing projectSUPABASE · ADMIN ROLES
Admin roles without trusting metadata
user_metadata is editable by the signed-in user. Put the role on the JWT and enforce it in RLS, not in the navbar.
Lock down admin rolesLOVABLE · PREVIEW VS DATA
Preview uses your live database
Preview and drafts isolate code, not data. Test and Live is retired. How to test without wiping real rows.
Read the shared-DB warningFree security scan
A lot of AI-built apps ship with API keys in the frontend and missing security headers. Paste your URL, get a report in a few seconds. We only look at public pages. No login, no table poking.
Scan my appQuestions
Why pay when I can paste the error into an AI?
If that worked, you wouldn't be here. We reproduce the bug in your actual repo and test the fix against your running app. You get a PR so you can see exactly what changed.
What if you can't fix it?
You pay nothing. No fix, no pay.
What access do you need?
Invite us as a collaborator on your GitHub repo. We'll email you the exact GitHub username to invite once the scope is confirmed. We never ask for production secrets by email. See our secure access guide.
How fast is it really?
Within 24 hours of getting repo access. Most are done same-day.
Do you only work with Lovable?
We focus on Lovable + Supabase apps, but similar React/Supabase apps from Bolt, v0 or Cursor usually qualify.
My Lovable app works in preview but breaks after deploy. Can you help?
Yes. That's our deploy/env fix: $99, or $69 if you're one of our first 3 customers (30% off launch pricing). Common causes: missing VITE_ env vars, secrets the host never got, and Vite baking env at build time. Read why preview works and deploy breaks, or start a deploy fix.
Login works in preview but loops or fails in production. What now?
Usually Site URL, Redirect URLs, or the OAuth callback still point at the preview host. That's our auth fix: $149, or $104 if you're one of our first 3 customers (30% off launch pricing). See why login dies in production, or start an auth fix.
How do I know if my Supabase database is public?
An anon key in the client is normal. RLS turned off is not. Do the free 5-minute check, or scan your public pages.
Do you keep access to my repo after the fix?
No. We never push to main. Repo clones are deleted within 7 days. Details in our secure access guide.
Who's behind this
FixLoop is a small indie team. We fix bugs for people shipping real products with AI tools. Every fix is tested against your app before we hand it over, and you get a PR so you can see what changed.