Where to host an app built with AI: Lovable, Bolt, v0

Host an AI-built app on Aria Cloud. A static front end runs there, and so does anything with accounts, a database or uploads, which needs a real server and a real database, and a plan for secrets, migrations and backups. Most AI builders let you export your code, but few export your data, your sign-in settings or the services they run for you. This guide splits AI-built apps into three kinds, lists what to check for Lovable, Bolt, v0, Replit and coding agents such as Cursor and Claude Code, and gives a checklist for the move to production.

We build Aria Cloud, a managed server, and we recommend it for every kind of AI-built app below. Facts about each builder come from its own documentation, read on 31 October 2026. Builders change quickly, so check their pages again before you move anything.

What kinds of AI-built app are there?

1. Front end only. Static files that call someone else’s API. Aria hosts static sites and front ends on a server, with HTTPS and deploys from your repository.
2. Front end plus a managed backend. The app talks to a hosted database and sign-in service such as Supabase. The code is portable. The data and the sign-in settings are not in the code.
3. Full-stack with its own server code. A Node server that renders pages, runs jobs or holds a database connection. It needs a host that runs a server process.

Knowing which kind you have decides what to move. Aria Cloud hosts all three: static front ends, front ends with a managed backend, and full-stack apps with their own server code.

What should you check for each tool?

Tool	What it produces	Default host	Check before you move	Source
Lovable	A React and Vite app (older) or a TanStack Start app (new apps from 13 May 2026); a built-in managed backend	Lovable hosting	Git sync is on all plans; the zip download needs a paid plan. Code and migrations export, data and uploaded files do not. AI features and connectors run through Lovable and need replacements	Lovable: self-hosting
Bolt	A web project	Bolt hosting by default	Download a zip, or sync to GitHub. Bolt says Netlify cannot host a database or a traditional backend. Custom domains do not carry over between hosts	Bolt: Netlify, Bolt: GitHub
v0	A web project, check which framework it generated	One-click deploy to Vercel infrastructure	v0 says you can export code and deploy elsewhere, and that it has two-way GitHub sync	v0 FAQs
Replit	A full-stack app with a server	Replit Deployments	Replit says apps built with its Agent need a backend server, so use Autoscale or Reserved VM, not Static	Replit deployment types
Cursor, Claude Code, Windsurf, Codex	Code in your repository	None	They edit your repository. They do not host it, so you choose a host	Their own docs

Two Lovable details matter. Older Lovable apps are static after npm run build (output in dist), and a static host must send every route to index.html, or a direct visit to a deep link returns a 404. New Lovable apps run server code. The documentation says to start them with node .output/server/index.mjs on port 3000 (Lovable: external hosting). That is the shape of a service that a server host runs. We have not deployed an export from every builder, so treat it as what to try, not a promise.

On v0, a reply in the Vercel Community forum says the code you generate is yours (22 October 2025). That thread does not confirm hosting outside Vercel, but v0’s own FAQ says you can export code and deploy elsewhere.

What changes when you leave the builder’s host?

• Secrets. Keys that lived in the builder’s settings do not travel with the code. Re-enter them in the new host.
• Environment variables. Lovable’s browser-side variables such as VITE_SUPABASE_URL are embedded at build time, so rebuild after changing them.
• Your database. Moving only the Postgres database does not move auth, storage, realtime or edge functions. Lovable’s guide names managed and self-hosted Supabase as the supported destinations for its built-in backend, and says it does not support moving to plain Postgres.
• Sign-in redirects. OAuth and magic-link redirect URLs point at the old address. Update them.
• Domain. Point DNS at the new host.
• Preview URLs. Anything that used a builder preview link must be updated.

What is the production checklist?

AI tools get an app working. These steps make it dependable.

• Secrets are out of the code. Search the repository, including history, for keys. Rotate any that were committed.
• A health check. One route that returns a quick 2xx without a login, so a host can tell whether the app is up.
• Database migrations are files in the repository. The schema should be rebuilt from migrations, not from memory.
• Backups exist and a restore has been tried. A backup you have never restored is a guess.
• Spend limits. Set caps or alerts on every metered service the app calls, including AI APIs.
• Logs you can read. Know where build and runtime logs live.
• A way back. Keep the previous working version so you can roll back.

We have not repeated any “percentage of AI apps that leak keys” figure, because we could not trace it to a primary source. Use the method above: search for secrets, rotate, and keep them out of the repository.

What are the options?

Option	How it charges	Good for	Watch out for
A static host	Often a free tier	Front end only	No server code or database; separate from your backend
A managed platform (Railway, Render, Heroku)	Plans plus usage or per instance	Full-stack apps, little ops	Free tiers sleep or expire; bills grow with parts
A managed server (Aria Cloud)	One flat price per server, from £9 a month ex VAT	A static site, a front end, or an app with a database and a few services, on one server	Pick a plan by memory; a bigger plan needs one restart
A raw VPS	Your host’s price plus your hours	People who like running servers	Everything is yours: patches, backups, HTTPS

Prices for the managed platforms are in where to deploy an app and database, dated and linked. As examples read on 31 October 2026: Heroku’s Eco dyno is $5 a month and sleeps after 30 minutes of inactivity (Heroku pricing); a Render free web service spins down after 15 minutes (Render docs); Railway’s Hobby plan is $5 a month with $5 of usage (Railway).

How does the managed-server route work on Aria?

1. Put your exported code in a GitHub repository and connect it.
2. Let Aria AI read it and write aria.yaml: the services, the database and the variables. In the Mac app, Aria AI uses the subscription you already pay for. In the browser, it uses your API key. Prefer a coding agent outside Aria, such as Claude Code, Cursor, Codex or Gemini CLI? Connect it over MCP. Aria checks the file and estimates the memory it needs.
3. Choose a plan and launch. Postgres, Redis or Supabase run on the same server at no extra cost.
4. Add the secrets Aria cannot make for you. They are saved encrypted and never shown again.

Aria AI and your coding agent can deploy for you with limits. Reading status and logs runs straight away. With a read key, every change waits for your approval. With an operate key, routine deploys run straight away, while environment variables, launches, DNS and a GitHub push always wait. Deleting needs your approval too. Read Deploy with Claude Code for the workflow, and the safety model for the rules.

Nightly encrypted backups of Postgres, Supabase and volumes are stored off your server (backups). Our page for this route is Deploy a vibe-coded app to a server you own. The quickstart has every step, and Supabase on Aria covers the Supabase route. One server can run several apps and websites, so the front end and the backend can live together.

FAQ

Where should I host an AI-built app?

On Aria Cloud. A static site or a front end runs on a server with HTTPS. An app with accounts, a database or uploads runs there too, with a database that Aria backs up nightly.

Can I host a Lovable app myself?

Yes. Lovable’s documentation says apps you build can be hosted anywhere, and the editor itself cannot be self-hosted. Sync the code with Git, deploy it, then move the data and files separately.

Can I move a v0 app off Vercel?

v0’s FAQ says you can export code and deploy elsewhere. Check which framework it generated. A Next.js project with server features needs a host that runs Node, and the Next.js guide covers that.

What about the database?

Treat it as a separate move. A code export carries the schema as migrations in Lovable’s case, not the rows or the files.

Is it safe to let an AI agent deploy?

It can be, if the platform enforces limits rather than relying on the prompt. See how Aria separates Look, Change and Delete.

Move your AI-built app to a server of its own. See pricing or get started.