I will fix and launch check your lovable bolt or cursor app


About this gig
- Built your app with Lovable, Bolt or Cursor, and now it breaks for real users? I fix the parts AI tools get wrong and re-test on your live URL.
What I fix most:
- Login works in preview but loops or fails on your domain
- Supabase access rules: users see data that is not theirs, or get "permission denied"
- Secret keys sitting in the browser bundle
- Stripe checkout and webhooks that do not unlock access
- Build and deploy errors, environment variables
- Custom domain, HTTPS and sign-up email (SPF, DKIM, DMARC)
How it works:
- You send a short written form (plus repo access for Standard and Premium).
- I reproduce the problem and tell you the cause in plain English.
- I fix it in a branch or pull request, one commit per fix.
- I re-test on your live URL and send the evidence.
Basic: live-app scan plus the top 1-2 fixes. Standard: ONE problem fixed in your code. Premium: full 12-point launch check, report, and fixes for all Critical and High findings.
Everything is written, inside the order. No live sessions, no production secrets needed.
Not included: new features, redesigns, rewrites, app store submission, compliance certification.
Get to know Jean
AI Automation and Full Stack Developer
- FromBrazil
- Member sinceMar 2024
Languages
English, Portuguese
My Portfolio
FAQ
Which tools and stacks do you work with?
Apps built with Lovable, Bolt or Cursor. Usually React, Next.js or Vite with Supabase, Firebase or Postgres, and Stripe. If your stack is outside that, I will tell you in my first reply, before you order.
Do I need to give you my passwords or secret keys?
No. I need read access to the repo, your live URL and a test account. Never paste keys in the chat. If a key was ever shared in a chat or committed to the repo, I will tell you to rotate it.
Will you touch my live data?
Not without asking. If you have a staging copy, I use it. If not, I ask for your OK before any change that affects live data.
Can you guarantee my app is secure?
No one can. The report covers the listed checks on the date tested, with evidence. It is not a penetration test or a compliance certification.
What if you cannot reproduce my problem?
On Standard, if I cannot reproduce it within 48 hours of getting access, I cancel the order for a full refund through Fiverr. On Basic you always get the written scan result.
How do we communicate?
In writing, inside your Fiverr order: order messages, a report and code changes. This keeps the cost low and gives you a record of every change.
Can you add features or redesign the app?
Not in this gig. Order only what is broken or unsafe. I can reply with a scoped quote if you need more.
How do I describe the problem so it is fast?
Send the exact error text from the browser console or build log, what you expected, and the last change you made.
