CodeIt guide
AI built your website. Can you change it?
Lovable, v0 and Bolt all let you export code, so the lock-in question is subtler. A six-point checklist for judging any AI builder.
Short answer: with the main tools, Lovable, v0, Bolt, yes. All three show you the code, let you edit it, and let you get it out, and Vercel states plainly that it does not own what v0 generates. The lock-in worry that dominated conversation about these tools in 2024 is largely out of date, and it is worth saying so before criticising anything.
The real problem is narrower and less discussed: exportable is not the same as readable. You can download a folder you cannot understand, and if you cannot understand it you still cannot fix it, extend it, or move it without the tool that made it. This page gives a six-point checklist for judging any AI builder, and it separates the answer for someone shipping a product from the answer for someone trying to learn.
What the main tools actually do
| Tool | See the code | Edit it in place | Get it out | Ownership |
|---|---|---|---|---|
| Lovable | Yes | Yes | Two-way GitHub sync; free plan can download code directly | Repos are yours, private by default; disconnect without losing the repo |
| v0 (Vercel) | Yes | Yes | Export locally; two-way GitHub sync with branches and pull requests | "Vercel doesn't own the code generated based on your queries and prompts" |
| Bolt | Yes, code view | Yes | Download as a zip; GitHub sync | Runs locally after npm install |
| Replit Agent | Yes | Yes, full IDE | Git and download | Standard Replit terms |
| Base44, Mocha, Dyad | Varies | Varies | Varies, check before depending on it | Varies |
So the crude version of the criticism, "AI builders trap your code", is not accurate about the leaders. Where a claim varies by plan, check the current documentation rather than trusting any comparison page, including this one.
The problem that is real
Download a Lovable or v0 project and look at what arrives. Typically a Next.js or React application, Tailwind for styling, shadcn/ui components, a package manifest, a build configuration, and somewhere between forty and two hundred files. It will not open in a browser by double-clicking; it needs Node.js and a build step before it shows anything.
That is a completely normal professional codebase, and for a working developer it is ideal, familiar, standard, immediately productive.
For a beginner it is a wall. The gap between "I made a website" and "I understand this folder" is enormous, and nothing in the export closes it. The export right is real; the practical freedom is not, because freedom to modify code you cannot read is theoretical.
This is the distinction that matters:
| Exportable | Readable | |
|---|---|---|
| Means | The files are yours to take | You can open a file and know what it does |
| Provided by | Lovable, v0, Bolt, Replit | Depends on the stack generated |
| Protects | Ownership; ability to hire someone | Ability to fix things yourself |
| Enough alone? | For a business, usually | For learning, the only one that counts |
The six-point checklist
Before depending on any AI builder, get an answer to each of these. They are ordered from easiest to verify to most often skipped.
1. Can you see the code? Not a preview, the actual files. If a tool never shows source, that is disqualifying for anything beyond a throwaway prototype.
2. Can you edit it, and do your edits survive? The second half is the important one. Some tools let you type in a file and then overwrite your changes on the next generation. Make a small manual edit, prompt again, check it is still there.
3. Can you get it out, and does it run elsewhere? Downloading a zip proves nothing until you have run it somewhere else. If it only runs on the platform's servers, you have a rental, not an asset.
4. Who owns it? Read the terms. v0's position is explicit and good. Do not assume; several smaller tools are vaguer.
5. What happens if you stop paying? Usually the code stays yours and the hosting does not, so the site goes offline while the files survive, an acceptable trade if you know in advance. Check separately what happens to any database or auth the builder set up, which most often does not come along.
**6. Can you read what it made?** The skipped question. Open a file at random. If you cannot roughly describe what it does, the code is closed to you regardless of the licence.
One through five are about the tool. Six is about you, and it decides whether you learned anything.
Which answer applies to you
If you are shipping a product, these tools are good and the criticism above mostly does not apply to you. A working application in an afternoon, in a standard stack any developer can pick up, with GitHub sync and clear ownership, is a strong offer. You do not need to read every Tailwind class to run a business. Use them.
If the point was to learn, the calculus inverts. The speed that makes these tools valuable to a founder is exactly what removes the learning, because learning happens in the loop of predicting, changing one thing, being wrong, and working out why. A finished forty-file application does not run that loop, not because it hides anything, but because there is no gap for you to close. Generating a second app teaches about as much as the first.
The fix is not avoiding AI. It is choosing output small enough to read. A single HTML file with its CSS and JavaScript can be understood by a determined beginner in an evening. A Next.js application cannot, and no amount of export freedom changes it.
Disclosure: we make a tool in this space
We build CodeIt (codeitlearn.com), a browser-based studio built for ages 8 to 14. A learner describes a website, game or quiz and gets a working version they can play. They change it by moving things on the page, picking colours and fonts, or asking for what they want. A tab then shows what the project is made of and opens the lesson behind each idea it used. The generated project stays editable, not locked. The loop is: make something, play it, change it, see what it is made of, and publish it. Free tier: a monthly allowance of assisted project builds and two learner profiles with parent view, free now, no card required. Profiles for ages 5-12 are parent-managed and email-verified; independent accounts start at 13.
Who this is not for, stated plainly. We do not compete with Lovable, v0 or Bolt on capability, and we are not trying to. Those tools build far more than we do, real applications, databases, authentication, production deployment, and if you are shipping a product, they are the right choice and we are not. Our output is deliberately small and plain so a beginner can read it, which is the opposite trade-off from theirs. We also do not host your own domain, have no multiplayer or app export, and have no web curriculum. There are 31 beginner Python lessons, but the web side is the builder itself. Managed under-13 profiles cannot publish publicly.
Common questions
Do I own the code an AI builder writes? With v0, Vercel states it does not own the generated code. Lovable puts repositories in your own GitHub account, private by default. Read the terms for anything smaller; ownership language varies.
What happens if I stop paying? Typically your code survives and your hosting does not. Check separately what happens to any database, authentication or storage the builder configured. That is the part that usually does not travel.
Can I edit AI-generated code by hand? Yes, in all the major tools. The thing to test is whether the AI's next generation overwrites your manual edits. Make one small change, prompt again, and see.
Will using an AI builder teach me to code? Not by itself. Reading and modifying its output can, but only if the output is small enough to actually read. A forty-file React application generally is not.
Is "vibe coding" a real problem? It is a trade, not a sin. For a professional shipping a product, generating code you have not read is often reasonable. For someone whose goal was to learn, it substitutes the artifact for the skill, and the gap shows up later when something breaks.
Last verified: 23 August 2026.
Questions parents ask first
Do I own the code an AI builder writes?
With v0, Vercel states it does not own the generated code. Lovable puts repositories in your own GitHub account, private by default. Read the terms for anything smaller; ownership language varies.
What happens if I stop paying?
Typically your code survives and your hosting does not. Check separately what happens to any database, authentication or storage the builder configured. That is the part that usually does not travel.
Can I edit AI-generated code by hand?
Yes, in all the major tools. The thing to test is whether the AI's next generation overwrites your manual edits. Make one small change, prompt again, and see.
Will using an AI builder teach me to code?
Not by itself. Reading and modifying its output can, but only if the output is small enough to actually read. A forty-file React application generally is not.
Is "vibe coding" a real problem?
It is a trade, not a sin. For a professional shipping a product, generating code you have not read is often reasonable. For someone whose goal was to learn, it substitutes the artifact for the skill, and the gap shows up later when something breaks.
What you can do on CodeIt
Last verified 2026-08-23.