away from lovableVibe code without limits.
Build real apps with Claude Code on your own GitHub, Supabase and Vercel. No builder in between, no credits for every change, and every account in your name. Coming from Lovable? You don’t have to leave in one go: your code goes to GitHub first, and the hosting and the data move only when your business asks for it.
I’m Teemu Sormunen. I build SaaS apps for clients alone, end to end, with Claude Code and Codex, and I have deployed over 100 Lovable apps and around 50 Vercel projects.
What “without limits” means
The builder got you to a working app. Owning the stack is what lets you keep going without asking its permission.
You own
- The code, in your own GitHub account
- The database, the logins and the files, in your own Supabase project
- The hosting, on your own Vercel account
- The bills, in accounts you can open
Claude Code does
- The building, on your own plan instead of per-message credits
- The changes, the checks and reading the logs
What you take on: secret keys, table rules, who can call what. Those are yours to check now, and that is where the free scan, the kit and my review come in.
Four ways to get there
Start free. Pay only for the step you actually need.
-
Free
Tips and a safety check
Is my app safe? LaunchGuard’s free scan checks your live app from the outside for data the public can read. The five-question check tells you where a Lovable app stands, and I post Claude Code tips on TikTok.
-
$19 one payment
The kit: you and your agent
A guide, an agent skill, guardrails and checks. Claude Code or Codex moves your app onto your own accounts with you, one step at a time.
-
$590 one-time
Done for you
I move one app onto your own GitHub, Supabase and Vercel, set up CI, and run a security pass on it.
-
$249 a month
Monthly review
You keep building with Claude Code. I review every change that touches payments, logins or the database before it goes live.
Coming from Lovable? Six stages, read only yours.
Written for founders who built the app in Lovable and can’t read the code. Most stop at stage 2: the code moves to GitHub and Claude Code, while Lovable keeps hosting the app and running its database.
- 1 Keep building Nobody uses it yet
- 2 Bring in your agent Credits hurt, or Lovable loops on a bug Most founders stop here
- 3 Real people use it Others sign up, store data or pay
- 4 Move the hosting You want previews, or your own account
- 5 Move the data You need your own database
- 6 Someone else works on it A developer, client or buyer joins
What changes when your agent takes over
Stage 2 is where most founders stay. Nothing about the app moves; the work moves to your agent.
Stays with Lovable
- Your live site and its address
- The database, the logins and the uploaded files
- The Lovable editor, whenever you still want it
Moves to you
- Your code, in your own GitHub account
- The building, by Claude Code or Codex on your own plan
- The approvals: nothing goes live until you click Publish
Five things worth knowing before you start
- A change pushed to GitHub is not live. Your site changes only when you click Publish in Lovable.
- Server code and database changes stay undeployed even after Publish. Lovable runs them only when its chat is asked, and that message costs credits. The dashboard can still look up to date.
- “Row level security enabled” can still let anyone change your data. Nothing breaks, so nobody notices until someone else does.
- Once another host serves your site, every Lovable edit goes live at once. There is no Publish button in between any more.
- Removing Lovable Cloud deletes your saved export with it, and everyone signed in to your app signs in again after the move.
You unzip one folder, open it in your AI agent, and paste one prompt. Your agent does the technical work and explains each step in a sentence before it runs it.
- The guide. Six short pages, one per stage. You read only the one you’re in.
- The agent skill. It runs each stage with you and remembers where you left off, on any computer. Built for Claude Code and Codex, and readable by any AI agent.
- Guardrails. Anything that reaches your live app waits for your yes. In Claude Code and Codex, force pushes, database resets and project deletes are blocked outright.
- Checks. Secret keys in your code, tables anyone can change, server functions anyone can call.
- Five deep scans of one live app by LaunchGuard, which tries your app from the outside the way a stranger would.
- Updates in a private GitHub repository, when Lovable, Supabase or Vercel change something.
You
Log in where a browser asks you to, type secret values into your own terminal, say yes or no, and click the few buttons that change things for good.
Your agent
Everything else: reads the code, makes the changes, runs the checks, reads the logs, and tells you in plain words what it found.
How it starts
- Pay once. Your access key arrives by email.
- Download the kit and unzip it.
- Open it in your AI agent, such as the Claude app, and paste the prompt from the guide.
- Your agent copies your app from GitHub and starts stage 2 with you.
What you can count on
- Your app stays the app you built. The kit works with Lovable’s code as it is, with no rewrite.
- Every step explained first. One plain sentence before it runs, and one after on what changed.
- Logins tested before anything moves. When you move your data, the agent tests your sign-ins first and has a reset plan ready.
- Checks that show their work. Every check lists what was tested and what came back, so you can see it for yourself.
- Your accounts stay in your hands. You log in, you hold the secret values, and the final clicks are always yours.
- Honest timing. If nobody uses your app yet, the free check tells you to keep building and come back later.
Questions
Can you do it for me instead?
Yes. Done for you is $590 one-time: I move one app onto your own GitHub, Supabase and Vercel, set up CI and run a security pass, in five working days. If you keep building with AI after that, the monthly review is $249 a month: I review every pull request that touches payments, logins or the database before it goes live. Both start with a short form about your app, and I reply before anything is paid.
Should I leave Lovable at all?
Often, no. The usual reasons are credits, wanting Claude Code or Codex, and bugs Lovable keeps looping on. All three are solved by putting your code on your own GitHub and letting your agent work on it, while Lovable keeps hosting the app and running its database. Move the hosting or the data only when your business asks for it. If nobody uses the app yet, connect GitHub as a backup and keep building.
Can I keep using the Lovable editor?
Yes. Lovable’s GitHub sync works both ways on one branch: what Lovable changes lands in your repository, and what your agent pushes lands back in Lovable. While Lovable hosts the app, a push updates the project in Lovable, not your live site, so you still click Publish. Server functions and database changes your agent writes are not deployed until you ask Lovable’s chat, and that message costs credits. Once another host serves the app, every Lovable change goes live straight away.
Is it cheaper than building in Lovable?
Building usually costs less. People writing publicly about their own moves report going from a few hundred dollars a month in Lovable credits to a single agent plan. Those are their numbers, not a promise about yours. While Lovable hosts the app and runs its database, those still use Lovable credits, and so does every message you send its chat. After a full move, hosting, the database and every paid service still cost what they cost; the difference is that every bill is in an account you can open.
Can I move my Lovable app to Vercel?
Usually yes. Connect the Lovable project to GitHub, then import that repository at vercel.com/new. Projects Lovable started from May 2026 run on TanStack Start, and Vercel deploys them without custom build settings once the @lovable.dev/vite-tanstack-config package is version 2.6.2 or newer. Older React and Vite projects need a vercel.json rewrite, or every page except the home page returns 404 on refresh. Vercel’s free plan is for non-commercial use, so an app that takes money needs a paid one.
Why does my app show a 404 or a blank page after I deploy it?
Four usual causes. The host has none of your environment variables, so the app stops before it draws anything. An older React and Vite app has no single-page-app rewrite, so every page except the home page returns 404 on refresh. The framework preset or output folder on the host is wrong. Or a TanStack Start project has an older build setup aimed at Cloudflare, so Vercel builds green and serves its own 404. Each one is a single setting or a single file.
How do I get my database out of Lovable Cloud?
With Lovable’s own export: More → Cloud → Overview → Advanced settings → Export project data. It copies the whole database, structure and data, up to 15 GB, once a day. Uploaded files, server function code and secrets are not in it, so the files come separately from More → Cloud → Storage. Restore into a Supabase project you created, compare the row counts table by table, and only then press Remove Lovable Cloud. That button deletes the Cloud backend and the saved export for good.
Will my users have to reset their passwords?
Usually not, but test before you promise anything. Lovable’s docs say the export carries your users’ accounts and their scrambled passwords, so after a restore into your own Supabase they keep their passwords. Anyone signed in at the switch has to sign in again, and sign-in settings such as Google sign-in are not in the export, so you set them up again. Test an existing account and each sign-in method on the new project, and keep a password-reset plan and working email sending ready before you remove anything.
Do I need to know how to code?
No. You need an AI coding agent such as Claude Code, Codex or Cursor; Claude Code and Codex both come as desktop apps with a chat window like Lovable’s. The agent explains each step in a sentence before it runs it. Your part is logging in where a browser asks you to, saying yes or no, and clicking the buttons that change things for good.
Which AI agents does it work with?
Any agent that can read your project’s files and run commands, including Claude Code, Codex and Cursor. The guide, the rules in AGENTS.md and the skill are plain instructions any of them can follow. In Claude Code and Codex the kit’s guardrails are also enforced by the tool itself, so commands like force pushes and database resets are blocked outright.
Not sure where to start?
The five-question check takes about a minute: no email, no code upload, nothing to install. The free scan takes your app’s address and shows what the public can read.