Where should I host my vibe-coded app?

If your vibe-coded app is pages that open in a browser (a folder with index.html, or dist after npm run build), host it anywhere that takes a finished folder: on DropTheHassle you drop it on dropthehassle.com and it's live on a free HTTPS link in minutes, and your own .com is €19 / $19 a year. Only a part that has to keep running, like a server, needs a server host, and if your app talks to Supabase or Lovable Cloud, that part already lives there.

Your AI can publish. It can never spend your money.

Built it with ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf or by hand? Same steps.

Last updated: 3 October 2026. The GitHub Pages limits, the Vercel Hobby rules and the Bolt price were checked on their own pages that day. Netlify and Cloudflare Pages were checked on 30 September 2026, with a source per claim on our host comparison.

First: what did you actually build?

Picking a host gets easy once you know what kind of app you have. You can tell in a minute by opening the project folder, or by asking the AI that built it.

Pages only. HTML, CSS, JavaScript and images, and nothing that needs to keep running. Landing pages, portfolios, small tools and games from ChatGPT, Claude, Cursor or Claude Code are usually this. After npm run build it's a dist folder. Any host for built files will do.
Pages that talk to a service. A Lovable or Bolt app on Supabase, a form that posts to a form service, a page that calls someone's API. The pages go on any host. The service stays where it is, and you only tell it your new address.
An app with its own server. You start it with node server.js, python app.py or npm start, and it has to keep running for the app to work. That part needs a server. The pages can still sit somewhere simple.

Not sure? Ask your AI: Is this pages only, pages that call an outside service, or does it need its own server running? Which folder would I upload?

Your options, side by side

These all work. They're good at different things. The table scrolls sideways on a narrow screen.

Where	A good fit when	Keep in mind
Stay on Lovable or Bolt	You still change the app every day and like pressing Publish in the builder	Your own domain needs a paid plan on both. On Bolt that's Pro, $25 a month billed monthly
DropTheHassle	You have the finished folder and want it live with no account, then your own name and email in one place	It doesn't build from GitHub. You upload the built folder, or your AI does, and it links the server part you keep on AWS, Google Cloud, DigitalOcean or your own server.
Netlify	You want builds from your Git repo, or a quick drag onto Netlify Drop without an account	A domain that stays at your registrar means adding DNS records there
Vercel	You built with Next.js and want builds from your Git repo	The free Hobby plan is for personal, non-commercial use only
Cloudflare Pages	You expect a lot of visitors and want to stay on a free plan	Uploading a folder needs a login. For a domain without www, Cloudflare wants your nameservers
GitHub Pages	The code lives on GitHub anyway, and it's a portfolio, docs or a project page	GitHub says it's not meant for running an online business or a shop. A published site can be at most 1 GB
AWS, Google Cloud, DigitalOcean or your own server	The app has a real server part that has to keep running	Someone has to set up and look after that machine, you or your AI

So which one?

For a vibe-coded app that's pages only, pick on the boring stuff, not on speed. They're all fast enough for a launch. What differs is how many steps it takes you, what the domain costs next year, and whether you ever have to touch DNS.

You just want a link to send today. Drop the folder here or on Netlify Drop. Neither needs an account first. Here, claim the site and the free link stays.
You want your own .com without learning DNS. Buy it here. A .com is €19 / $19 a year, including VAT in the EU, the same every year, and it's connected to your site for you.
You push to GitHub on every change and like it that way. Netlify, Vercel and Cloudflare Pages can build from your repo each time.
You're selling something. Read the free tier's rules before launch day. Vercel Hobby is non-commercial, and GitHub Pages isn't meant for a shop.
There's a server part. Read the next section first.

If your app has a server part

A folder of files can't run a program that keeps going in the background. That's the one thing it can't do. If your app starts with node server.js or python app.py, split it in two: the pages people see go on a host for built files, and the program goes on a server. Got a server part too? Keep it on AWS, Google Cloud, DigitalOcean or your own server, and your AI links it to your site in one step.

