What gets fixed
- Login, sign-up and OAuth redirects that work in preview but fail on the live domain
- Supabase: row level security blocking inserts, keys exposed in the client, storage rules, slow queries
- Stripe checkout and webhooks that never fire
- Deploys on Vercel or Netlify, custom domains, environment variables, transactional email
- Features the AI keeps breaking every time you prompt it again
How it works
- Send a link and two sentences about what is broken, by email or WhatsApp
- You get a fixed price within a day: no hourly billing, and if the job turns out bigger you hear it before any extra work
- The fix goes into your repo with a short note on what was wrong, so it stays fixed
- Quick fixes and audits are paid after you see them working; builds are half up front, half on handover
Why not just prompt the AI again
AI builders often loop on the same bug because they never see the real cause: a redirect URL in the auth settings, a missing policy, an environment variable that only exists in preview. Reading the code and the logs finds it once, properly.
Related guides
Quick answers
What access do you need?
Usually access to the repo as a collaborator and to the Supabase or hosting project. Lovable and Bolt projects can be connected to GitHub in a couple of clicks.
Who owns the code?
You do. Everything goes into your repo and your accounts, nothing is locked to us.
Can you keep working on it after?
Yes. Many fixes turn into a small monthly plan for changes and keeping things running.