Do You Own Your AI-Built App's Code? Export, Hosting and Lock-In

Usually you can get the files out, but a download button isn't the same as owning the app. Owning an AI-built app takes five things: the code, the right to use it, somewhere to run it, the data and accounts behind it, and the address people know. Most builders let you take the code. Fewer let you take the rest without rebuilding part of the app.

Lock-in rarely looks like a locked door. It looks like an export that runs only half the app, a download that needs a pricier plan, or a site whose links all point at the builder's domain. Below: the five parts, how 14 builders handle export and hosting according to their own documentation, and a checklist to run before you commit. It isn't legal advice: for the licence question, read each builder's terms.

What "owning" an AI-built app means

1. Export. Can you download the files, on which plan, and in what form? Standard files a developer can open (plain HTML, a normal React project) are worth more than a format only the builder reads. Git sync keeps an up-to-date copy outside the builder; a zip is a snapshot.
2. Licence. Who holds the rights to the generated code and to your content, and what are you allowed to do with them? This lives in the terms of service, not on the pricing page.
3. Hosting. Will the exported code run anywhere, or only on the builder's servers? Static files run on almost any host; an app with server code needs a host that runs it.
4. Data and backend. Sign-in, user accounts, stored records, uploaded files and server functions are usually services the builder runs, not code in your zip. Find out whether the data can come out and in what format.
5. Domain. If your site lives on the builder's subdomain, every link and bookmark points at an address you don't control. If you bought a domain inside the builder, know where it's registered and how to move it.

For where exported code can run, see our guide on where to host an AI-built website. It covers builder hosting, static hosting, Node.js hosting and a VPS, so we won't repeat it here.

How 14 builders handle export and hosting

From the data behind our "Veloxa Build vs" pages, checked on each builder's own pages on the date shown. Plans change, so follow the sources before you decide.

AI app builders

• Lovable (checked 8 October 2026): download and edit the code on paid plans; two-way sync with GitHub, GitLab or Bitbucket on every plan, including Free. Hosting is included at an address like xxx.lovable.app. Hosting and the built-in backend (a SQL database, sign-in, storage and edge functions) draw on credits after a monthly grant; when credits run out the site stays live, but the backend can pause. Source. Moving it: host a Lovable app on your own domain.
• Bolt (18 October 2026): download a zip, or use GitHub sync that commits your changes and pulls in changes made outside Bolt. Hosting is included at a bolt.host address; on Free, a site that goes over the monthly bandwidth or request limit goes offline for the rest of the month. Source. Moving it: export a Bolt project and host it.
• v0 (18 October 2026): download a ZIP, or sync with a private GitHub repository, which is listed on the Free plan. Vercel says it does not own the code v0 generates. Sites publish to Vercel; its free Hobby plan is for non-commercial personal use only, so a commercial site needs Vercel Pro. Databases come through Vercel Marketplace integrations such as Neon and Supabase, each creating an account with that service. Source, Hobby plan.
• Replit (18 October 2026): download a zip, or connect a GitHub repository with two-way sync. Publishing is billed by usage, and on the Starter plan a published app's link goes down after 30 days. Apps get a built-in PostgreSQL database and Replit Auth sign-in. Source.
• Base44 (18 October 2026): on Builder and higher, download a zip or use two-way GitHub sync. The export has the front-end code and backend functions, and data comes out as CSV files; the hosting, sign-in system and database stay on Base44. Source.
• Hostinger AI Builder, formerly Horizons (18 October 2026): on paid plans, export the code as a zip of a React and Vite project. Data in the built-in backend isn't exported, an export can't be imported back, and there's no GitHub import. Source.
• Veloxa Build: download the project as a zip of plain HTML, CSS and JavaScript on every plan, including Free. You get the current version; version history isn't in the download. There's no GitHub sync. Hosting with HTTPS is included at an address like yourname.veloxa.site, never uses AI usage, and sites stay online when AI usage runs out. Forms and their inbox work only on veloxa.site, and sign-in, file storage, the database and AI features call Veloxa Build's services rather than anything in the zip. Custom domains are coming soon on paid plans.

Website builders with AI features

• Wix (8 October 2026): no export. Wix says a Wix site must run on Wix's servers, and that the content you build belongs to you. Source. Moving it: move a website from Wix to an AI builder.
• Squarespace (19 October 2026): no full export. Some content (layout pages, one blog, text and image blocks) exports as a WordPress .xml file; style settings and custom CSS don't. Source.
• Framer (19 October 2026): unsettled. One Framer help article says it doesn't offer HTML export for self-hosting, another says the published files can be downloaded. CMS content can be exported as CSV or JSON with plugins. Source.
• Carrd (19 October 2026): on Pro Plus and up, download the unminified HTML, CSS and JavaScript as a zip. Forms don't work in the download, and it can't be uploaded back to Carrd. Source.
• Mixo (19 October 2026): the published site's source code is a separate paid purchase, arranged through Mixo support, and a downloaded site can't be imported back. Source.
• 10Web (19 October 2026): a full WordPress site with SSH, SFTP and MySQL access and downloadable backups, but 10Web's help says sites built with its AI won't function correctly outside its hosting. Source.
• Durable (8 October 2026): export isn't settled by its own pages. Durable calls itself a "no code" builder and doesn't offer extensive HTML customization.