A database you reach from the browser, like Supabase, isn't a server you have to host. It already runs at Supabase. Put its keys in .env before you build, and add your live address to its list of allowed redirect URLs. Lovable Cloud works the same way: the published pages keep talking to it.

Put it online in 4 steps

Build it. With a package.json, run npm run build, or ask your AI to, and use dist (or build or out). A plain HTML project is ready as it is.
Open dropthehassle.com and press Upload (free). There's no account to make first.
Press Drop your folder and drop it in. A .zip works too. Give your email when it asks. Before you claim, the limit is 25 MB and 1,000 files.
Claim it. Your site is already live at https://yourname.dropthehassle.app. Hit Claim this site on that same screen: unclaimed sites are removed after at least 7 days, and claimed ones can grow to 100 MB and 5,000 files.

Apps with their own routes, like /pricing or /dashboard, survive a refresh: any address without a matching file is answered with your index.html.

Or let your AI do it

Connect https://dropthehassle.com/mcp once in Claude Code, Cursor, Codex or Windsurf, then say put this site online with DropTheHassle. You get a live link and a claim link back, and the first deploy needs no account and no token. The set-up for each tool is in the MCP guide. Your AI can also look up a domain and hand you the payment link. Paying is always your own click.

Common mistakes when picking a host

Renting a server for a site that's pages only. A VPS or a Node hosting plan will run it, but you're paying to look after a machine your site doesn't need.
A free tier that doesn't allow what you do. Check the rules on selling before you launch, not after the first sale.
Uploading the project instead of the build. The files you edit are the source, and a browser can't run them as they are. Here, a project that still needs a build is refused, so you find out right away.
Sharing the preview link. localhost and the preview window in your builder only open for you.
Secret keys in the build. Everything in the built folder can be read by visitors. A public key like Supabase's anon key is fine there. A secret key is not.
Moving the domain first. Get the new site working on its free link, then point the domain at it.

Already online and something's broken? The five usual causes are in my site works on my computer but not online.

Copy this to your AI

Paste this into whichever AI built the app. It sorts out what you have before you pick anything.

I want to put this project online. Before we do, tell me:
1. Is it pages only, pages that call an outside service (like Supabase), or does it need its own server running?
2. Does it need a build step? If so, run it and tell me which folder to upload (dist, build or out).
3. Is there a secret key anywhere in code that ends up in the browser? Tell me where, but don't print the key.
4. Which values from .env does the build need?
If DropTheHassle is connected, put the built folder online with it and give me the live link and the claim link.

Questions

How do I get my vibe-coded app online?

If your project has a package.json, run npm run build first, or ask your AI to, and take the dist folder. Then open dropthehassle.com, press Upload (free) and drop the folder in. A few minutes later it's live on a free yourname.dropthehassle.app link with HTTPS. Hit Claim this site on that same screen so it stays.

Where should I host what I vibe-coded?

If it is pages only, on any host that takes a finished folder, such as DropTheHassle, Netlify or Cloudflare Pages. If it also has its own server, the pages can still go there, and only the server part needs a machine that keeps running.

Can you deploy a vibe-coded app for free?

Yes, the pages at least. Drop the built folder on dropthehassle.com for a free yourname.dropthehassle.app link with HTTPS and no card, and claim it so it stays. You only pay for your own domain: a .com is €19 / $19 a year, including VAT in the EU, the same every year.

Do I need GitHub to host my app?

No. GitHub helps if you want a host to build from your repo on every change. You can also upload the built folder yourself, or let your AI do it. A first deploy here needs no GitHub, no account and no token.

Can I keep using Supabase or Lovable Cloud?

Yes. Your pages keep calling them from the new address. Put the keys in .env before you build, and add the new address to the allowed redirect URLs if people sign in.

Can you put a vibe coded app on the App Store?

Not through a web host. Hosting makes it a website, which opens in any phone browser. The App Store is a separate route, with its own app build and Apple's review.

Can my AI buy the domain for me?

No. It can check whether a name is free and hand you a payment link, but it can never spend your money. You pay yourself, through Stripe.

Where to go next

Know which folder it is? Then the hosting part takes a couple of minutes.

Drop your folder, free