What is the easiest way to host a vibe-coded app?

Ask the AI that built it. Connect LazyFrog to Claude, ChatGPT, Codex or Claude Code once, then say "put this online": it makes a project, moves the code in, checks the preview and publishes when you say so.

My app works in the builder but not elsewhere. Why?

Usually one of three things: keys that lived in the builder's settings, a database that was part of the builder, or a build step the builder ran for you. The import lists the keys the code reads, every project has its own PostgreSQL, and the preview shows the build's errors to your AI so it can fix them.

Do I need GitHub or Docker?

No. Code can be pushed straight from a folder, uploaded, or imported from GitHub. LazyFrog runs the commands in your services.json; a Dockerfile and compose.yml are there to run the same code anywhere else.

Is a vibe-coded app safe to put online?

Check it first. AI-written code often has keys in it, routes anyone can call and queries built from strings. LazyFrog's security scan looks for those, and our checklist lists what to check by hand.

Hosting for AI-built apps

Made an app with AI? Here's how to put it online.

An app that works in a chat or a builder still needs somewhere to run, a database, its keys kept safe and an address. The quickest way is to ask the AI that made it: connect LazyFrog once and it puts the app online for you, preview first.

Start free Connect your AI

Start from where your app is

A chat with Claude

An artifact or a site Claude wrote in the conversation.

Connect LazyFrog to Claude and ask it to put the site online. It makes a project, builds the site there and shows you a preview.

Claude website builder, with a real example

A chat with ChatGPT or Codex

A page or app ChatGPT made, or code Codex wrote.

Add LazyFrog in ChatGPT or Codex and ask for the same. The project, the database and the preview are made for you.

ChatGPT website builder, with a real example

Claude Code or Codex on your machine

A folder with an app in it, with or without git.

Your AI makes a project and pushes the folder to it with git. Every push updates a preview with its own PostgreSQL.

Claude Code hosting, with a real example

Lovable

An app in Lovable's editor, usually with a Supabase backend.

Send it to GitHub from Lovable, then ask your AI to import it. Supabase keeps working, or the data moves into the project's own database.

Move from Lovable

Bolt, v0 or another builder

Code you can download or send to GitHub.

Put it in a repository on GitHub, GitLab or Bitbucket and ask your AI to import it. The import removes the builder's editor plugins, starts the preview, runs a security scan and lists the keys the code needs.

Moving in and moving out

An MCP server

Tools for AI apps, written by your AI or by you.

It runs like any web service: an HTTPS address, its own database, secrets and logs.

MCP server hosting, with a real example

What your app needs once it leaves the chat

These are the parts a builder or a chat handled for you. Each project on LazyFrog has all of them.

Somewhere to run: A server process for the app, not only static files: forms, logins and APIs need one. Each project runs the commands in its services.json, in any language.
A database: PostgreSQL in every project, one for the preview and one for the live site, kept separate. Schema changes run as migrations on every push and publish.
Keys kept out of the code: Secrets are pasted in your LazyFrog account, never in the chat, and read from the environment. A push that contains a key is refused, with the file and line.
A preview before it's live: A private preview address for every project, where your AI checks the app in a real browser. Nothing is public until you publish.
An address and HTTPS: A live address on lazyfrog.app, or your own domain on Hobby and up, with HTTPS handled for you.
A way back: Snapshots of the code, the database and the files, and an earlier version back in seconds. The code is in git and exports with your data.

Before it goes live

AI-written code often works and still isn't safe: a key in the code, a route anyone can call, a query built from strings. Ask your AI to scan the project, then go through the security checklist for AI-built apps. Publishing rehearses on a copy of the live database first, and an earlier version comes back in seconds.

What it costs

Building and trying is free: one project with its database and a private preview. A live site starts with Hobby at $9 a month (excluding VAT and sales tax), with your own domain. LazyFrog sells no AI credits; your AI runs on the plan you already have. Every plan and limit

Questions

What is the easiest way to host a vibe-coded app?: Ask the AI that built it. Connect LazyFrog to Claude, ChatGPT, Codex or Claude Code once, then say "put this online": it makes a project, moves the code in, checks the preview and publishes when you say so.
Can I host it for free?: Building and trying is free: one project with its database and a private preview. A live site starts with Hobby at $9 a month (excluding VAT and sales tax). LazyFrog sells no AI credits; your AI runs on the plan you already have.
My app works in the builder but not elsewhere. Why?: Usually one of three things: keys that lived in the builder's settings, a database that was part of the builder, or a build step the builder ran for you. The import lists the keys the code reads, every project has its own PostgreSQL, and the preview shows the build's errors to your AI so it can fix them.
Do I need GitHub or Docker?: No. Code can be pushed straight from a folder, uploaded, or imported from GitHub. LazyFrog runs the commands in your services.json; a Dockerfile and compose.yml are there to run the same code anywhere else.
Is a vibe-coded app safe to put online?: Check it first. AI-written code often has keys in it, routes anyone can call and queries built from strings. LazyFrog's security scan looks for those, and our checklist lists what to check by hand.

Start free Connect your AI