The Veloxa Build comparison puts the AI app builders' plans, code download and GitHub sync in one table.

What lock-in looks like in practice

Across those 14, lock-in shows up in six recognizable shapes.

The export that runs half the app

The front end comes out; the backend stays. Base44's export leaves hosting, sign-in and the database on Base44, and Hostinger's leaves the backend data behind. Veloxa Build belongs here too: pages, styles and scripts run on any static host, but forms, sign-in, file storage and stored data need Veloxa Build hosting. Ask: if I downloaded today and the builder disappeared, what would still work?

The exit behind a plan

Lovable puts code download on paid plans (Git sync is on Free), Base44 on Builder and higher, Carrd on Pro Plus, Hostinger on paid plans, and Mixo sells it separately. Paying for an export is reasonable; discovering it after you've built on a cheaper plan is the trap.

The one-way door

Carrd, Mixo and Hostinger say an export can't go back in. Edit it elsewhere and you maintain it there: fine if you meant to leave, awkward if you wanted a backup.

The site that only runs at home

Wix sites run only on Wix. Squarespace exports some content but not the design. 10Web hands you WordPress but says its AI-built sites won't work correctly on other hosts. Here, owning your content doesn't mean you can run the site anywhere else.

Hosting tied to usage

Lovable's backend can pause when credits run out, Bolt's Free sites go offline for the rest of the month over the limit, and Replit's Starter links go down after 30 days. None of that is hidden, but your site's uptime then depends on your plan and your AI spending. On Veloxa Build, hosting never uses AI usage, and published sites stay online when it runs out.

The address you don't control

Every link to yourapp.lovable.app or yourname.veloxa.site points at the builder's domain, not yours. On Veloxa Build, changing a site's address removes the old one, so links to it stop working. And switching builders usually means rebuilding: Veloxa Build, for example, has no importer for Lovable projects, and data in Lovable's backend doesn't move over.

Licence: read the terms, not the marketing

We can't tell you what any builder's terms mean for your business, and this isn't legal advice. We can say where to look. Terms of service usually cover who owns the output, what rights you grant the builder over your content and prompts, what happens to projects you cancel or delete, and limits on use. Pricing pages and FAQs are summaries; the terms are what apply.

Two statements from the builders' own pages show why the details matter. Vercel says it doesn't own the code v0 generates. Wix says the content you build belongs to you, while also saying a Wix site must run on Wix's servers. Owning the content and being able to move the site are separate questions.

Generated code often includes third-party libraries, each with its own licence terms. If the app matters to your business (you plan to sell it, license it or raise money on it), have a lawyer read the terms. For Veloxa Build, the Veloxa Build terms are published on this site; for others, follow the links in their footers, such as Mixo's terms or 10Web's terms of service.

Where Veloxa Build fits, honestly

Veloxa Build suits you if you want the code out on any plan, as plain files you can open in an editor, and hosting that doesn't depend on your AI spending. When an app outgrows the builder, you can run the files on VeloxaHost hosting or on a VPS from $4 a month, billed to the same account.

Another builder is the better pick if you need:

• Git sync. Veloxa Build has none; Lovable, Bolt, v0 and Replit have it, and Base44 from its Builder plan.
• A SQL database. Veloxa Build apps get a key-value database. Lovable's backend has a SQL database and Replit has PostgreSQL. See Veloxa Build vs Lovable.
• Payments. Veloxa Build has no payments integration; Bolt and Replit list Stripe payments.

If you delete a Veloxa Build project, its files, version history and conversation are deleted and the site is taken down, so download it first. More answers are on the Veloxa Build FAQ.

A checklist before you commit to a builder

1. Download on day one. Export a small test project and open it. Is it standard files a developer would recognize, or something only the builder reads?
2. Find the plan the export needs. Check it now, not when you want to leave.
3. Turn on Git sync if there is one. A repository with history is a better backup than an occasional zip.
4. List what the export leaves behind. Forms, sign-in, the database, file storage, server functions, AI features and payments. For each, note what you'd replace it with.
5. Host the export somewhere else once. Put the files on a static host and click through. What breaks is your real lock-in.
6. Get your data out. Find out whether records, user accounts and uploaded files can be exported, and in what format.
7. Check what happens when credits run out. Does the site stay online? Does the backend pause?
8. Plan the address. Know where your domain is registered and how to transfer it. If you start on a subdomain, decide early whether you'll move.
9. Read the terms. Output ownership, rights over your content, cancellation and deletion. Get legal advice if the stakes are high.
10. Keep your inputs. Save your prompts, copy, images and price lists outside the builder. They're what you need to rebuild somewhere else.

Run it against two or three builders before you put real work into one. For the search side of the same decision, see our checklist on whether an AI-built website is good for SEO.

Start building in Veloxa Build on the Free plan, or see what each plan includes on the Veloxa Build pricing page.

Competitor details are from each builder's own pages, checked on the dates shown (8, 18 and 19 October 2026). This post is general information, not legal advice. Spotted something out of date? Email us at support@veloxahost.com.