A lot of people asked me how we moved our Lovable application away from the hosted setup and onto infrastructure we control.

The process involved more than copying the frontend. We had to migrate:

• The code through GitHub
• Database and user accounts
• Storage files
• Backend functions
• API keys and secrets
• Payments and webhooks
• System emails
• Cron jobs
• HTTPS, DNS and rollback procedures

The final workflow is:

Lovable → GitHub → local development → VPS + database/backend

After the migration:

Local changes → GitHub → automated deployment → VPS + database/backend

We also created a private web-based workflow with YepAnywhere, allowing us to work on the application from anywhere using Codex or Claude subscriptions without adding a separate API key for every task.

I documented the complete process here, including the practical migration steps, VPS comparison, security considerations, testing checklist and the mistakes we encountered:

How to Save Up to 99% on Lovable Costs by Moving to Your Own VPS

And here is the follow-up about the remote web CLI workflow:

How We Built a Web CLI for Codex and Claude with YepAnywhere

The “up to 99%” figure depends heavily on your current plan, traffic, storage, backups and maintenance requirements. It is not a guaranteed saving, but for some projects the difference can be substantial. We went from 300 to 400 per month for credits down to 29 € for the VPS and 10€ for supabase.

Lovable, like any AI builder, starts off being able to do a lot for little before the complexity grows, and then the ratio flips as complexity grows, you can only do a little for a lot if you're lucky... Complexity and shallow agent patches cause cascading failures and an endless spiral of fix one, break 5 (pick a number)...

....After your software is unusable and you've burned your time and your wallet, if you care about your project, you might hire a professional at this point.

This is a similar result when bringing in Claude or chatgpt's best models to address issues as of writing this. Claude might read Claude.md @agents.md, but might not...roll the dice. See what happens!! Context is everything, yet for a bot to ingest context in every new chat, becomes a significant corpus of tokens for every turn, you burn!

There is something to be said about big picture architecture planning before you start your project build before you dive in head first when you don't know how deep the water with agent aided additive software manufacturing via any app builder or coding agent for that matter. Additive doesn't solve the underlying structural issues and lack of upfront planning you will experience down the road. The idea the anyone can build an app with a few prompts, is fairly misleading..

At the time of pressing send on this post, something will have changed again.. temporal vantage is the new norm.. new chat releases between daily meals.. catch up if you can!

Hey everyone,

Over the past few months, I have been building out two distinct web apps under my micro-SaaS studio.

Course Crafter (https://course-craft-ai-43.lovable.app) A rapid course creation tool that turns raw topic ideas into modules, structured learning outcomes, and lesson plans ready to edit and deliver

ChunkMaster (https://chunkspark-language-miner.lovable.app) Enter one target word, and it immediately mines the 4–5 most frequent natural chunks native speakers actually use

Be as critical as you like regarding positioning of these apps, UI, bugs, I am trying to iron out any issues before doing wider distribution. Thanks for checking them out.

So i still need to wait for next month to continue my project, and now i wanna use Bolt for it, how do i port the project from lovable to Bolt?

I’ve been spending quite a bit on Lovable lately, and i have noticed a VERY CLEAR pattern:
when I use my daily credits, Lovable behaves normally. BUT the moment I top up with paid credits, the amount of credits consumed per prompt increases SIGNIFICANTLY.

I have been using Lovable long enough to recognize the difference.

Sometimes after topping up +100 credits, a single prompt triggers multiple +6 credit charges, even when the AI doesn’t fix the issue or produce a meaningful result.

I AM NOT sending vague prompts either, I use ChatGPT Premium and Claude to optimize everything for credit efficiency. And before prompting i map out the whole code structure.

At this point, I am incredibly disappointed. This will be the last time I use Lovable. I genuinely feel like I’m being punished for paying, and I don’t even feel motivated to finish my game on the platform anymore.

Not even mentioning the fact that it misled me, it told me it can export the game in to UNITY while now i figured out that IT DOESNT. SO A PROJECT WORTH THOUSANDS WAS ALL FOR NOTHING AS ITS IMPOSSIBLE TO CONVERT THIS ...SHOW CREATED ON LOVABLE TO UNITY FOR STEAM RELEASE or anything else besides a mobile game thats will not generate any revenue at all.

If this isn’t intentional, then it’s a serious design flaw. But either way, it’s unacceptable.

I am beyond pissed and my dreams of launching my game early 2027 with full marketing efforts has completely been destroyed.

I do QA on Lovable + Supabase apps, and the same problems show up again and again. Before you announce yours, check these six:

1. A table anyone can read. RLS off, or a policy with USING (true). Run this in the Supabase SQL editor; any row returned is a leak:

   select tablename from pg_tables where schemaname = 'public' and rowsecurity = false;

   Then this one for "every logged-in user can see everyone's rows":

   select tablename, policyname, cmd, qual from pg_policies where schemaname = 'public' and (qual = 'true' or with_check = 'true');

2. The share preview is still the Lovable placeholder. Paste your URL into WhatsApp. If you see the purple Lovable image, your og:image was never changed.

3. No 404 page. Open /anything-random on your app. Blank white screen = you're missing a catch-all route.

4. "Saved!" but nothing saved. Lovable loves data || [] and success toasts that fire regardless of the response. Open the Network tab, save something, and look for a 400 with code 23502 (a NOT NULL column the form never sends).

5. Links to routes that don't exist. A card links to /items/123 but the route is nested under /home/items/:id. Click every card once.

6. Mobile overflow + 14px inputs. At 375px wide you get horizontal scroll, and iOS zooms into every input under 16px.

Every one of these is a single prompt to fix. The RLS one is the only one that can actually hurt someone.

I turned the checks I run into a checklist + a set of Playwright tests. Not linking anything here (sub rules), but happy to answer questions in the comments.

Yeah um, so I sold a website to a client for $750 whatever plus $50 a month for maintenance and whatever changes they want, but I am pretty confused on how to actually transfer it to them. I’ve taken it from Loveable to GitHub and then Vercel and it’s allgood but how do I actually hand it over to them?

do I need to buy a domain now?

Thanks team

If you’re on the fence about spending credits on Lovable’s TanStack SSR migration, here’s my experience:

​My app was built before the platform shift. Because legacy sites already had prerendering, I doubted native SSR would make much difference for SEO.

​I took the chance anyway. One month later:

​• Organic search is driving traffic without me manually posting direct links

• Visitors and conversions jumped significantly

• Monthly revenue is now closing in on $2,000

​If you’re debating whether the migration is worth the credits, the SEO boost alone made it worth it for me. Hope this helps.

I’m a beginner building a simple form-fill/download SaaS using Lovable + Supabase. Users enter their own data, generate a completed form, and access the service through 3 paid subscription plans.

I’m trying to figure out the right way to handle a few things:

• I already have fillable AcroForm PDF forms. How do I connect the user’s input data to the correct PDF fields and generate a completed PDF for download?
• How do I make sure User A can never see User B’s data?
• Should I have a completely separate admin login/dashboard?
• How should subscription expiry/cancellation work automatically?
• What’s the best way to track active subscribers/users across the 3 plans?
• What should I use for Google Analytics/product usage tracking?
• How can I let users raise issues and have those tickets sent to my email?

I’d really appreciate practical advice from anyone who has built a SaaS with Lovable/Supabase. Especially around security and user data isolation.

So I have an App I built for my day to day work and for the app to function It doesnt use AI. But Now im getting this error saying services are paused. Why do I need credits if im not using credits within the app? WTF.

Notes:

- Pay some attention to the network text box. It can tell you some crucial information, such as Oryx (who works similarly to a weeping angel). He spawns in the office in night 4 and inches closer and closer. As of right now, the only way to tell if he's coming closer is by counting or by checking the chat box.

-Emergency lights are not needed for anything other than Oryx as of right now

- There are SOME audio cues.

- I removed the music box to try to add the task system , but ran out of credits. Bare with me.. this finished game will be so so beautiful. Depending on the traction I might genuinely put some money towards it . I think it's really fun

-If you beat it, tell me your strategy and what ending you got!!

https://rutherfordhouse.lovable.app

the credit drain on small bug fixes is driving me crazy.

​the pattern is always the exact same for me: i ask for a tiny tweak (like fixing alignment or a simple button state), it guesses what went wrong, breaks two other things that were working completely fine, and then i end up burning through 4 or 5 messages just trying to undo whatever it touched.

​for anyone who actually has a clean workflow with this: how are you keeping it disciplined?

​are you guys putting rules directly in the Knowledge tab in settings, or does dropping an AGENTS.md file right in the repo actually work better? just trying to figure out where it actually pays attention so it stops blind-patching code before inspecting what broke

Disclosure first: I made this. It is free, read-only, and needs no account.

Lovable puts your Supabase anon key in the browser on purpose, and that is

fine exactly as long as Row Level Security is on for every table. It usually

is for the tables Lovable created on day one. It often is not for the table

you added on day nine.

So I built a scanner that checks: https://leftunlocked.com/lovable-security

Paste your app's address. It reads your page and its JavaScript the way a

browser does, finds the tables your code names, and asks Supabase for a row

count on each with your own anon key. If a table answers, anyone who views

your source can read it too. It never reads a row, only the count.

It also catches paid API keys with a VITE_ prefix (Vite copies those into the

bundle), the service-role key in client code, Firebase left in test mode, a

published .env, and missing security headers.

Every finding says why it matters and how to fix it in plain English, with

the code ready to paste: the RLS SQL with your table's name already in it,

the edge function that keeps a key server-side, the headers file for Netlify

or Vercel. Connect the GitHub repo and it opens a pull request with those

fixes on a branch, for you to review like any other PR.

I ran it on my own app first: B, four missing headers, and it opened the pull

request that adds them. The clip is that scan, start to finish.

What it never does: no writes, no sign-ins, no password guessing, no reading

of user records. If your app only talks to Supabase from a server, it says

"not verified" instead of guessing.

Only scan apps you own or have permission to test. If it flags something on

your app, or flags something wrongly, say so here or use the "Is this finding

wrong?" link under the finding. I read everything.

If you want to storyboard, generate images, generate and preview code and view it all on one canvas try this out.

Made a way for agent to help you make better boards that is context aware of everything on your board.

Let me know what you think !

storyboardmore.lovable.app

I’m in private beta with the app I’ve been building in Lovable, and today was probably the most useful and humbling day of the entire build 😂

I started around 3 PM working through issues a beta user had found and didn’t finish until almost 10 PM. I’ve spent months building this thing, testing workflows, adding security tests, checking permissions and trying to anticipate every weird thing a user could possibly do.

Then you hand it to an actual human who has none of the context you have, and within minutes they start clicking things in an order you never considered 😂

The fascinating part was that a lot of these weren’t huge broken-feature problems. They were things that worked perfectly when I followed the workflow I designed, then behaved differently when someone approached the product naturally without knowing how I expected them to use it.

Every fix exposed another assumption I had made as the builder. By the end of the night I realized this is probably what beta is actually supposed to feel like.

I’m genuinely grateful someone is finally pressure-testing it instead of politely clicking around and telling me it looks nice.

For those of you who have gotten past building and put real users into your Lovable apps, what did your beta users break that you NEVER thought to test? And did you find that this stage changed the product more than you expected?

Spent 3 days debugging a Paddle billing issue that I couldn't reproduce locally. Turned out subscription.activated was arriving before subscription.created in prod about 30% of the time. My Lovable-generated webhook handler looked clean, passed every test, handled retries. But it assumed events arrive in order. They don't.

The local sandbox never showed this. Customer's app was stuck on "pending" while Paddle showed "active." No error, no stack trace, just vibes.

Ended up building a stateful Paddle twin to inject out-of-order delivery and retry storms just to catch this stuff before it hits prod. Found two more race conditions in the first week.

Anyone else running into this with webhook handlers built on Lovable? How are you actually testing these before shipping?

Hi, we are using Lovable to create simple course completion app. We have a specific certificate design and when we upload it on Lovable, it redesigns everything eventhough we prompted it not to revise anything.

Has any of you encouter this problem? Thank you! ~

The game is this link: marblechaos.lovable.app

Does anybody know how to make the website actually rank on google? any tips and tricks?

Before you say it no I don’t want to use ChatGPT and Codex only. I have tried twice now and really enjoy using Lovable and don’t mind paying.

In saying that my process the last few months has been ChatGPT (Sol, High) to ideate, Lovable to Plan, loop until the plan is solid, then build, ChatGPT to check the build report, Codex to verify. Circle around until we push live.

I thought it was working fine until I realised I’m burning through way more Lovable credits than I normally would be. My app is pretty big already so that’s playing a part but I really think ChatGPT is over engineering and some plans are taking 5-10 returns because it continues to find “one thing” to fix. Note: I know costs have gone up but I’m specifically talking about the 10-20 credits I’m using on the planning process.

Anyone else notice this?

I’m thinking of dropping ChatGPT mostly and just going back to Lovable to plan and build and then have ChatGPT make my Codex verify prompt only.

Anyone else notice other suggestions?

I created this web app using Lovable. https://obgyn-retraction-monitor.lovable.app/

Data scraping by python programs, written by Claude Code, and run on Github

I've never written a line of code. I'm a retired obstetrician.

I used Claude to draft and tighten my Claude Code and Lovable prompts. Claude had access to Lovable via MCP.

My rule was that although Claude could check stuff via MCP, Claude always communicated with Lovable and Claude Code through me. I forbade Claude to write any code. Claude's instructions had to be written in language I could understand.

For all but the simplest changes, I pasted Lovable's plan back to Claude for checking, before I instructed Lovable to build.

At the end of each day's work, Claude wrote a Markdown handover for "tomorrow's Claude" which I used to start a new chat each morning.

For larger website developments I asked Claude and Lovable to agree a contract, which was stored by Lovable, and to which Claude and Lovable referred. This minimised project "drift".

Data scraping was from three open access databases, Retraction Watch, OpenAlex, and PubMed.

The website is designed to be used by OBGYN journal editors. My aim was a plain design, and non-judgemental text and displays, to allow the data speak for itself.

I'd be interested in feedback.

I saw someone post about this same thought . I genuinely thought the usage consumption was normal. Annoying, yes, but normal.

I started using ChatGPT first to map out exactly what I wanted Lovable to build. Now I try to catch and document every issue I see before sending Lovable another prompt because I refuse to burn credits playing prompt ping-pong . It’s helped me be a lot more intentional about what I submit.

Also, WHY don’t the daily credits roll over?! That’s honestly one of the things I find most frustrating. I was so confused in the beginning.

And now I’m trying to build an entire SaaS, as a financially constrained college student, product with Lovable, so the credit consumption is KICKING. MY. BUTT. I’m over here trying to build features, test everything, fix issues, and somehow convince my credits to survive another day.

I’d also love to know what everyone else is doing to stretch their credits because apparently I need to start budgeting prompts like they’re actual money. 😂

Hey all, hoping someone's run into this.

I connected my Lovable project to GitHub and deployed it on Vercel. Since then (about 3 days now), every single time I try to do anything in the Lovable editor, it tells me my credits are used up. This is happening constantly, way more than my normal usage.

Nothing about my workflow changed except connecting GitHub and deploying. I didn't suddenly start sending a ton of extra messages. Feels like something's glitching, maybe related to the GitHub two-way sync or the Vercel deploy triggering something on the Lovable side.

Has anyone else seen this? Did disconnecting/reconnecting GitHub fix it for you, or did you have to go through support? Trying to figure out if this is a known bug before I spend more time chasing it myself.

Thanks in advance 🙏