# DropTheHassle guides
# https://dropthehassle.com/llms-full.txt
# Generated by deploy/build-sitemap.py. Do not edit by hand.

---
# https://dropthehassle.com/guides

Guides: put your AI-built site on your own domain
Pick the tool you used. The steps are the same: a folder with index.html, then your own domain. You already built it. Now it's on your name.
One command from the terminal: npx -y dropthehassle@latest deploy.
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.
Start here
Host an HTML file for free: put your AI-made page online. Save the HTML or the zip, drop the folder, and it's on a free HTTPS link. No account.
Quick answers
How do I get my site online?. Drop the folder, free HTTPS link in minutes.
My site works on my computer but not online. The 5 usual causes, and a prompt for your AI.
How do I get my Claude Code site online?
How do I get my Cursor project online?
Where should I host my vibe-coded app?. Pages only, pages plus a service, or a server: what goes where.
Can I put my site online without GitHub?. Yes: drop the folder, no repo or terminal.
How do I update my site after it's online?. Drop the new folder, the old one stays live until then.
By tool
Put your Claude Code website online, then on your own domain
Claude Code on the web: put your site live on your own domain
Deploy a Codex-built site to your own domain
Put your Cursor website online, then on your own domain
Put your Windsurf website online, then on your own domain
ChatGPT made me a website: how do I put it online?
Claude made me a website: how do I publish it?
Publish a Gemini Canvas app as a real website, on your own domain
Lovable custom domain without a paid plan, step by step. Build once, drop the folder, free HTTPS link, then a .com.
Put a new Lovable app online. For Lovable apps made from 13 May 2026 (TanStack Start).
Downgrading Lovable: does your domain keep working?
Move your app off Lovable or Replit
Lovable custom domain not working
Bolt.new custom domain: put your site on your own name. Export, build once, drop the folder, free HTTPS link, then a .com.
Guides
Is there an MCP server to publish my site and manage the domain?
How do I hand a website and domain to a client?
Website design
Make your AI-built website look less AI. 12 fixes for the purple-gradient look, each with before and after code.
Design skills for Claude Code, Cursor and Codex. What frontend-design, emil-design-eng, Impeccable, Taste Skill and Vercel's guidelines do, and how to install them.
Compare
Netlify vs Vercel vs Cloudflare Pages, with renewal
AI app builders with your own domain, compared
GoDaddy Node.js Hosting vs DropTheHassle for AI-built apps
Nederlands
Eigen domein koppelen aan je Lovable- of Bolt-site
Wat een zakelijk e-mailadres met je eigen domein echt kost
Je website is gemaakt met Claude Code. Zo zet je hem online
ChatGPT heeft je website gemaakt. Zo zet je hem online
Hoe zet ik mijn vibe-coded website online?
Hoe zet ik mijn Cursor-project online?
Kan ik een website online zetten zonder hosting?

---
# https://dropthehassle.com/guides/put-ai-html-online

Host an HTML file for free: put your AI-made page online
Short answer: Save the code from ChatGPT or Claude as a file called index.html, put it in a folder, and drop that folder (or the zip the chat gave you) on dropthehassle.com. It's online straight away on a free yourname.dropthehassle.app link with HTTPS, with no account and no card. Claim it with your email to keep it, and add your own .com whenever you're ready.
You already made it. Now it's live under your name. This page is for you if a chat gave you a page of code (or a zip) and you're wondering how other people can open it. No coding, no hosting account, no terminal.
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: 30 September 2026.
Step 1. Turn the chat's code into a file
A website is just a file called index.html. Browsers open it automatically as the home page.
From ChatGPT: in the code block, click Copy (or Download if you see it).
From Claude: open the artifact, then copy or download the code. (Claude's own Publish button gives you a claude.ai link, not your own address.)
Then save it:
Mac: open TextEdit, choose Format, then Make Plain Text, paste, and save as index.html.
Windows: open Notepad, paste, choose File, then Save as, set "Save as type" to All files, and name it index.html.
Put that file in a new, empty folder (for example "my-site").
Got several files, or a React component? Ask the chat: "Rewrite this as one self-contained index.html with all CSS and JavaScript inline." One file is the easiest to publish.
Got a zip? You can upload the zip itself. index.html can sit at the top of the zip, inside one wrapper folder, or inside a build folder such as dist, build, out, public, _site, .output/public or docs. If the zip has one other HTML file and no index.html, for example home.html, that file is served as the home page. A project that still needs a build (it has package.json and no built folder) is refused: run npm install and npm run build, then upload the folder the build wrote.
Step 2. Upload it
Go to dropthehassle.com and click Upload (free). You do not sign in first.
Click Drop your folder. The next screen says Drop your folder or .zip. Drop your folder, or the zip. The other control, or browse, picks a folder on your computer. It does not pick a zip.
Done: your site is online at an address like yourname.dropthehassle.app, with HTTPS (the padlock in the browser). No account, no card.
Send the link to a friend, or open it on your phone.
Step 3. Keep it: claim it
Click Claim this site, type your email and the 6-digit code we send you. Until you do:
the claim link works until the site is removed. An unclaimed site is kept for at least 7 days. Once claimed, the free link stays;
search engines are asked not to list it ("noindex"), so it won't show up in Google yet;
visitors see a small bar at the bottom. It says Made with DropTheHassle and has a Claim this site link. They can close it. It also has a Report abuse link;
the upload can be at most 25 MB and 1,000 files. After claiming, uploads can be 100 MB and 5,000 files.
Step 4 (optional). Your own name, like yourname.com
Buy it here: search for a name in your dashboard and pay yourself. It's connected to your site automatically, so there are no DNS settings. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
Already bought one somewhere else? Leave it there and add one A record: a single line in your domain's settings that says which server your site lives on. You set it once, using the address shown on your screen. HTTPS is set up for you.
Good to know
Your pages go online as they are: HTML, CSS, images and JavaScript. A database, a login or code that runs on a server (PHP, Python, Node) is a server part. 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.
AI features inside the page stop working. Buttons that called ChatGPT, Claude or Gemini from inside their app won't work outside it.
Links between your pages work, and so does refreshing a sub-page: if an address isn't a real file, the site serves your index.html.
Your AI can publish it for you, but it can never spend your money. If you use Claude Code, Cursor or Codex, see deploy with your AI. Buying a domain is always your own click.
Other free options exist too (Netlify Drop, GitHub Pages, Cloudflare Pages, tiiny.host). They're fine for one page; putting your own domain on them usually means editing DNS yourself.
Questions
How do I put my website online?
Save your page as index.html in a folder, go to dropthehassle.com, click Upload (free) and drop the folder. You get a free link with HTTPS right away, with no account. Claim it with your email to keep it.
I made a website with ChatGPT. How do I put it online?
Copy the code ChatGPT gave you, save it as index.html in a folder, and drop the folder on dropthehassle.com. If ChatGPT gave you several files, ask it: "Rewrite this as one self-contained index.html with all CSS and JavaScript inline."
Can I host an HTML file for free?
Yes. A single index.html, or a folder or zip with index.html, gets a free yourname.dropthehassle.app link with HTTPS and no card. index.html can sit inside one wrapper folder or a build folder. Unclaimed sites can be up to 25 MB and 1,000 files. The claim link works until the site is removed. An unclaimed site is kept for at least 7 days. Once claimed, the free link stays and uploads can be 100 MB and 5,000 files.
Why does my page look blank or unstyled online?
The page is probably looking for a CSS file or image that wasn't uploaded. Put every file next to index.html with the exact same name, or ask the AI to put everything inline in one file, then upload again.
Can I use my own domain name?
Yes. A .com is €19 / $19 a year, including VAT in the EU, the same every year. Buying it here means no DNS settings. A domain you already own needs one A record.
Do I need to know how to code?
No. If you can save a file and drag a folder, you can put the site online. Your AI can also publish it for you, but it can never spend your money.
By tool
ChatGPT made a website
Put a Claude artifact online
Gemini Canvas
Lovable
Bolt.new
Claude Code
Cursor

---
# https://dropthehassle.com/guides/lovable-custom-domain

Lovable custom domain without a paid plan, step by step
Short answer: You can put a Lovable app on your own domain without Lovable's paid plan. Get the code out through GitHub, build it once so you have a dist folder, and drop that folder on dropthehassle.com: it goes live on a free HTTPS link straight away, no account needed. Then buy a .com there (no DNS settings to touch) or point a domain you already own with one A record. If your app uses Lovable Cloud or Supabase, that backend stays where it is and keeps working.
If you'd rather let an AI do the deploy: npx -y dropthehassle@latest deploy in the folder with the dist.
This is for you if Lovable wants a paid plan before it'll put your own domain on the app, or if you'd simply like the app somewhere you control. You don't need to code. You will copy a few short commands, or have an AI tool run them for you.
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.
First, one thing to know
Lovable shows you a working app, but what's inside your project is the recipe, not the finished dish. Before anyone can host it, it has to be built: turned into a folder of plain files (usually called dist) that a browser can open. You do this once each time you want to publish a new version.
Step 1. Get your code out of Lovable
In Lovable, connect your project to GitHub. GitHub is a free website that stores code; the connection is available on every Lovable plan.
Open your project on github.com, click the green Code button, then Download ZIP.
Unzip it. You now have a folder with your project in it.
(On a paid Lovable plan you can also download the code directly.)
Step 2. Build it once
Made your app on or after 13 May 2026? Then it's a TanStack Start app, and npm run build won't give you a plain dist folder you can drop. This guide is for the older kind, built with React + Vite. To check, open package.json: if it lists @tanstack/react-start, you have the newer kind. For that one, follow Put a new Lovable app (TanStack Start) online.
Option A: on your own computer.
Install Node.js from nodejs.org (the "LTS" version). It's the free program that does the building.
Open a terminal in your project folder. A terminal is the window where you type commands: on a Mac, right-click the folder and choose Services, then New Terminal at Folder (or open Terminal, type cd with a space, drag the folder into the window and press Enter); on Windows, open the folder, click the address bar, type cmd and press Enter.
Type these two commands, pressing Enter after each and waiting until it finishes:
npm install
npm run build
A new folder called dist appears. That's your finished site.
Option B: let an AI do it. If you use Claude Code, Cursor or Codex, open the project there and ask: "Build this project and deploy the dist folder with npx -y dropthehassle@latest deploy. Show me the live link and the claim link." Then skip to step 4.
Step 3. Upload the dist folder
Go to dropthehassle.com and click Upload (free). You do not sign in first.
Click Drop your folder. The next screen says Drop your folder or .zip. Drop the dist folder, or a .zip of it. The other control, or browse, picks a folder on your computer. It does not pick a zip.
A few seconds later your app is live on a free address like yourname.dropthehassle.app, with HTTPS (the padlock). No account, no card.
A zip that still has dist inside another folder is fine. That dist folder is what goes live. A zip of the project before you build is refused.
Step 4. Claim it to keep it
Click Claim this site, type your email, and enter the 6-digit code we send you. Now the site is on your account. Until you claim it:
the claim link works until the site is removed. An unclaimed site is kept for at least 7 days. Once claimed, the free link stays;
search engines are asked not to list it (it's marked "noindex");
there's a small bar at the bottom. It says Made with DropTheHassle and has a Claim this site link. Visitors can close it. It also has a Report abuse link;
it can be at most 25 MB and 1,000 files. After claiming, uploads can be 100 MB and 5,000 files.
Step 5. Put it on your own domain
Buy the domain here. Search a name in your dashboard and pay yourself. The domain is attached to your site automatically, so there are no DNS settings to touch. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
Use a domain you already own. Keep it where you bought it and add one A record. An A record is one line in your domain's settings that says which server your site lives on. You set it once, at the company where you bought the domain, using the address shown on your screen. HTTPS follows by itself.
If your app has a backend (Lovable Cloud or Supabase)
We only host the front end (the pages people see). Your backend (the database, logins and server functions in Lovable Cloud or Supabase) stays where it is and keeps its own plan and costs. Running your own server instead? Host it on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card. The published site keeps talking to your backend, as long as:
the .env file (it holds the address of your backend) is in the project folder before you build;
your new domain is on the list of allowed login addresses, if people sign in. In Supabase that's Authentication, then URL Configuration. For Lovable Cloud, open More → Cloud → Users → Auth settings → Advanced and add it there, or ask Lovable in the project chat to add your domain to the auth redirect URLs.
Good to know
Sub-pages and refreshes work. When an address isn't a real file, the site serves your index.html, so /about or /dashboard still opens after a refresh.
Only finished files. A folder that still needs building is refused, and so is anything that needs its own server to run (PHP, a Node or Python server).
Buying a domain is always your own click, even when an AI did the publishing.
Stuck on a domain you connected inside Lovable? See Lovable custom domain not working.
Common mistakes
Uploading the GitHub download as it is. What Lovable pushes to GitHub is the source code. A project zip before build is refused. Run the two commands from step 2 first and drop dist.
Building without the .env. If the app uses Lovable Cloud or Supabase, the .env has to sit in the folder when you build. Add it afterwards and the live app won't reach its backend.
People land back on the lovable.app address after signing in. The new domain isn't on the allowed list yet. Add it as described in the backend section above.
Old DNS from when Lovable had the domain. Point the A record at the address on your screen and delete any old AAAA record for that name. If the domain sits on Cloudflare, switch that record from the orange cloud to DNS only.
The www version won't load. www needs its own DNS entry. Once that points here too, it works.
Waiting too long to claim. Sites nobody claims are removed after at least 7 days, so do it right after the upload.
Questions
Can I use my own domain on Lovable's free plan?
Not inside Lovable: custom domains in Lovable need a paid plan. You can still put the app on your own domain by building it once and publishing the dist folder on DropTheHassle. The free link costs nothing. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
How do I connect my domain to Lovable?
On a paid Lovable plan: open Project, Settings, Domains, choose Connect domain, and add the A and TXT records Lovable shows at the company where you bought the domain. Without a paid plan: publish the built dist folder here, then point your domain with one A record, or buy a .com here with no DNS edit.
How do I get my Lovable app off Lovable?
Connect the project to GitHub (every plan can), download the code as a ZIP from GitHub, run npm install and npm run build, and upload the dist folder that appears.
Will my Lovable Cloud or Supabase backend still work?
Yes. The backend stays where it is, and the published site keeps talking to it. Make sure the .env file is in the folder before you build, and add your new domain to the allowed login addresses if people sign in. For Lovable Cloud that's More → Cloud → Users → Auth settings → Advanced.
My Lovable domain is not working. What now?
If you connected the domain inside Lovable and it's stuck (SSL pending, Offline, a Cloudflare error), follow the fixes on our Lovable custom domain not working page. If you'd rather skip DNS, publish the built folder here and buy the .com with the site.
Do refreshes and sub-pages work?
Yes. When an address isn't a real file, the site serves your index.html, so a page like /about still opens after a refresh.
What does it cost?
The yourname.dropthehassle.app link is free and needs no card. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
Related
Downgrading Lovable: does your domain keep working?
Move your app off Lovable or Replit
Lovable custom domain not working
Make your Lovable site look less AI
The same job for a Bolt.new site
Made a website with ChatGPT or Claude?
Netlify vs Vercel vs Cloudflare, with renewal prices
Works locally, not online? Here's why
Nederlands

---
# https://dropthehassle.com/guides/lovable-downgrade-keep-custom-domain

Downgrading Lovable: does your custom domain keep working?
Short answer: Yes. Lovable's own docs say a domain that is already connected keeps serving your published app after you downgrade to Free or cancel, and the project is not unpublished. What changes: on Free you can't connect a new domain (or reconnect one), the "Edit with Lovable" badge comes back the next time you publish, apps that use Lovable Cloud or AI features still need credits, and a domain you bought through Lovable keeps renewing and charging separately. If one of those is a problem, you can host the built front end somewhere else, for example on DropTheHassle, without a subscription.
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: 30 September 2026. Everything we say about Lovable below comes from Lovable's documentation as it read on that date; links are at the bottom of this page.
You're not the only one asking
These are real questions from r/lovable in August and September 2026:
"If I downgrade my Lovable account from Pro to Free, will my website remain published and fully functional with my custom domain?"
"will the custom domain continue serving the project, or will it be disconnected/replaced by the Lovable subdomain?"
"I don't really want to keep paying Lovable $25/month just to keep the custom domain"
The good news: you don't have to keep paying just for the domain.
What keeps working after you downgrade
According to Lovable's docs:
Your published app stays live. Downgrading or canceling does not unpublish it.
A domain that's already connected keeps serving it. It is not disconnected or swapped for the lovable.app address.
Nothing gets unpublished. You can still disconnect a domain, or unpublish, on any plan.
The website itself doesn't use credits. Lovable says a live site doesn't consume credits on its own.
What changes
After a downgrade to Free What that means for you
You can't connect a new domain Also not one that's already in your workspace. If you ever disconnect your domain, you can't put it back without upgrading.
The "Edit with Lovable" badge returns on your next publish Your live site keeps the badge hidden until you publish again. Then Lovable warns you and brings it back.
Lovable Cloud and AI features still need credits The pages keep loading, but logins, the database and AI calls run on credits. If the workspace has no credits at all, a Cloud backend can be paused.
A domain bought through Lovable keeps renewing It's billed separately from your plan, so auto-renew keeps charging.
Downloading your code directly stops "Download codebase" is a paid-plan feature. GitHub sync works on every plan.
Newer apps have a traffic cap on Free Apps created from 13 May 2026 are limited to 1,000 server requests per project per 10 seconds on Free.
One more for Business-plan users: an app published only to your workspace or to selected people stays live, but you can't publish changes to it on Free or Pro until you set its access to Public.
Before you click downgrade
Check the domain shows Live in Project → Settings → Domains. Because you can't connect a domain on Free, make sure everything is set up the way you want it first.
Get a copy of your code. Connect the project to GitHub (every plan can), or use Download codebase in Project settings → Git while you still have the paid plan.
Publish your last changes now if the badge matters to you. After the downgrade, the next publish brings it back.
Decide about a domain bought through Lovable. If you don't want it to renew, turn off auto-renew in Workspace settings → Workspace domains. You can also transfer it out from there (not in the first 60 days after you bought it).
Downgrade in Workspace settings → Plans & credit usage → Manage → Downgrade to free. You keep your current plan until the end of the billing period.
When hosting it somewhere else makes sense
For many people, downgrading is enough: the site stays up and the domain keeps working. Moving the front end elsewhere is worth it if you want to:
keep publishing changes without the "Edit with Lovable" badge;
connect a domain later, or change domains, without a paid plan;
have a copy of your site that doesn't depend on your Lovable plan.
Your backend doesn't move with it. If your app uses Lovable Cloud, it keeps running in Lovable and keeps using Lovable credits, wherever the pages are hosted. For moving the backend too, see How to move your app off Lovable or Replit.
The no-subscription route: DropTheHassle
Build the app so you have a folder of plain files, then drop that folder here.
For a React + Vite app:
Build it once. Put the .env file in the project folder, then run npm install and npm run build. That creates a dist folder. The full beginner steps are in Put your Lovable app on your own domain.
Drop the dist folder on dropthehassle.com (Upload (free) → Drop your folder). It goes live on a free yourname.dropthehassle.app link with HTTPS. No account, no card.
Claim it to keep it with your email and a 6-digit code. The claim link works until the site is removed. An unclaimed site is kept for at least 7 days. Once claimed, the free link stays. Until you claim it, the site is marked noindex and shows a small bar visitors can close. Before claim, an upload can be 25 MB and 1,000 files. After claiming, uploads can be 100 MB and 5,000 files.
Point your domain at it with one A record, using the address shown on your screen. Connecting a domain is free. Or buy a new one with the site and skip DNS entirely. A .com costs €19 / $19 a year, including VAT in the EU, the same every year (.org and .net the same; .nl and .eu 12; .app 25).
Add the new address to your login settings if people sign in. For Lovable Cloud that's More → Cloud → Users → Auth settings → Advanced. For your own Supabase project, it's that project's auth settings.
Moving the domain from Lovable:
Bought somewhere else (GoDaddy, Namecheap, Cloudflare…): at that company, replace Lovable's A record with ours, then disconnect the domain in Lovable. Remember that on Free you can't connect it to Lovable again.
Bought through Lovable: Lovable lets you edit DNS records in Workspace settings → Workspace domains → Configure, or transfer the domain out to another registrar. We haven't tested whether editing records still works on Free; transferring out does, according to Lovable's docs.
Sub-pages and refreshes work: when an address isn't a real file, we serve your index.html. Your AI can publish for you (npx -y dropthehassle@latest deploy), but it can never pay; buying a domain is always your own click.
And Bolt?
Bolt is different. Its docs say custom domains are only on paid plans, and after a downgrade to Free you can no longer publish to your custom domain. That's why people ask things like "How do u integrate a custom domain on bolt for free? without bolt pro". The answer is in Put your Bolt.new site on your own domain.
Questions
If I downgrade Lovable to Free, will my custom domain keep working?
Yes, if it's already connected. Lovable's docs say connected domains keep serving your published app and downgrading or canceling does not disconnect domains or unpublish the project. You can't connect a new domain on Free.
Will my Lovable site go offline when I cancel?
No. Lovable says a published app stays live after a downgrade or cancellation. Apps that use Lovable Cloud or AI features still need available credits to serve those requests.
Will the "Edit with Lovable" badge come back?
Yes, on your next publish. If you hid the badge on a paid plan, the live site keeps it hidden until you publish again; then Lovable brings the badge back. Hosting the built files elsewhere avoids that, because the badge setting is Lovable's.
Can I connect a different domain after downgrading?
Not inside Lovable. After a downgrade to Free you can't buy or connect domains, including ones already in your workspace, until you upgrade. You can connect any domain to a site on DropTheHassle with one A record, for free.
Do I still pay for a domain I bought through Lovable?
Yes. Domains bought through Lovable are billed separately from the subscription, and auto-renew keeps charging. The workspace owner can turn off auto-renew or transfer the domain out in Workspace settings → Workspace domains.
Should I download my code before downgrading?
It's a good idea. Downloading the codebase directly from Lovable is a paid-plan feature; GitHub sync works on every plan. Connect GitHub, or download the code, while you still have the paid plan.
Does this work the same on Bolt?
No. Bolt's docs say custom domains are only on paid plans and that after a downgrade to Free you can no longer publish to your custom domain. See our Bolt guide for the free route.
Related
Put your Lovable app on your own domain, step by step
Lovable custom domain not working
How to move your app off Lovable or Replit
Put your Bolt.new site on your own domain
AI app builders with your own domain, compared
Nederlands

---
# https://dropthehassle.com/guides/lovable-tanstack-static

Put a new Lovable app online as a static site
Lovable apps made from 13 May 2026 onward are TanStack Start apps. As they are, they run on a server, so npm run build doesn't give you a folder you can drop. Build a static copy in SPA mode instead and drop the dist/client folder. Pages that use server functions or /api routes need the app's server: run the whole app on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card.
Your AI can publish. It can never spend your money.
Last updated: 2 October 2026.
Is this you?
Open package.json. If it lists @tanstack/react-start and vite.config.ts uses @lovable.dev/vite-tanstack-config, this guide is for you. Another TanStack Start app without that wrapper: remove the nitro() plugin from the copy instead of adding nitro: false. The build lands in the same dist/client folder. An older Lovable app (React + Vite) builds a plain dist folder: follow the Lovable custom domain guide instead.
First get the code onto your computer: connect the project to GitHub in Lovable (every Lovable plan can), then clone it. You need Node.js 22.12 or newer.
Build a static copy in 5 steps
Leave vite.config.ts as it is, so Lovable keeps building the app its own way. Make a copy of it called vite.config.dth.ts.
In vite.config.dth.ts, add spa: { enabled: true } to the tanstackStart options. If there are none, add tanstackStart: { spa: { enabled: true } }. Also add nitro: false (an option of the Lovable wrapper).
Run npm install, then npx vite build --config vite.config.dth.ts.
Check that dist/client/_shell.html exists. If it doesn't, the build did not run in SPA mode: check step 2.
Drop the dist/client folder at dropthehassle.com. You get a free address like https://something.dropthehassle.app. No card. We use _shell.html as the start page, and every page of the app opens from it.
Or let your AI do it. Paste this into Lovable, Claude Code, Cursor or any AI that can run commands in the project:
Build this TanStack Start app as static files, without changing how it runs on Lovable. Leave vite.config.ts as it is. Create vite.config.dth.ts as a copy of vite.config.ts, then: add spa: { enabled: true } to the tanstackStart options (add tanstackStart: { spa: { enabled: true } } if there is none), and add nitro: false. Run npm install, then npx vite build --config vite.config.dth.ts. Check that dist/client/_shell.html exists. Then list every server function (createServerFn, files ending in .functions.ts) and every /api route, because those only work once the whole app runs on AWS, Google Cloud, DigitalOcean or my own server, connected in the DropTheHassle Backend card, and tell me which pages use them. Tell me when dist/client is ready to upload.
When the app needs its server
Server functions (createServerFn, files ending in .functions.ts) and /api routes need the app's server; the static copy works without them. List them before you upload and check which pages use them. To keep them, run the whole app (its normal build, with the server) on AWS, Google Cloud, DigitalOcean or your own server. Then connect it in the Backend card of your claimed site with the path /*, so every path goes to it, behind your own domain. Your AI can do it for you through our hosted connector. Or keep the app on Lovable as it is. Moving the whole app is in Move your app off Lovable or Replit.
On your own domain
A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year. No DNS edit. A domain you already own needs one A record: one line at the company where you bought the domain, set to the address shown on your screen. Press Check now. HTTPS follows.
Publish your site for free
Questions
Why won't my new Lovable app upload as it is?
Lovable apps made from 13 May 2026 onward are TanStack Start apps. As they are, they run on a server, so npm run build gives no folder to drop. A static copy built in SPA mode is a set of files we put online. Or run the whole app on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card.
What about server functions and /api routes?
They need the app's server, so the static copy works without them. To keep them, run the whole app on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card. Pages, routing and anything the browser does on its own work in the static copy straight away.
Does this change my app on Lovable?
No. vite.config.ts stays as it is. The static build uses its own copy, vite.config.dth.ts, so Lovable keeps building the app its own way.

---
# https://dropthehassle.com/guides/move-off-lovable

Move your app off Lovable or Replit: where to host it
Short answer: Moving off Lovable or Replit is two jobs: the front end (the pages people see) and the backend (database, logins, server code). A Lovable app becomes a folder of plain files after npm run build, and any host for built files can serve it, for example DropTheHassle (no account, free link, your own domain with one A record). The backend can stay on Lovable Cloud, which still uses Lovable credits, or move to your own Supabase project; there is no one-click migration. A server of your own runs on AWS, Google Cloud, DigitalOcean or your own server, connected in the Backend card. A Replit Static Deployment has no backend server and moves like a plain site.
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: 30 September 2026. Claims about Lovable and Replit come from their own documentation on that date; links are at the bottom of this page.
You're not the only one asking
"How to move out of lovable??"
"I don't want to spend any cash on hobby project but want to keep it running."
"Do you think I should also move the Lovable website to another server or hosting provider, just to reduce the risk?"
These are from r/lovable in August and September 2026. Moving is very doable, but you need to know which parts can move where.
First: do you need to move at all?
Lovable: if the only reason is money, you may not have to. Lovable's docs say a published app stays live after a downgrade to Free and a connected domain keeps working. What changes is explained in Downgrading Lovable: does your custom domain keep working?
Replit: on the free Starter plan, Replit's docs say you get one free published app and that its link goes down after 30 days. Downgrading doesn't delete anything ("Your projects and data stay intact"), but to keep a site up for free, a move is the practical option.
Step 1. What kind of app do you have?
This decides everything else.
Your app What it is Can it go on DropTheHassle?
Lovable app (React + Vite) Pages as plain files after a build; the backend lives separately Yes. The front end can.
Replit Static Deployment "There is no backend server" (Replit's words) Yes.
Replit Autoscale or Reserved VM deployment A running server Yes, with the Backend card: run the server on AWS, Google Cloud, DigitalOcean or your own server and connect it.
How to tell: in Replit, check which deployment type you chose when you published: Static, Autoscale or Reserved VM.
Step 2. Get your code out
Lovable: connect the project to GitHub. That works on every plan. Then download it from GitHub (green Code button → Download ZIP). On a paid plan you can also use Download codebase in Project settings → Git. Do that before you downgrade.
Replit: in the file tree, open the three-dot menu at the top and choose Download as zip.
Step 3. Host the front end
For a static app, build it once: put the .env file in the project folder (it holds your backend's address, and it's baked in when you build), then run npm install and npm run build. You get a dist folder. Step-by-step help for beginners is in Put your Lovable app on your own domain.
Then choose a host. All of these can serve a dist folder over HTTPS:
Host Good for Keep in mind
DropTheHassle Dropping a finished folder with no account, then adding a domain Built files; your server connects in the Backend card. The claim link works until the site is removed. An unclaimed site is kept for at least 7 days. Once claimed, the free link stays. Before claim, an upload can be 25 MB and 1,000 files. After claiming, uploads can be 100 MB and 5,000 files. Noindex until claimed
A server of your own (AWS, Google Cloud, DigitalOcean or your own machine) The backend: database, logins, server code Connected in the Backend card, so it runs behind your own domain here
For prices and renewals, see Netlify vs Vercel vs Cloudflare Pages. We don't list their prices here because they change.
On DropTheHassle: go to dropthehassle.com, click Upload (free), then Drop your folder and choose dist (a .zip works too). A few seconds later it's live on yourname.dropthehassle.app with HTTPS. Click Claim this site, enter your email and the 6-digit code, and it's yours. The free link stays free. Prefer your AI tool? npx -y dropthehassle@latest deploy does the same, but paying is never something it can do.
"My site is blank on my own domain"
"when I type my custom domain, my site is fully blank"
When a moved app shows a white page, it's usually one of these:
The .env file was missing when you built. The app can't find its backend. Add it and build again.
You uploaded the project instead of the build. Upload the dist folder, not the folder with src in it.
Sub-pages give a 404 after a refresh. The host has to send unknown paths to index.html. On DropTheHassle that's automatic. Lovable's docs explain how to set it up for Netlify, Cloudflare and others.
If the domain is still connected inside Lovable and that's what's broken, see Lovable custom domain not working.
Step 4. Decide where the backend lives
We don't host backends, so this part is between you and Lovable, Supabase or Replit. Your options:
A. Leave it on Lovable Cloud (the easiest) Your new front end keeps talking to it. It still uses Lovable credits for logins, the database and AI calls. Lovable pauses idle Cloud projects automatically, and while a backend is paused, your app can't read or write data. If people sign in, add your new address under More → Cloud → Users → Auth settings → Advanced.
B. Move it to your own Supabase project Lovable Cloud is built on Supabase, so this is the closest match, but it isn't one click. From Lovable's docs:
The database schema and storage buckets come across through SQL migrations.
Data: export tables as CSV, or request a full database export in More → Cloud → Overview → Advanced settings. That export is limited to databases up to 15 GB, a 5 GB file, and one export per 24 hours.
The export does not include storage files, Edge Function code or secrets. Move those yourself.
User accounts come with their password hashes, so users keep their passwords. Sign-in providers have to be set up again, and people who are signed in have to sign in again.
Then update the VITE_SUPABASE_* values in .env and build again.
C. Run the backend yourself (self-hosted Supabase or another platform) Possible, but Lovable points out you then own backups, security, monitoring and auth settings yourself. That's a lot for a hobby project.
Replit database: Replit's docs show how to export data from the Database tool (My Data) or with pg_dump. Your new backend host has to run the server part of your app.
Step 5. Move the domain last
Only switch the domain once the new site works on its free link.
Domain bought elsewhere: change its A record to the one shown in your DropTheHassle dashboard, then disconnect it on the old platform. One A record is all we need, and connecting is free.
Domain bought through Lovable: the workspace owner can transfer it out in Workspace settings → Workspace domains (Transfer out: turn off the transfer lock, then reveal the authorization code). New domains are locked for 60 days.
Domain bought through Replit: transfers go through Replit Support, also with a 60-day wait after purchase. Leave time for it. One person who moved off Replit wrote: "Replit needs to release my custom domain from its managed Clerk integration."
No domain yet? Buy one with your site on DropTheHassle and there's nothing to set up. A .com costs €19 / $19 a year, including VAT in the EU, the same every year (.org and .net the same; .nl and .eu 12; .app 25).
What we don't do
No servers run here. Databases, logins, server functions and API routes run on AWS, Google Cloud, DigitalOcean or your own server, connected in the Backend card.
No automatic builds from GitHub. You upload a finished folder (or your AI does).
If your app is mostly backend, host it on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card: it then runs on your own domain here, with HTTPS and email. If it's pages that talk to a backend somewhere else, we're the shortest route to your own domain.
Questions
How do I move my app out of Lovable?
Connect the project to GitHub (every plan can) to get the code. For a React + Vite app, put the .env file in the folder, run npm install and npm run build, and upload the dist folder to any host for built files. The backend stays on Lovable Cloud unless you move it to your own Supabase project yourself.
Do I have to leave Lovable to stop paying?
Not necessarily. Lovable's docs say a published app stays live after a downgrade, and a connected domain keeps working. Apps using Lovable Cloud or AI features still need credits.
Can DropTheHassle host my Lovable backend?
Not on our machines: we don't run servers. Your database, logins and server functions stay on Lovable Cloud or Supabase, or run on AWS, Google Cloud, DigitalOcean or your own server, connected in the Backend card. The published pages keep working with them.
Why is my site blank on my own domain?
Common causes: the .env file wasn't in the folder when you built, you uploaded the project folder instead of the built dist folder, or the host doesn't send unknown paths to index.html. On DropTheHassle unknown paths already serve index.html.
How do I move a Replit app?
If it's a Static Deployment (no backend server), download the project as a zip from the three-dot menu at the top of the file tree, build it if needed and upload the output. Apps with a server: run it on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card; export the database first.
What about a domain I bought through Lovable or Replit?
Lovable lets the workspace owner transfer it out in Workspace settings → Workspace domains. Replit transfers go through Replit Support. Both have a 60-day lock after purchase. Or keep it there and only change its DNS.
Related
Downgrading Lovable: does your custom domain keep working?
Put your Lovable app on your own domain, step by step
Lovable custom domain not working
Put your Bolt.new site on your own domain
Netlify vs Vercel vs Cloudflare Pages, with renewal prices
AI app builders with your own domain, compared
GoDaddy Node.js Hosting vs DropTheHassle for AI-built apps
Deploy with your AI (MCP)

---
# https://dropthehassle.com/guides/bolt-custom-domain

Bolt.new custom domain: put your site on your own name
Short answer: You can put a Bolt.new site on your own domain without Bolt's paid plan. In Bolt choose Export → Download, unzip, run npm install && npm run build to get a dist folder, and drop that folder on dropthehassle.com (or run npx -y dropthehassle@latest deploy dist): it goes live on a free HTTPS link right away, no account needed. Then buy a .com for €19 / $19 a year with no DNS settings, or connect a domain you already own with one A record.
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.
Publish your site for free
Bolt will attach a domain for you on its paid plan. If paying every month just so a finished site can have a name feels like a lot, here's the other way, one step at a time.
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 export path (project title, then Export, then Download) matches Bolt's project files page (checked 2 October 2026). The downgrade line is from Bolt's domains page.
First, one thing to know
An export from Bolt gives you the project: the source files. A web host needs the built site, a folder of plain files (usually dist) that a browser can open as it is. Building is one or two commands, and you only do it again after you change something.
Step 1. Export from Bolt
In Bolt, click the project title at the top.
Choose Export, then Download. You get a .zip file.
Unzip it (double-click on a Mac; right-click, then Extract All on Windows).
Your environment variables (keys, like the address of your database) are not in the download. If your site uses any, put them in a file called .env in the project folder before you build.
Step 2. Build it once
Look inside the folder.
Only an index.html (and maybe images and CSS), no package.json? It's already built. Skip to step 3.
There's a package.json? Then build it:
Get Node.js, the LTS version from nodejs.org, if you don't have it yet.
Open a terminal (the window you type commands into) inside the project folder. Mac: right-click the folder, Services, New Terminal at Folder. Windows: click in the folder's address bar, replace what's there with cmd and hit Enter.
Type these two, one after the other, and let each one finish:
npm install
npm run build
When it's done there's a dist folder next to your files, and that's the thing you upload. A zip with dist somewhere inside is fine too: that folder is what gets published.
Rather have an AI do this bit? Open the project in Claude Code, Cursor or Codex and ask: "Run npm install and npm run build, then publish dist with npx -y dropthehassle@latest deploy and paste both links back to me, the live one and the claim one."
Step 3. Upload it
Open dropthehassle.com and click Upload (free). No sign-in.
Click Drop your folder, and you land on a screen that reads Drop your folder or .zip. Drag dist, or a zip of it, onto it. Prefer clicking? or browse opens a folder picker, but it won't take a zip.
That's it: the site is up at an address like yourname.dropthehassle.app, on HTTPS, without an account or a card.
Step 4. Claim it so it stays
Click Claim this site, type your email and enter the 6-digit code that arrives. Until you've done that:
the site sticks around for at least 7 days, and its claim link keeps working for as long as the site is there. After the claim, the free link is yours to keep;
it's marked noindex, so search engines are asked to skip it;
a slim Made with DropTheHassle bar sits at the bottom, with a Claim this site link and a Report abuse link. Visitors can close it;
uploads are capped at 25 MB and 1,000 files, which goes up to 100 MB and 5,000 files once it's claimed.
Step 5. Your own domain
Buy it here: pick the name in your dashboard and check out yourself. It's connected to the site for you, so there are no DNS settings. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
Already own one: add one A record where you bought it, using the address on your screen. It's a single line in the domain's settings that tells browsers which server to go to. HTTPS gets set up for you.
Good to know
Refresh away. Any address that isn't a real file gets your index.html, so /pricing still opens after a reload.
Databases and logins stay where they are. We host the pages people see. If your Bolt app uses a database or login service (for example Supabase), that keeps running at its own provider. Add your new domain to its list of allowed login addresses.
Server code runs elsewhere. A site with its own server (Node, PHP, Python): host that part on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card.
Common mistakes
Dropping the Bolt download straight in. That zip is the project, not the site. A project zip before build is refused. Unzip it, build it, and drop the dist folder that appears.
Forgetting the keys. Bolt's download leaves your environment variables out. If the site talks to a database, write the .env before you build, or the live site can't find it.
Logins that bounce to the Bolt preview. Your login service still only trusts the old address. In Supabase, add the new domain under Authentication, then URL Configuration.
A stray AAAA record. Your registrar may still have an old AAAA record (the IPv6 one) for that name, and some visitors will end up there. Delete it. On Cloudflare, keep the A record on DNS only, the gray cloud, while HTTPS is being set up.
www stays dark. To DNS, www is a separate name. It opens once its DNS points here as well.
Leaving it unclaimed. After at least 7 days an unclaimed site is gone. Claim it while the screen is still open.
Questions
Can I use a custom domain on Bolt.new for free?
Bolt attaches custom domains on its paid plan. Without it, export the project, build it once, and publish the dist folder on DropTheHassle: the free HTTPS link costs nothing, and a .com is €19 / $19 a year, including VAT in the EU.
How do I deploy my Bolt.new site to my own domain?
Export, then Download in Bolt, unzip, run npm install and npm run build, and drop the dist folder on dropthehassle.com. Claim the site, then buy a .com with no DNS settings or connect a domain you own with one A record.
Why is my Bolt site blank after uploading?
Usually the project folder was uploaded instead of the built site, or the keys were missing when you built. Build it once and drop the dist folder.
Does my database or login still work?
Put your public keys (for example the Supabase URL and anon key) in a .env file before you build. Never put secret keys there: everything in the built site is public. Add your new domain to your login service's allowed addresses.
Is the free link permanent?
Yes, once you have claimed the site. Until then it is kept for at least 7 days. You can rename the link later, and the old one redirects.
Related
The same job for a Lovable app
On Lovable too? What a downgrade does to your domain
Site from ChatGPT or Claude instead?
Make your Bolt site look less AI
How Netlify, Vercel and Cloudflare compare, renewals included
Nederlands

---
# https://dropthehassle.com/nl/eigen-domein-koppelen-lovable-bolt

Eigen domein koppelen aan je Lovable- of Bolt-site
Je hebt het al gebouwd. Nu staat het op jouw naam. Je Lovable- of Bolt-site kan op je eigen domein zonder het betaalde plan van de bouwer. Zet de gebouwde map online bij DropTheHassle, en wijs daarna een domein dat je al hebt, of koop een .com voor €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde.
Je AI mag publiceren, maar kan nooit je geld uitgeven.
Gemaakt met ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf of met de hand? Dezelfde stappen.
Site gemaakt met ChatGPT of Claude Code? Lees hoe je een ChatGPT-website online zet of een Claude Code-website online zet.
Laatst bijgewerkt: 30 september 2026. Prijzen van Lovable en Bolt komen van hun eigen prijspagina's.
Wat de bouwer vraagt
Bij Lovable vraagt een eigen domein een betaald plan: Pro vanaf $25 per maand of $250 per jaar. Bij Bolt: Pro vanaf $25 per maand, of $18 per maand bij jaarbetaling. Geen van beide levert een postvak. Volgens Lovable blijft een domein dat al gekoppeld is werken na een downgrade, maar een nieuw domein koppelen vraagt weer een betaald plan.
De gratis route via GitHub naar Netlify of Cloudflare Pages bestaat ook. Je zet dan zelf DNS, en een postvak zit er niet bij. Vercel's hobby-plan is gepubliceerd als persoonlijk en niet-commercieel gebruik.
Wat het bij DropTheHassle kost
Jaar 1 Daarna
Link naam.dropthehassle.app €0, geen kaart Blijft gratis
Domein dat je al hebt, alleen de site €0 bij ons. Je betaalt de verlenging bij je eigen registrar. Hetzelfde. Eén A-record. De nameservers (die bepalen wie alle instellingen van je domein beheert, ook je mail) blijven staan.
.com kopen hier €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde Ook bij verlenging: €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde. Geen lokprijs in het eerste jaar.
E-mail, optioneel €5 / $5 per maand voor het eerste postvak, €3 / $3 per maand per extra adres Zelfde bedragen. Zie de mailgids.
Een .nl of .eu kost €12 / $12 per jaar, incl. btw in de EU, elk jaar hetzelfde. Een .org of .net kost hetzelfde als een .com, en een .app €25 / $25 per jaar. Andere extensies bieden we niet aan. De prijs zie je altijd voordat je betaalt.
Stappen
Bij Lovable krijg je op het gratis plan de code via GitHub (de directe download is voor betaalde plannen). Bij Bolt: klik op de projectnaam, dan Export, dan Download. In beide gevallen draai je daarna npm install en npm run build (je hebt Node.js nodig) en sleep je de map dist. Zet sleutels in een .env-bestand voordat je bouwt. Een map zonder pagina om mee te beginnen (geen index.html en ook geen los HTML-bestand) wordt geweigerd, net als een site die een server nodig heeft om te draaien. Zonder claim maximaal 25 MB en 1.000 bestanden. Na het claimen 100 MB en 5.000 bestanden.
Ga naar dropthehassle.com en klik op Upload (free). Inloggen hoeft niet. Klik op Drop your folder en sleep de map dist of een .zip ervan. Een paar seconden later staat je site op HTTPS op een gratis .dropthehassle.app-adres, zonder account en zonder kaart. Klik daarna op Claim this site, vul je e-mailadres in en typ de code van 6 cijfers die we je mailen. De claimlink werkt tot de site wordt verwijderd. Een niet-geclaimde site blijft minstens 7 dagen online. Na het claimen blijft de gratis link. Tot je hem claimt, mag een upload maximaal 25 MB en 1.000 bestanden zijn en vragen we zoekmachines hem niet op te nemen. Na het claimen staat de site op je account en mag een upload 100 MB en 5.000 bestanden zijn.
Of laat je AI het doen. De eerste publicatie heeft geen token nodig. Via https://dropthehassle.com/mcp of via npx -y dropthehassle-mcp@latest (stdio) gaat de site anoniem online en krijg je een claim link. Voor een site die al op je account staat kies je Connect your AI en zet je DTH_TOKEN. Je AI mag publiceren, maar kan nooit je geld uitgeven.
Een A-record is één regel in de instellingen van je domein. Die regel vertelt waar je site staat. Je stelt hem één keer in bij het bedrijf waar je het domein kocht. Open daar de DNS-instellingen van je domein. Zet het A-record op @ naar het adres dat op je scherm staat. Klik daarna op Check now (de knop die controleert of het domein al hierheen wijst). Je domein wordt gekoppeld zodra het naar ons wijst. Wij blijven controleren, dus je kunt gewoon even wachten. HTTPS volgt. (HTTPS is het slotje in de adresbalk: je site is dan beveiligd.) Een certificaat uploaden hoef je niet.
Liever de naam hier kopen: zoek hem in het dashboard en betaal zelf. Een .com is €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde. Dan stel je geen DNS in.
Zet je site gratis online
Waar het misgaat
Single-page apps werken. Is een adres geen echt bestand, dan geven we je index.html met een 200, dus een Vite- of React-app opent op elke eigen route, ook na verversen.
Sleutels zoals een Supabase-adres moeten al in de gebouwde bestanden zitten. Zet ze in .env voordat je bouwt.
Staat er een login op de site, voeg het nieuwe domein dan toe aan de toegestane redirect-URL's (de lijst met adressen waar iemand na het inloggen naartoe mag). Dat doe je bij die dienst, niet hier. Bij Supabase: Authentication, URL configuration. Bij Lovable Cloud: More → Cloud → Users → Auth settings → Advanced, of vraag Lovable in de projectchat om je domein aan de auth-redirect-URL's toe te voegen.
Een oud AAAA-record (een tweede adresregel, voor IPv6) of een proxy (het oranje wolkje bij Cloudflare) kan bezoekers langs een goed A-record sturen. Haal het weg als de site niet laadt.
www werkt hier als de DNS van www ook naar deze server wijst.
Nameservers omzetten naar ns1.dropthehassle.app en ns2.dropthehassle.app is de verhuisroute. Daarmee verhuist ook de mail. Voor alleen de site laat je de nameservers staan en zet je het A-record.
Betalen
Je betaalt via Stripe. Welke betaalmethodes je ziet, zoals iDEAL, zie je bij het afrekenen.
Gerelateerd
Engels, alleen Lovable
Engels, alleen Bolt
Elke tool, of met de hand
Wat een zakelijk e-mailadres kost

---
# https://dropthehassle.com/nl/zakelijk-email-eigen-domein-kosten

Wat een zakelijk e-mailadres met je eigen domein echt kost
Je hebt het al gebouwd. Nu staat het op jouw naam. Je hebt je site al. Nu ook een mailadres op jouw naam. Een echt postvak waar je vandaan mailt kost bij DropTheHassle €5 / $5 per maand voor het eerste adres en €3 / $3 per maand voor elk extra adres. Het domein zelf, een .com, is €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde.
Je AI mag publiceren, maar kan nooit je geld uitgeven.
Gemaakt met ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf of met de hand? Dezelfde stappen.
Laatst bijgewerkt: 26 september 2026.
Eerste jaar en daarna
Aanbieder Eerste stuk Daarna Postvak
TransIP
.com €8,99 het eerste jaar. Email Core €1 per maand als actie.
.com €27,99 per jaar excl. btw. Email Core daarna €6,50 per maand excl. btw.
Ja, bij hun mailproduct.
one.com
.com €12,99 het eerste jaar.
.com €27,99 per jaar.
Mail zit in een apart hostingproduct.
Google Workspace Business Starter
€6,80 per gebruiker per maand excl. btw bij een jaarcontract. Het domein koop je apart.
Flexibel €8,10 per gebruiker per maand excl. btw.
Ja.
DropTheHassle
.com €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde. Eerste postvak €5 / $5 per maand, elk extra adres €3 / $3 per maand. De site op naam.dropthehassle.app is gratis.
Geen introductieprijs. Een .com blijft €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde. Mail blijft €5 / $5 en €3 / $3 per maand.
Ja. Een postvak waar je vandaan mailt, met inbox in het dashboard.
De rijen van andere aanbieders zijn hun gepubliceerde prijzen op 26 september 2026. Controleer hun site voordat je kiest. Strato en Zoho staan hier niet: die bedragen zijn niet opnieuw op hun eigen prijspagina gecontroleerd.
Een postvak is iets anders dan doorsturen
Een echt postvak ontvangt en verstuurt op jouw adres, bijvoorbeeld info@jouwdomein.nl. In het dashboard open je die inbox, lees je mail en antwoord je. Dat is het product van €5 / $5 en €3 / $3.
Doorsturen ontvangt alleen. Het antwoord vertrekt daarna vanaf Gmail of Outlook, dus de ander ziet een ander adres. Spamfilters zijn streng op mail die is doorgestuurd. Sinds januari 2026 haalt Gmail geen mail meer op via POP, dus "Gmail haalt het wel op" is geen route meer.
De site verhuizen zonder de mail kapot te maken
MX is de regel die bepaalt waar je mail binnenkomt. SPF en DKIM zijn regels die bewijzen dat mail echt van jouw domein komt. De website is een A-record. Verhuis je alleen de site naar DropTheHassle, wijzig dan het A-record op @ naar het adres dat op je scherm staat en laat MX, SPF en DKIM staan.
Twee acties vervangen wél de mailroutering. De nameservers omzetten naar ns1.dropthehassle.app en ns2.dropthehassle.app (dat is de verhuizing van het hele domein, inclusief mail). En mail hier aanzetten: dan schrijft DropTheHassle MX en SPF naar onze mailservers, in de DNS die het zelf beheert. Dat klopt voor een domein dat hier geregistreerd of naartoe verhuisd is. Wijs je alleen een A-record aan en blijft de DNS bij je registrar, dan publiceert die schrijfactie de MX daar niet. Laat in dat geval de bestaande MX staan tot je bewust overstapt.
Aanzetten
De site staat online en het domein hoort bij het account. Mail op een losse gratis .dropthehassle.app-link zit niet in deze stap. Eerst een actief domein.
Kies het lokale deel, bijvoorbeeld info. Je bevestigt de afschrijving zelf. Je AI kan dit niet.
Het eerste adres is €5 / $5 per maand. Elk volgend adres op hetzelfde domein is €3 / $3 per maand. Opzeggen kan. Een periode die al betaald is blijft werken tot het einde.
Open DropTheHassle
Vragen
Zit btw in de €19?
Ja. Een .com is €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde.
Kan ik een .nl nemen?
Ja. Je ziet de prijs van een .nl voordat je betaalt.
Kan ik met iDEAL betalen?
Je betaalt via Stripe. Welke betaalmethodes je ziet, zoals iDEAL, zie je bij het afrekenen.

---
# https://dropthehassle.com/nl/claude-code-website-online-zetten

Je website is gemaakt met Claude Code. Zo zet je hem online
Claude Code bouwt je site, maar zet hem niet online: sleep de map met je index.html (of de dist-map na npm run build) op dropthehassle.com en je site staat binnen een paar minuten op een gratis https-link, zonder creditcard en zonder FTP. Geen zin om zelf te slepen? Koppel DropTheHassle één keer aan Claude Code en zeg zet deze site online met DropTheHassle.
Je AI mag publiceren, maar kan nooit je geld uitgeven.
Gemaakt met ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf of met de hand? Dezelfde stappen.
Laatst bijgewerkt: 3 oktober 2026. Het koppelcommando komt uit de MCP-uitleg van Claude Code zelf.
Wat heeft Claude Code voor je gemaakt?
Claude Code werkt in een map op je eigen computer. Open die map even, dan zie je meteen welke kant je op moet:
Je ziet een index.html, met wat css, javascript en plaatjes eromheen. Dan ben je eigenlijk al klaar: precies die map gaat online.
Je ziet een package.json en mappen als src. Dan is het een project met React, Vite of Astro, en dat is nog het bouwpakket, niet de site. Zeg tegen Claude Code bouw dit project, of typ zelf npm run build. Er verschijnt een map dist (soms heet hij build of out), en die upload je.
Je start het met iets als node server.js of python app.py. Dan draait er een stukje server mee. De pagina's die mensen zien kunnen gewoon hier. Heb je ook een serverdeel? Laat dat op AWS, Google Cloud, DigitalOcean of je eigen server staan, en je AI koppelt het in één stap aan je site.
Twijfel je? Vraag het gewoon: Welke map moet ik uploaden om deze site online te zetten? Claude Code heeft de boel zelf gebouwd, dus het weet het antwoord.
In 4 stappen online
Pak de goede map. De map met index.html erin, of dist als je net gebouwd hebt.
Ga naar dropthehassle.com en klik op Upload (free). Een account maken hoeft niet eerst.
Klik op Drop your folder en sleep de map erin. Een .zip mag ook. Meteen daarna vraagt de pagina om je e-mailadres. Zolang je niet geclaimd hebt, mag het 25 MB en 1.000 bestanden zijn.
Claim hem. Je site staat nu al op een adres als https://jouwnaam.dropthehassle.app, met het slotje erbij. Klik op hetzelfde scherm op Claim this site, anders verdwijnt hij na minstens 7 dagen. Geclaimd mag je tot 100 MB en 5.000 bestanden uploaden, en de gratis link blijft gewoon staan.
Vóór het claimen staat er onderaan nog een klein balkje Made with DropTheHassle, dat bezoekers kunnen wegklikken. Zoekmachines vragen we dan ook om de site nog even over te slaan.
Of laat Claude Code het doen
Zit je toch al in Claude Code, dan is dit eerlijk gezegd de makkelijkste route. Je koppelt DropTheHassle één keer, vanuit een terminal in je projectmap:
claude mcp add --transport http dropthehassle https://dropthehassle.com/mcp
Start Claude Code en zeg: Zet ./dist online met DropTheHassle. Het vraagt om je e-mailadres en komt terug met de live link en een claimlink. Open die claimlink, dan is de site van jou. Een account, een token of GitHub heb je voor die eerste keer niet nodig.
Ga je later nog aan de site sleutelen? Claim hem eerst. Kies daarna op dropthehassle.com in het menu rechtsboven Connect your AI en koppel Claude Code aan je account. Vanaf dan is werk mijn site bij genoeg, en komt de nieuwe versie op hetzelfde adres.
Een domeinnaam opzoeken en je een betaallink sturen kan Claude Code ook. Afrekenen niet: dat blijft jouw klik.
Werk je met Claude Code in de browser in plaats van op je eigen computer? Daar is een aparte Engelse gids voor: Claude Code on the web.
Eigen domeinnaam erbij
Met de gratis link kun je je site prima laten zien. Wil je een echte naam, zoals jouwnaam.nl, dan heb je twee smaken:
Wat Prijs
Gratis link jouwnaam.dropthehassle.app met https €0, geen kaart. Claim hem en hij blijft.
.com, .org of .net hier kopen €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde
.nl of .eu hier kopen €12 / $12 per jaar, incl. btw in de EU, elk jaar hetzelfde
Een domein dat je al hebt €0 bij ons. De verlenging loopt bij je eigen registrar.
E-mail op je eigen naam, als je wilt €5 / $5 per maand voor het eerste postvak, €3 / $3 per maand voor elk extra adres
Koop je de naam hier, dan hoef je niets met DNS: hij hangt meteen aan je site. Je zoekt hem op in je dashboard en rekent zelf af via Stripe. Welke betaalmethodes er zijn, zoals iDEAL, zie je bij het afrekenen.
Staat je domein al ergens anders? Dan zet je daar één A-record, met het adres dat op je scherm staat. Zo'n record is één regel in de domeininstellingen die zegt op welke server je site woont. Klik daarna op Check now, en https komt er vanzelf bij. Je nameservers blijven staan, dus je mail merkt er niets van.
Waarom je geen FTP, public_html of hostingpakket nodig hebt
Zoek je op hoe je een website online zet, dan kom je vaak oude uitleg tegen: hostingpakket kopen, FileZilla installeren, inloggen met FTP en je bestanden in public_html zetten. Dat kan nog steeds, maar voor een map uit Claude Code is het een flinke omweg.
Hier sleep je de map in je browser, of Claude Code stuurt hem zelf op. Voor de gratis link vul je geen kaart in, en het certificaat voor https hoef je niet zelf te regelen, ook niet als je later een eigen domein koppelt. Domein, site en mail zitten bij elkaar, op één rekening.
En heeft Claude Code een app met eigen routes gebouwd, zoals een React-app met /over en /contact? Die openen ook na verversen. Is een adres geen echt bestand, dan krijgt de bezoeker je index.html, en je app doet de rest.
Veelgemaakte fouten: werkt het lokaal maar niet online?
Op je laptop ziet alles er goed uit, online krijg je een wit scherm of ontbreken de plaatjes. Bijna altijd is het een van deze drie:
De verkeerde map. Je uploadde het hele project in plaats van dist. Draai npm run build en upload dist. Een map zonder pagina om mee te beginnen (geen index.html en ook geen los HTML-bestand) wordt geweigerd.
Paden naar je eigen computer. Iets als C:\Users\... of /Users/jouwnaam/... in de code werkt alleen op jouw laptop. Vraag Claude Code om er relatieve paden van te maken.
Hoofdletters. Je laptop vindt Logo.png en logo.png hetzelfde, een webserver niet. Zorg dat de naam in de code precies klopt.
Ligt het daar niet aan, kijk dan nog of je .env-bestand erin zat toen je bouwde, en of je app soms een server nodig heeft. Alle vijf de oorzaken, plus een prompt die je zo in Claude Code plakt, vind je in de Engelse gids My site works on my computer but not online.
Veelgestelde vragen
Kan ik met Claude Code een website bouwen?
Ja, en best een goede ook. Claude Code schrijft alles, van één pagina tot een complete React-app. Alleen online zetten doet het niet uit zichzelf, daar heb je een host voor. Met DropTheHassle gekoppeld zet Claude Code de site op een gratis https-link en krijg je een claimlink.
Hoe kan ik gratis een website online zetten?
Klik op dropthehassle.com op Upload (free) en sleep de map erin. Je krijgt een gratis adres op dropthehassle.app met https, zonder dat je een kaart invult. Vergeet niet te claimen: een site die niemand claimt, wordt na minstens 7 dagen verwijderd.
Hoeveel kost het om een website te hosten?
Hier niets, zolang je de gratis link gebruikt. Pas voor een eigen naam betaal je: €19 / $19 per jaar voor een .com en €12 / $12 per jaar voor een .nl, incl. btw in de EU, elk jaar hetzelfde. Mail op je eigen naam is een losse keuze, vanaf €5 / $5 per maand.
Heb ik GitHub, een account of een terminal nodig?
GitHub en een account niet, in elk geval niet de eerste keer. Een terminal alleen als je project gebouwd moet worden, en ook dat kun je aan Claude Code overlaten.
Hoe werk ik mijn site later bij?
Na het claimen heb je een dashboard. Klik daar op Update website en sleep de nieuwe versie erin; de oude blijft online tot de nieuwe klaarstaat. Of koppel Claude Code via Connect your AI en vraag het om je site bij te werken.
Kan Claude Code het domein voor me kopen?
Nee. Het mag kijken of een naam vrij is en je een betaallink geven, maar op betalen klik je zelf.
Meer lezen
De uitgebreide Engelse gids voor Claude Code, met eigen domein
Kwam je site uit ChatGPT? Dan is dit je stappenplan
Je eigen domein aan een Lovable- of Bolt-site hangen
Wat mail op je eigen domein echt kost
Staat je dist klaar? Dan ben je een paar minuten verwijderd van een link die je kunt rondsturen.
Zet je site gratis online

---
# https://dropthehassle.com/nl/chatgpt-website-online-zetten

ChatGPT heeft je website gemaakt. Zo zet je hem online (2026)
Sla wat ChatGPT je gaf op als index.html, zet het in een map en sleep die map op dropthehassle.com: binnen een paar minuten staat je site online op een gratis https-link, en een eigen .com kost €19 / $19 per jaar zonder DNS-gedoe. ChatGPT Plus heb je er niet voor nodig, FTP en een hostingpakket ook niet.
Betaal je al voor Plus of hoger? Dan kan ChatGPT Sites je site ook zelf hosten, op een adres op chatgpt.site, en een domein koppelen dat je al hebt. Verderop lees je wanneer dat handiger is.
Je AI mag publiceren, maar kan nooit je geld uitgeven.
Gemaakt met ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf of met de hand? Dezelfde stappen.
Laatst bijgewerkt: 3 oktober 2026. Wat er over ChatGPT Sites staat, komt uit de hulppagina's van OpenAI (help.openai.com/en/articles/20001339) en de release notes van 9 juli 2026.
Wat heeft ChatGPT je gegeven?
ChatGPT geeft je code, geen website die al ergens draait. Wat je ermee doet, hangt af van wat er in je chat staat:
Eén blok HTML. Klik boven het blok op Copy of Download en bewaar het als index.html in een lege map. Dat was het.
Losse blokken voor HTML, CSS en JavaScript. Sla ze op onder de namen die in de code staan, meestal style.css en script.js, allemaal in dezelfde map. Makkelijker: vraag Kun je hier één index.html van maken, met alle CSS en JavaScript erin?
Een zip. Uitpakken en de map met index.html zoeken. Zit er ook een package.json bij, dan moet het eerst gebouwd worden met npm run build, en upload je daarna de map dist.
Een app met inlog of database. De pagina's kunnen hier. Heb je ook een serverdeel? Laat dat op AWS, Google Cloud, DigitalOcean of je eigen server staan, en je AI koppelt het in één stap aan je site.
Let op: de preview in ChatGPT, en ook een deellink van zo'n codeblok, kun je alleen binnen ChatGPT bekijken. Dat is nog geen website.
Kladblok of TextEdit? Kies in Kladblok bij Opslaan als het type Alle bestanden, anders heet je bestand ineens index.html.txt. Op de Mac zet je TextEdit eerst op platte tekst: Opmaak, dan Maak platte tekst.
In 4 stappen online
Zet alles in één map: je index.html en wat erbij hoort, zoals css en plaatjes.
Klik op dropthehassle.com op Upload (free). Om te beginnen heb je geen account nodig.
Drop your folder: sleep de map erin, of een .zip ervan, en vul daarna je e-mailadres in. Tot je claimt, past er 25 MB en 1.000 bestanden in.
Claim this site. Je site staat dan al online op jouwnaam.dropthehassle.app, met https. Met de claimknop op datzelfde scherm houd je hem; doe je niets, dan wordt hij na minstens 7 dagen weggehaald. Geclaimd mag hij 100 MB en 5.000 bestanden zijn.
Een HTML-website online zetten zonder FTP
Wie zoekt op html website online zetten, krijgt vaak een stappenplan van jaren terug: hosting kopen, FileZilla installeren, verbinding maken, bestanden naar public_html. Werkt prima, alleen heb je het niet meer nodig.
Je sleept de map gewoon in je browser. De link jouwnaam.dropthehassle.app kost niets en vraagt geen kaart, en https zit er vanaf het begin op, ook op een eigen domein. Iets veranderd? Na het claimen klik je in je dashboard op Update website en sleep je de nieuwe bestanden erin. Tot die erop staan, blijft de oude versie online.
Meer dan één pagina? Laat index.html je voorpagina zijn en link de rest op bestandsnaam, bijvoorbeeld over-ons.html.
Of laat je AI het doen
Gebruik je naast ChatGPT ook Codex, Claude Code of Cursor? Dan kun je het uploaden overlaten. Koppel daar één keer https://dropthehassle.com/mcp en zeg publiceer deze map met DropTheHassle. Je krijgt een live link en een claimlink terug, en voor die eerste keer is geen account nodig. Hoe dat per tool gaat, staat in de Engelse gids over de MCP-server en in die voor Codex.
In de Claude-app voeg je https://dropthehassle.com/mcp toe als custom connector, op claude.ai of in Claude Desktop. Daarna zie je hem ook in de app op je telefoon.
En ChatGPT Sites dan?
Sinds 9 juli 2026 heeft ChatGPT zelf ook hosting: ChatGPT Sites, in publieke bèta voor Plus, Pro, Business, Enterprise en Edu. Op Free en Go zit het niet. Je site komt op een adres op chatgpt.site, en Sites kan ook een lichte app met database en inlog draaien.
Een domein kopen kan daar niet, een domein dat je al hebt koppelen wel. Sites laat je dan een paar DNS-records zien, en die zet je zelf bij het bedrijf waar je domein staat. In Enterprise kan dat bij de start nog niet. Over e-mail of een exportknop zegt de hulp van OpenAI niets.
Mijn advies: heb je al Plus, al een domein, en schrik je niet van DNS, dan is Sites prima. Zit je op het gratis plan, wil je de naam kopen zonder DNS-gedoe, wil je mail op je eigen naam, of wil je dat je site blijft staan als je ChatGPT opzegt? Dan zit je met de route hierboven beter.
Eigen domeinnaam erbij
De gratis link is handig om te delen, maar op een visitekaartje wil je je eigen naam.
Hier kopen. Een .com, .org of .net kost €19 / $19 per jaar, een .nl of .eu €12 / $12 per jaar, incl. btw in de EU, elk jaar hetzelfde. Je zoekt de naam op in je dashboard en betaalt zelf via Stripe; iDEAL zie je bij het afrekenen. Aan DNS hoef je niets te doen, de naam hangt meteen aan je site.
Al een domein? Dan kost het bij ons niets en verleng je gewoon bij je eigen registrar. Zet daar één A-record naar het adres op je scherm en klik op Check now. https komt er vanzelf bij. Je nameservers raak je niet aan, dus je mail blijft werken.
Mail op je eigen naam, als je dat wilt: €5 / $5 per maand voor het eerste postvak en €3 / $3 per maand voor elk adres dat erbij komt.
Veelgemaakte fouten
Hier lopen mensen met een site uit ChatGPT vaak op vast:
Je ziet code in plaats van je site. Dan heet het bestand stiekem index.html.txt, of het is als opgemaakte tekst bewaard. Sla het opnieuw op als platte tekst, met de naam index.html.
Geen opmaak, geen plaatjes. De HTML zoekt naar style.css of images/foto.jpg, maar die staan niet in je map. Zet ze ernaast, met exact dezelfde naam, of laat ChatGPT alles in één bestand stoppen.
Hoofdletters. Online zijn Foto.JPG en foto.jpg twee verschillende bestanden.
Het hele project gezipt. Een project dat nog gebouwd moet worden, wordt geweigerd. Eerst npm run build, dan dist uploaden.
Knoppen die ChatGPT aanroepen. Werkt een onderdeel via ChatGPT zelf, dan doet het niets meer zodra de pagina ergens anders staat.
Gaat het op je eigen computer goed en online niet? De vijf bekende oorzaken staan op een rij in de Engelse gids My site works on my computer but not online.
Veelgestelde vragen
Kan ChatGPT een website maken?
Zeker. ChatGPT schrijft de HTML, CSS en JavaScript voor een hele site. Online zetten is stap twee: met ChatGPT Sites als je Plus of hoger hebt, of op elk plan door de code als index.html op te slaan en de map hier te uploaden.
Wat kost het om mijn site zo online te zetten?
De link op dropthehassle.app is gratis, zonder kaart. Je betaalt pas voor een eigen domein: €19 / $19 per jaar voor een .com, €12 / $12 per jaar voor een .nl, incl. btw in de EU. Mail is optioneel.
Heb ik ChatGPT Plus nodig?
Nee. Code opslaan als index.html kan op elk plan, ook het gratis plan. Plus heb je alleen nodig voor ChatGPT Sites.
Blijft mijn site online als ik stop met ChatGPT?
Ja, als je hem hier hebt gezet en geclaimd. Je bestanden staan op je DropTheHassle-account en hebben niets met je ChatGPT-abonnement te maken. Claimen is wel nodig: anders wordt de site na minstens 7 dagen verwijderd.
Kan ik later nog iets veranderen?
Ja. Laat ChatGPT de aanpassing maken, sla de nieuwe bestanden op en sleep ze in je dashboard bij Update website. Je oude versie blijft online tot de nieuwe erop staat.
Kan ChatGPT het domein voor me kopen?
Nee. Een AI die aan DropTheHassle gekoppeld is, kan publiceren en je een betaallink sturen, maar afrekenen doe je altijd zelf.
Ook handig
Deze gids in het Engels, met een vergelijking van Netlify Drop en Tiiny Host
Gebouwd met Claude Code? Zo zet je die site online
Eigen domein koppelen aan je Lovable- of Bolt-site
Een website online zetten zonder hostingpakket
Een zakelijk e-mailadres op je eigen domein: de kosten
Heb je je index.html al opgeslagen? Sleep de map erin en kijk hoe hij eruitziet als echte website.
Upload je map, gratis

---
# https://dropthehassle.com/nl/vibe-coding-website-online-zetten

Hoe zet ik mijn vibe-coded website online?
Een vibe-coded website zet je online door de map met je index.html (of de dist-map na npm run build) op dropthehassle.com te slepen: binnen een paar minuten staat hij op een gratis https-link die iedereen kan openen, zonder creditcard. Komt je site uit Lovable of Bolt, dan haal je de code er eerst uit. Hieronder staat per tool hoe dat gaat.
Je AI mag publiceren, maar kan nooit je geld uitgeven.
Gemaakt met ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf of met de hand? Dezelfde stappen.
Laatst bijgewerkt: 3 oktober 2026. Wat er over Lovable en Bolt staat, komt uit hun eigen documentatie; de prijs van Bolt staat op bolt.new/pricing (gecheckt op 3 oktober 2026).
Een preview is nog geen website
Het verwarrende aan vibe coding: je ziet je site de hele tijd al. In het voorbeeldvenster van Lovable of Bolt, in de preview naast je chat met Claude of ChatGPT, of op localhost:5173 als Cursor of Claude Code hem op je laptop draait. Maar dat venster is van de tool, of van je eigen computer. Stuur je die link naar een vriend, dan ziet hij niets, of hij moet eerst inloggen bij een dienst die hij niet heeft.
Online zetten betekent: de bestanden van je site staan op een server die dag en nacht aan staat, op een adres met https dat iedereen kan openen. Je AI heeft het bouwen gedaan. Dit laatste stuk doet hij meestal niet uit zichzelf, en daar gaat deze pagina over.
Lovable en Bolt kunnen je site wel publiceren op een adres van henzelf. Voor je eigen domeinnaam vragen ze allebei een betaald plan. Bij Bolt is dat Pro, $25 per maand als je per maand betaalt. Wil je dat niet, dan zet je de gebouwde site gewoon ergens anders neer.
Welke map moet online? Per tool
Een host wil de afgebouwde site: een map met gewone bestanden die een browser zo kan openen. Waar je die vandaan haalt, hangt af van je tool. De tabel scrolt opzij op een smal scherm.
Gemaakt met Zo haal je het eruit Dit upload je
ChatGPT, Claude of Gemini, in de chat Copy of Download bij het codeblok, opslaan als index.html De map met index.html
Claude Code, Cursor, Codex of Windsurf Staat al in een map op je computer Met een package.json: eerst npm run build, dan dist. Zonder: de map met index.html
Lovable Koppel je project aan GitHub (kan op elk plan) en kies op github.com Code, dan Download ZIP dist, na npm install en npm run build
Bolt Klik op de projectnaam, dan Export, dan Download dist, na npm install en npm run build
Replit Download als zip via het menu met de drie puntjes boven de bestandenlijst De gebouwde map. Draait er een server mee, lees dan verderop
Bouwen klinkt zwaarder dan het is. Je hebt Node.js nodig (de LTS-versie van nodejs.org), je opent een terminal in de projectmap en typt npm install en daarna npm run build. Of je vraagt het aan Cursor, Claude Code of Codex. Er verschijnt een map dist, soms build of out, en die gaat online.
Lovable-app gemaakt op of na 13 mei 2026? Dan is het een TanStack Start-app, en daar geeft npm run build geen map die je zo kunt slepen. Daarvoor is een aparte Engelse gids.
Twijfel je welke map het is? Vraag het je AI: Welke map moet ik uploaden om deze site online te zetten? Hij heeft de boel zelf gebouwd, dus hij weet het.
In 4 stappen online
Pak de goede map. Die met index.html bovenin, of dist als je net hebt gebouwd. Een .zip ervan mag ook.
Ga naar dropthehassle.com en klik op Upload (free). Je hoeft niet eerst een account te maken.
Klik op Drop your folder en sleep de map erin. Meteen daarna vraagt de pagina om je e-mailadres. Tot je claimt, mag het 25 MB en 1.000 bestanden zijn.
Claim hem. Je site staat nu al op een adres als https://jouwnaam.dropthehassle.app. Klik op hetzelfde scherm op Claim this site, anders verdwijnt hij na minstens 7 dagen. Geclaimd mag je tot 100 MB en 5.000 bestanden uploaden, en de gratis link blijft staan.
Heeft je app eigen pagina's, zoals /prijzen of /contact? Die openen ook na verversen. Is een adres geen echt bestand, dan krijgt de bezoeker je index.html, en je app doet de rest.
Of laat je AI het uploaden
Werk je in Claude Code, Cursor, Codex of Windsurf? Dan kan je AI dat laatste stuk ook zelf. Koppel één keer https://dropthehassle.com/mcp en zeg zet deze site online met DropTheHassle. Je krijgt een live link en een claimlink terug, en voor die eerste keer heb je geen account, token of GitHub nodig. Hoe je dat koppelt, staat in de gids voor Claude Code, die voor Cursor en de Engelse gids over de MCP-server.
Je AI mag ook een domeinnaam voor je opzoeken en je een betaallink sturen. Afrekenen doet hij nooit: die klik blijft van jou.
Heeft je app een database of inlog?
Veel vibe-coded apps praten met Supabase of Lovable Cloud voor de database en het inloggen. Dat blijft gewoon waar het is. De pagina's staan hier en praten vanaf hier met die dienst. Let op twee dingen: zet je sleutels in een .env-bestand voordat je bouwt, en zet je nieuwe adres in de lijst met toegestane redirect-URL's van je inlogdienst. Bij Supabase is dat Authentication, dan URL Configuration.
Start je je app met iets als node server.js of python app.py, dan draait er een stuk server mee dat aan moet blijven. Een map met bestanden kan dat niet in z'n eentje. Heb je ook een serverdeel? Laat dat op AWS, Google Cloud, DigitalOcean of je eigen server staan, en je AI koppelt het in één stap aan je site.
Is het veilig om een vibe-coded site online te zetten?
Die vraag komt vaak voorbij, en terecht. De hosting zelf is meestal het probleem niet. Je site krijgt https, en bestanden en mappen die met een punt beginnen, zoals .env of .git, halen we uit je upload voordat hij online gaat. Het risico zit in wat je AI in de code heeft gezet.
Alles in de gebouwde map is openbaar. Iedereen kan de JavaScript van je site lezen, ook de sleutels die er tijdens het bouwen in zijn gezet. Een publieke sleutel, zoals de anon key van Supabase, mag daar staan. Een geheime sleutel, zoals die van OpenAI of Stripe, nooit.
Zet de beveiliging van je database aan. Bij Supabase heet dat Row Level Security. Staat die uit, dan kan iemand met die publieke sleutel meer lezen dan je lief is.
Laat je AI even meekijken. Vraag bijvoorbeeld: Staan er geheime sleutels in code die in de browser terechtkomt? En welke tabellen kan iemand lezen met alleen de publieke sleutel?
Tot je hem claimt, vragen we zoekmachines je site nog over te slaan, en staat er onderaan een klein balkje Made with DropTheHassle dat bezoekers kunnen wegklikken.
Eigen domeinnaam erbij
Met de gratis link kun je je site prima laten zien. Op een visitekaartje of in je bio wil je je eigen naam.
Wat Prijs
Gratis link jouwnaam.dropthehassle.app met https €0, geen kaart. Claim hem en hij blijft.
.com, .org of .net hier kopen €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde
.nl of .eu hier kopen €12 / $12 per jaar, incl. btw in de EU, elk jaar hetzelfde
.app hier kopen €25 / $25 per jaar, incl. btw in de EU, elk jaar hetzelfde
Een domein dat je al hebt €0 bij ons. De verlenging loopt bij je eigen registrar.
E-mail op je eigen naam, als je wilt €5 / $5 per maand voor het eerste postvak, €3 / $3 per maand voor elk extra adres
Koop je de naam hier, dan hoef je niets met DNS: hij hangt meteen aan je site. Je zoekt hem op in je dashboard en rekent zelf af via Stripe. Staat je domein al ergens anders? Zet daar één A-record naar het adres op je scherm en klik op Check now. https komt er vanzelf bij, en je nameservers blijven staan, dus je mail merkt er niets van.
Veelgemaakte fouten
Hier lopen mensen met een vibe-coded site het vaakst op vast:
De previewlink rondsturen. Een link naar localhost of naar het voorbeeldvenster van je tool werkt alleen bij jou. Stuur de link op dropthehassle.app.
Het hele project uploaden. Een project dat nog gebouwd moet worden, wordt geweigerd. Eerst npm run build, dan dist.
De sleutels vergeten. In een download uit Bolt zitten je omgevingsvariabelen niet. Zet ze in .env voordat je bouwt, anders vindt de live site je database niet.
Inloggen stuurt je terug naar de preview. Je inlogdienst kent alleen het oude adres. Zet het nieuwe in de lijst met toegestane redirect-URL's.
Hoofdletters. Je laptop vindt Logo.png en logo.png hetzelfde, een webserver niet.
Niet claimen. Na minstens 7 dagen is een niet-geclaimde site weg. Claim hem terwijl het scherm nog openstaat.
Werkt alles op je eigen computer en online niet? De vijf bekende oorzaken, plus een prompt die je zo in je AI plakt, staan in de Engelse gids My site works on my computer but not online.
Veelgestelde vragen
Hoe zet je een website online?
Je zet de bestanden van je site op een server die dag en nacht aan staat, op een adres met https. Hier sleep je daarvoor de map met index.html op dropthehassle.com, of je laat je AI het doen. Een hostingpakket, FTP of DNS heb je voor de gratis link niet nodig.
Hoe kan ik gratis een website online zetten?
Klik op dropthehassle.com op Upload (free) en sleep je map erin. Je krijgt een gratis adres op dropthehassle.app met https, zonder kaart. Claim de site daarna, anders wordt hij na minstens 7 dagen verwijderd.
Kun je vibe coding uitleggen?
Je vertelt in gewone taal wat je wilt hebben, en een AI-tool als Lovable, Bolt, Cursor of Claude Code schrijft de code. Je stuurt bij door te zeggen wat er anders moet, niet door zelf te programmeren. Wat eruit komt is gewone code, en die kan overal online.
Kan ik mijn Lovable- of Bolt-site online zetten zonder abonnement?
Ja. Haal de code eruit (bij Lovable via GitHub, bij Bolt via Export en Download), bouw hem één keer met npm run build en sleep de map dist hierheen. De link op dropthehassle.app is gratis; een eigen .com kost €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde.
Blijft mijn site online als ik stop met mijn AI-tool?
Ja, als je hem hier hebt gezet en geclaimd. De bestanden staan op je DropTheHassle-account, los van je abonnement bij Lovable, Bolt, Cursor of ChatGPT. Een database bij Lovable Cloud of Supabase houdt wel zijn eigen plan.
Hoe werk ik mijn site later bij?
Laat je AI de aanpassing maken, bouw opnieuw als je project dat nodig heeft, en sleep de nieuwe map in je dashboard bij Update website. De oude versie blijft online tot de nieuwe erop staat.
Kan mijn AI het domein voor me kopen?
Nee. Hij kan kijken of een naam vrij is en je een betaallink sturen, maar afrekenen doe je altijd zelf.
Meer lezen
Gebouwd in Cursor? Zo zet je dat project online
Gebouwd met Claude Code? Zo zet je die site online
Kwam je site uit ChatGPT? Dan is dit je stappenplan
Je eigen domein aan een Lovable- of Bolt-site hangen
Een website online zetten zonder hostingpakket
Waar host je een vibe-coded app? (Engels)
Weet je welke map het is? Dan staat je site over een paar minuten op een link die je echt kunt rondsturen.
Zet je site gratis online

---
# https://dropthehassle.com/nl/cursor-project-online-zetten

Hoe zet ik mijn Cursor-project online?
Cursor bouwt je project op je eigen computer, maar zet het niet online: laat de agent npm run build draaien, sleep de map dist (of de map met je index.html) op dropthehassle.com en je krijgt binnen een paar minuten een gratis https-link, zonder creditcard. Liever niet slepen? Zet DropTheHassle één keer in .cursor/mcp.json en zeg tegen de agent zet ./dist online met DropTheHassle.
Je AI mag publiceren, maar kan nooit je geld uitgeven.
Gemaakt met ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf of met de hand? Dezelfde stappen.
Laatst bijgewerkt: 3 oktober 2026. Waar mcp.json hoort te staan, komt uit de MCP-documentatie van Cursor.
Kwam je hier voor Projects, de functie in Cursor zelf? Daarover lees je meer op cursor.com. Deze pagina gaat over het andere project: wat Cursor voor je gebouwd heeft, op internet zetten.
Wat heeft Cursor voor je gebouwd?
Cursor werkt in een map op je laptop. Kijk in die map, dan weet je meteen wat je moet uploaden:
Je ziet een index.html, met wat css, javascript en plaatjes. Dan is die map je site. Klaar om te uploaden.
Je ziet een package.json en een map src. Dan is het een React-, Vite- of Astro-project, en wat je ziet is nog het bouwpakket. Na npm run build krijg je de echte site: dist bij Vite, build bij Create React App, out bij een Next.js-export.
Je start het met node server.js of python app.py. Dan draait er een stukje server mee. De pagina's die mensen zien kunnen hier staan. Heb je ook een serverdeel? Laat dat op AWS, Google Cloud, DigitalOcean of je eigen server staan, en je AI koppelt het in één stap aan je site.
Twijfel je? Typ in de agent-chat: Welke map moet ik uploaden om dit project online te zetten? Cursor heeft het zelf gemaakt, dus het weet het antwoord.
Waarom localhost:5173 niet werkt bij een ander
Draait Cursor npm run dev, dan zie je je site op een adres als http://localhost:5173 of localhost:3000. Localhost betekent: deze computer. Je laptop laat de site aan zichzelf zien. Stuur je die link naar iemand anders, dan zoekt zijn browser op zijn eigen computer, en daar staat niets. Klap je je laptop dicht, dan is hij ook voor jou weg.
Er zijn tools die je localhost even naar buiten doorgeven, maar dan moet je laptop aan blijven staan. Wil je een link die gewoon blijft werken, dan moet de gebouwde map op een server staan die altijd aan is.
In 4 stappen online, met de hand
Bouw het. Vraag de agent draai npm run build, of typ het zelf in de terminal van Cursor. Pak daarna de map dist (of build of out). Een project met alleen HTML sla je over: dat is al klaar.
Ga naar dropthehassle.com en klik op Upload (free). Een account maken hoeft niet eerst.
Klik op Drop your folder en sleep de map erin. Een .zip mag ook. Daarna vraagt de pagina om je e-mailadres. Zolang je niet geclaimd hebt, mag het 25 MB en 1.000 bestanden zijn.
Claim hem. Je site staat nu op een adres als https://jouwnaam.dropthehassle.app, met het slotje erbij. Klik op hetzelfde scherm op Claim this site, anders verdwijnt hij na minstens 7 dagen. Geclaimd mag je tot 100 MB en 5.000 bestanden uploaden.
Sleep je per ongeluk de hele projectmap erin, met src en package.json? Een project dat nog gebouwd moet worden, wordt geweigerd. Dan weet je meteen dat je dist moet hebben, in plaats van dat je een week later een wit scherm ontdekt.
Of laat de agent in Cursor het doen
Zit je toch al in Cursor, dan is dit de kortste weg. Maak in je project het bestand .cursor/mcp.json aan, of ~/.cursor/mcp.json als je het in elk project wilt hebben, met dit erin:
{
"mcpServers": {
"dropthehassle": {
"url": "https://dropthehassle.com/mcp"
}
}
}
Typ daarna in de agent-chat: Zet ./dist online met DropTheHassle. De agent vraagt om je e-mailadres en komt terug met je live link en een claimlink. Open die claimlink om de site te houden. Voor deze eerste keer heb je geen account, geen token en geen GitHub nodig.
Ga je later nog aan de site sleutelen? Claim hem eerst. Kies daarna in je dashboard Connect your AI en klik op Add to Cursor. Vanaf dan is werk mijn site bij genoeg, en komt de nieuwe versie op hetzelfde adres.
Een domeinnaam opzoeken en je een betaallink sturen kan de agent ook. Afrekenen niet: dat blijft jouw klik. Alles wat de koppeling kan, staat in de Engelse gids over de MCP-server.
Eigen domeinnaam erbij
De gratis link is prima om te testen en rond te sturen. Wil je een echte naam, zoals jouwnaam.nl, dan zijn er twee routes:
Wat Prijs
Gratis link jouwnaam.dropthehassle.app met https €0, geen kaart. Claim hem en hij blijft.
.com, .org of .net hier kopen €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde
.nl of .eu hier kopen €12 / $12 per jaar, incl. btw in de EU, elk jaar hetzelfde
Een domein dat je al hebt €0 bij ons. De verlenging loopt bij je eigen registrar.
E-mail op je eigen naam, als je wilt €5 / $5 per maand voor het eerste postvak, €3 / $3 per maand voor elk extra adres
Koop je de naam hier, dan hoef je niets met DNS: hij hangt meteen aan je site. Je zoekt hem op in je dashboard en rekent zelf af via Stripe. Welke betaalmethodes er zijn, zoals iDEAL, zie je bij het afrekenen.
Staat je domein al ergens anders? Zet daar één A-record naar het adres op je scherm. Zo'n record is één regel in de domeininstellingen die zegt op welke server je site staat. Klik daarna op Check now, en https komt er vanzelf bij.
Veelgemaakte fouten
Werkt het in Cursor en online niet? Meestal is het een van deze:
Een localhost-link delen. localhost:5173 opent alleen op jouw laptop. Stuur de link op dropthehassle.app.
De projectmap in plaats van dist. Wat Cursor bewerkt, is de bron. Een browser kan die niet zo draaien. Eerst npm run build, dan dist.
De .env te laat. Sleutels uit .env worden bij het bouwen in je site gezet. Zet ze er dus vóór npm run build in. Alleen publieke sleutels horen daar: bezoekers kunnen alles in de gebouwde map lezen.
Paden naar je eigen computer. Iets als C:\Users\... of /Users/jouwnaam/... in de code werkt alleen bij jou. Vraag de agent om er relatieve paden van te maken.
Hoofdletters. Je laptop vindt Logo.png en logo.png hetzelfde, een webserver niet.
Alle vijf de oorzaken, plus een prompt die je zo in Cursor plakt, staan in de Engelse gids My site works on my computer but not online.
Veelgestelde vragen
Kan ik met Cursor een website bouwen?
Ja. Cursor schrijft alles, van één pagina tot een complete React- of Vite-app, en draait hem op je laptop zodat je meekijkt. Online zetten doet het niet uit zichzelf. Daar heb je een host voor, en met DropTheHassle gekoppeld doet de agent ook dat.
Waarom werkt mijn Cursor-project alleen op localhost?
Omdat localhost je eigen computer is. Je laptop laat de site aan zichzelf zien, dus niemand anders kan dat adres openen. Zet de gebouwde map online en je krijgt een link die iedereen kan openen, ook als je laptop dicht is.
Heb ik GitHub of een account nodig?
Nee, niet voor de eerste keer. Slepen of de agent laten publiceren kan zonder GitHub, account of token. Vul je e-mailadres in als erom gevraagd wordt en claim de site om hem te houden.
Werkt het met React, Vite of Next.js?
Ja, zolang het bouwen een map met index.html oplevert. Bij Vite is dat dist, bij een Next.js-export out. Apps met eigen routes werken: is een adres geen echt bestand, dan krijgt de bezoeker je index.html.
Hoe werk ik mijn site later bij?
Claim de site en kies in je dashboard Connect your AI, dan Add to Cursor. Daarna is werk mijn site bij genoeg en komt de nieuwe versie op hetzelfde adres. Met de hand kan ook: sleep de nieuwe map bij Update website.
Kan Cursor het domein voor me kopen?
Nee. De agent kan kijken of een naam vrij is en je een betaallink geven, maar betalen doe je altijd zelf. Een .com kost €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde.
Meer lezen
De uitgebreide Engelse gids voor Cursor, met eigen domein
Gemaakt met Lovable, Bolt of een andere AI-tool? Zo zet je hem online
Gebouwd met Claude Code? Zo zet je die site online
Wat mail op je eigen domein echt kost
Staat je dist klaar? Dan ben je een paar minuten verwijderd van een link die je kunt rondsturen.
Zet je project gratis online

---
# https://dropthehassle.com/nl/website-online-zetten-zonder-hosting

Kan ik een website online zetten zonder hosting?
Ja: voor een website die je met AI of met de hand hebt gemaakt, heb je geen hostingpakket, FTP of eigen server nodig. Sleep de map met je index.html op dropthehassle.com en binnen een paar minuten staat je site op een gratis https-link die iedereen kan openen, zonder creditcard. Een eigen domeinnaam kun je er later bij nemen, zonder dat je iets met DNS hoeft.
Je AI mag publiceren, maar kan nooit je geld uitgeven.
Gemaakt met ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf of met de hand? Dezelfde stappen.
Laatst bijgewerkt: 3 oktober 2026. Wat er over Netlify Drop staat, komt uit de documentatie van Netlify (gecheckt op 3 oktober 2026).
Wat "zonder hosting" eigenlijk betekent
Eerlijk is eerlijk: ergens moeten je bestanden staan, op een computer die altijd aan is. Dat heet hosting, en daar ontkom je niet aan. Waar je wel omheen kunt, is alles wat er vroeger bij hoorde: een pakket uitkiezen, een contract voor een jaar, inloggen met FileZilla, bestanden in de map public_html zetten en daarna nog de DNS van je domein goed krijgen.
Wie op website online zetten zonder hosting zoekt, bedoelt meestal precies dat stuk. Je hebt een site, hij werkt op je eigen computer, en je wilt een link die een ander kan openen. Zonder eerst een hostingbedrijf te kiezen.
Wat je overslaat
Zo ziet het verschil eruit voor een site met een index.html. De tabel scrolt opzij op een smal scherm.
Stap Met een hostingpakket Hier
Beginnen Pakket kiezen en afrekenen Niets kiezen. De link op dropthehassle.app is gratis
Bestanden online zetten FTP of een bestandsbeheerder, naar de goede map De map in je browser slepen
https Bij veel pakketten een instelling Zit er vanaf het begin op, ook op een eigen domein
Eigen domein Nameservers of records aanpassen bij je registrar Hier gekocht: hangt meteen aan je site. Elders: één A-record
Iets veranderen Opnieuw inloggen en bestanden overschrijven Update website in je dashboard, de oude versie blijft online tot de nieuwe erop staat
In 4 stappen online
Pak de map van je site. Die met index.html bovenin. Heeft je project een package.json, laat je AI dan eerst npm run build draaien en neem de map dist. Een .zip mag ook.
Ga naar dropthehassle.com en klik op Upload (free). Een account maken hoeft niet eerst.
Klik op Drop your folder en sleep de map erin. Daarna vraagt de pagina om je e-mailadres. Zolang de site nog niet geclaimd is, mag een upload tot 25 MB en 1.000 bestanden groot zijn.
Claim hem. Je site staat nu op een adres als https://jouwnaam.dropthehassle.app. Klik op hetzelfde scherm op Claim this site, anders verdwijnt hij na minstens 7 dagen. Geclaimd mag je tot 100 MB en 5.000 bestanden uploaden.
Meer dan één pagina? Laat index.html je voorpagina zijn en link de rest op bestandsnaam, zoals over-ons.html. Bouwde je in Lovable of Bolt? Exporteer de code dan eerst uit die tool. Hoe dat per tool gaat, staat op je vibe-coded website online zetten.
Alleen een domeinnaam, zonder hosting?
Een deel van de zoekresultaten gaat over het omgekeerde: een domeinnaam kopen zonder hostingpakket. Dat kan prima, maar een domein is alleen een adres. Wie het intikt, ziet niets zolang je bestanden nergens staan.
Hier komen die twee samen. Je zet eerst je site online op de gratis link, en neemt er een naam bij wanneer je wilt:
Wat Prijs
Gratis link jouwnaam.dropthehassle.app met https €0, geen kaart. Claim hem en hij blijft.
.nl of .eu hier kopen €12 / $12 per jaar, incl. btw in de EU, elk jaar hetzelfde
.com, .org of .net hier kopen €19 / $19 per jaar, incl. btw in de EU, elk jaar hetzelfde
.app hier kopen €25 / $25 per jaar, incl. btw in de EU, elk jaar hetzelfde
Een domein dat je al hebt €0 bij ons. Verlengen doe je gewoon waar de naam nu staat.
E-mail op je eigen naam, als je wilt €5 / $5 per maand voor het eerste postvak, €3 / $3 per maand voor elk extra adres
Neem je de naam bij ons, dan koppelen wij hem aan je site en hoef jij geen DNS-instelling aan te raken. Zoeken doe je in je dashboard, betalen zelf via Stripe. Heb je al een domein bij een andere partij? Zet daar één A-record naar het adres op je scherm en klik op Check now. Het slotje (https) regelen wij. Je nameservers verander je niet, dus mail die al op dat domein loopt, blijft gewoon werken.
Wat niet zonder server kan
Een map met bestanden is genoeg voor de meeste sites die een AI bouwt: een portfolio, een landingspagina, een menukaart, een spelletje, een React- of Vite-app na npm run build. Sommige dingen draaien op een programma dat de hele tijd aan moet staan. Denk aan WordPress, dat PHP en een database gebruikt, of een app die je start met node server.js.
Heb je ook een serverdeel? Laat dat op AWS, Google Cloud, DigitalOcean of je eigen server staan, en je AI koppelt het in één stap aan je site.
Een database die je vanuit de browser gebruikt, zoals Supabase, telt niet als server die je zelf moet hosten. Die draait al bij Supabase. Zet de sleutels in .env voordat je bouwt.
Andere manieren zonder hostingpakket
DropTheHassle is niet de enige plek waar je een map kwijt kunt. Een paar die je vaak tegenkomt:
Netlify Drop. Ook slepen, ook zonder GitHub. Volgens Netlify krijgt een project dat je zonder in te loggen dropt een tijdelijk wachtwoord, tot je het claimt met een account.
GitHub Pages. Gratis voor een portfolio of projectpagina, als je code toch al op GitHub staat. Je hebt dan wel een GitHub-account en een repository nodig.
Cloudflare Pages. Een map uploaden kan, na inloggen in het dashboard. Voor een domein zonder www wil Cloudflare je nameservers.
Je eigen computer. Kan, maar dan moet hij dag en nacht aan blijven en moet je router open voor bezoekers van buiten.
Wil je ze naast elkaar zien, met de prijs van een domein in het tweede jaar erbij? Lees de Engelse vergelijking van Netlify, Vercel en Cloudflare Pages.
Of laat je AI het doen
Bouw je met Claude Code, Cursor, Codex of Windsurf, dan kan je AI de laatste stap zelf zetten. Voeg één keer https://dropthehassle.com/mcp toe als connector en vraag: zet deze site online met DropTheHassle. Je AI stuurt de map en jij krijgt een live link en een claimlink terug. Voor die eerste keer heb je geen account, token of GitHub nodig. Hoe je dat koppelt, staat in de gids voor Claude Code en die voor Cursor.
Veelgemaakte fouten
Een link naar je eigen computer delen. localhost of file:/// opent alleen bij jou. Stuur de link op dropthehassle.app.
Geen duidelijke voorpagina. Meerdere pagina's en geen index.html of home.html? Hernoem je voorpagina naar index.html, of vraag je AI dat te doen.
Het hele project in plaats van de gebouwde map. Een project dat nog een build nodig heeft, komt niet door de upload. Eerst npm run build, dan dist.
Paden naar je eigen computer. Iets als C:\Users\... in de code werkt alleen bij jou. Vraag je AI om er relatieve paden van te maken.
Eerst een domein kopen en dan pas kijken. Zet je site eerst op de gratis link. Werkt alles, neem er dan een naam bij.
Doet je site het thuis wel en online niet? De vijf bekende oorzaken staan in de Engelse gids My site works on my computer but not online.
Veelgestelde vragen
Hoe kan ik een gratis website online zetten?
Upload de map van je site op dropthehassle.com en je krijgt een adres op dropthehassle.app met https, zonder kaart en zonder abonnement. Geld kost het pas als je hier een domeinnaam koopt of e-mail wilt. Claim de site wel: een site zonder eigenaar halen we op z'n vroegst na 7 dagen weg.
Hoe zet ik mijn website online zonder hosting?
Je hebt geen pakket en geen FTP nodig. Heeft je project een package.json, bouw het dan eerst met npm run build. Ga daarna naar dropthehassle.com, klik op Upload (free) en sleep de map met index.html, of de map dist, erin. Na een paar minuten staat je site op een gratis adres op dropthehassle.app, met https.
Kan ik een domeinnaam registreren zonder hosting?
Ja, maar dan heb je alleen een adres. Bezoekers zien pas iets als je bestanden ook ergens staan. Koop je de naam hier, dan hangt hij meteen aan je site: een .nl kost €12 / $12 per jaar, incl. btw in de EU, elk jaar hetzelfde.
Hoe zet ik mijn website online?
Online staan betekent dat je site op een computer staat die altijd aan is, en dat iedereen hem kan openen via een adres met https. Dat deel regelen wij. Jij sleept de map met index.html in je browser, of je vraagt je AI het te doen. Voor de gratis link heb je geen FTP en geen DNS nodig.
Kan ik mijn website op mijn eigen computer hosten?
Het kan, maar dan moet je computer dag en nacht aan blijven en moet je je router openzetten voor bezoekers van buiten. Een link naar localhost werkt alleen bij jou. Voor de meeste mensen is een plek die altijd aan staat minder gedoe.
Kan ik WordPress zonder hosting online zetten?
Nee. WordPress heeft een server met PHP en een database nodig, en die moet ergens draaien. Laat die server op AWS, Google Cloud, DigitalOcean of je eigen server staan, en je AI koppelt hem in één stap aan je site.
Kan mijn AI het voor me doen?
Ja. Voeg in Claude Code, Cursor, Codex of Windsurf één keer https://dropthehassle.com/mcp toe en vraag je AI: zet deze site online met DropTheHassle. Je krijgt een live link terug, plus een link om de site te claimen. Afrekenen doet je AI nooit: die klik is altijd van jou.
Meer lezen
Je vibe-coded website online zetten, per tool
Kwam je site uit ChatGPT? Dan is dit je stappenplan
Je eigen domein aan een Lovable- of Bolt-site hangen
Wat mail op je eigen domein echt kost
Online zonder GitHub (Engels)
Je site later bijwerken (Engels)
Staat je map klaar? Dan heb je over een paar minuten een link die je kunt rondsturen, zonder dat je eerst een pakket hoeft uit te zoeken.
Zet je site gratis online

---
# https://dropthehassle.com/guides/claude-code-website-online

Put your Claude Code website online, then on your own domain
If Claude Code built your site (a folder with an index.html, or a dist folder after npm run build), you can put it online for free in minutes and add your own domain later. If it needs a database, logins or file uploads, the pages still go here and can call a backend such as Supabase. 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.
Short answer: How do I get my Claude Code site online?
You already built it. Now it's on your name.
Your AI can publish. It can never spend your money.
The one command is npx -y dropthehassle@latest deploy, in the folder with your built site.
Built it with ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf or by hand? Same steps.
Last updated: 27 September 2026. The connector command matches Claude Code's MCP docs.
What did Claude Code build?
New to Claude Code? Start with this beginner guide.
A website. A folder with index.html, or a dist folder after npm run build. This guide is for that.
It needs a backend. A database, logins, or file uploads need a backend. The pages can call one such as Supabase directly, or you host a server on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card: it then runs behind your own domain. We don't run the server ourselves.
An internal tool. Something only your team should open needs hosting with access control. DropTheHassle does not provide that.
A website from a Claude chat is a different page: put a Claude artifact online.
Using Claude Code in the browser, on claude.ai/code? That cloud session is a different page: deploy from Claude Code on the web.
Works on your laptop but blank or broken once it's online? That's usually a path or build-folder issue: why a site works locally but not online.
Does it look like every other AI-built site? Fix that before you publish: 12 before and after fixes, and the design skills worth installing in Claude Code.
Put it online in 2 minutes
If the project needs a build, run npm run build and use the dist folder. If the site is already HTML, use the folder that contains index.html. Put keys in a .env file before you build. DropTheHassle does not add them later.
Open dropthehassle.com, press Upload (free), then Drop your folder. You do not sign in first. You get https://yourname.dropthehassle.app on HTTPS. No card. Claim it with your email afterwards. An unclaimed site is kept for at least 7 days. The domain can wait.
You do not sign in first, so the upload is a zip of at most 25 MB and 1,000 files until you claim the site. After you claim it, uploads can be 100 MB and 5,000 files. It needs a page to open first (an index.html, or a single HTML page). A folder that still needs a build is refused. So is a site that is itself a server (PHP, Node or Python): host that part on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card.
Keys left out of .env before the build are not in the site. Add them, build again, and drop dist again.
Single-page apps work. When an address is not a real file, we serve your index.html with a 200, so a Vite or React app opens on any of its own routes, also after a refresh.
Video and large images from tools such as Higgsfield or Seedance can push the zip over 25 MB before you claim it, or over 100 MB after. Shrink them, or leave them out of this upload.
The Vercel CLI, the Netlify CLI, and GitHub Pages will also publish a built folder. A domain you already own still needs DNS records there. They do not include a mailbox. GitHub Pages says it is not meant as a shop. Vercel's hobby plan is published as personal, non-commercial use.
Let Claude Code deploy it for you
Claude Code can publish the same folder. It can deploy a new free link, update a site you already have, and check the domains already on your account (which names point where, and whether a name is free and what it costs). It cannot buy a domain, turn on email, or edit DNS at the company where a name is registered. Renaming the free link happens only after you say yes.
A first deploy needs no token. The remote connector at https://dropthehassle.com/mcp and the stdio server (npx -y dropthehassle-mcp@latest) both publish an anonymous site and return a claim link. Get your token in the dashboard, then Connect your AI, when the site should land on your account. Do not paste a placeholder. Leave DTH_TOKEN unset until you have the real token.
Add to Cursor
claude mcp add dropthehassle -- npx -y dropthehassle-mcp@latest
{
"mcpServers": {
"dropthehassle": {
"command": "npx",
"args": ["-y", "dropthehassle-mcp@latest"]
}
}
}
Paste this into CLAUDE.md or a Cursor rule.
# DropTheHassle
Never buy anything without asking me. Never buy a domain, email or subscription for me without asking first. When something costs money, give me the payment link and let me pay.
The token cannot pay.
Then ask Claude Code to put ./dist online or update my site. What that connector can and cannot do is on the MCP guide.
Add your own domain
A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year. No DNS edit. A domain you already own needs one A record: one line in your domain's settings that says which server your site lives on. You set it once, at the company where you bought the domain, to the address shown on your screen. Press Check now. HTTPS follows. You do not upload a certificate. DNS and other hosts are also in the general guide.
Publish your site for free
Building it for a client?
Publish it here, get paid your own way, then give them the domain. The connector cannot give a name away. DropTheHassle does not collect your fee.
When it has a backend too
If the project needs a server to store data, sign people in, or accept uploads, host that part on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card; the pages stay here. A database such as Supabase that the pages call directly needs nothing extra. A folder that still needs Node, PHP, or Python to answer requests can't be uploaded as it is.
If Claude Code already built the folder, and the data lives in a service the browser calls, that folder can still go on the free link. The database stays on that service.
Questions
Do I need a domain?
No, not to see it working. The free link is enough to test it and to send to someone. Buy a domain when you share it more widely or sell it. A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year. Read that renewal price before you buy a name anywhere else.
Can Claude Code deploy and host a website?
Claude Code can deploy one, but it does not host it: it needs a host to deploy to. Add the connector (claude mcp add dropthehassle -- npx -y dropthehassle-mcp@latest) and ask it to put ./dist online. A first deploy needs no account and returns a claim link.
What if it breaks?
Your site is a folder of files, so there are few moving parts. Keep the folder or the repo. Fix it in Claude Code and publish the folder again, by dropping it or by asking the connector to update the site.
Can I charge for access?
Not with DropTheHassle alone. You need a course platform or a payment platform. This host serves the files. It does not sign visitors in or take their payment.
Can Claude Code buy the domain?
No. It can deploy, update, and check the domains already on your account. Buying the domain, and turning email on, is your click.

---
# https://dropthehassle.com/guides/claude-code-on-the-web-deploy-custom-domain

Claude Code on the web: put your site live on your own domain
Short answer: Claude Code on the web blocks dropthehassle.com on its default "Trusted" network, so either add https://dropthehassle.com/mcp as a custom connector in claude.ai (no token) and ask Claude to publish with it, or set the environment's network access to Custom, add dropthehassle.com, and have Claude run npx -y dropthehassle@latest deploy. Both return a live yourname.dropthehassle.app link with HTTPS and a claim link, with no account. Claim the site to keep it and add your own .com.
Claude Code on the web runs your task in a cloud machine that Anthropic manages, on a copy of your GitHub repo. It can build the whole site there. The deploy step is where people get stuck, because that machine only talks to an approved list of websites, and dropthehassle.com is not on the default list. Here are the two ways around it, with no account needed to get a live link.
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: 4 October 2026. Network levels, the Trusted domain list, and connector traffic are from Anthropic's cloud environment docs. Plans and the cloud VM are from Claude Code on the web.
This page is only the cloud session (claude.ai/code). Running Claude Code on your own machine is a different guide. Cloud sessions are on Pro, Max, and Team plans, and for Enterprise users with a premium seat or a Chat and Claude Code seat.
Why the deploy fails in a cloud session
Every Claude Code on the web environment has a network access level: None, Trusted, Full, or Custom. The default is Trusted, which allows a fixed list of package registries and code hosts. registry.npmjs.org is on that list, so npx -y dropthehassle@latest deploy downloads fine. dropthehassle.com is not on it, so the environment blocks the upload.
You have two options. Use a connector, which Anthropic says does not go through the session's network, or allow one extra domain.
Route 1. Add DropTheHassle as a connector
Connectors you enable on a session run through Anthropic's servers, not through the sandbox. They keep working under the Trusted setting. Anthropic does not publish one settings URL for the add-connector screen, so use the connector controls in claude.ai.
In claude.ai, add a custom connector with this URL: https://dropthehassle.com/mcp. No token.
Enable it for your Claude Code on the web session.
Ask: "Build the site, then publish the built files with DropTheHassle and give me the claim link."
Claude sends the files to the deploy_site tool and gets back a live address like yourname.dropthehassle.app with HTTPS, plus a claim link. search_domain and whoami work on that URL with no account too. What the connector can and cannot do is on the MCP guide.
The connector sends file contents in the request. Before the site is claimed, that upload can be at most 25 MB and 1,000 files, same as the command below. A normal static site fits. Large video often does not. Claiming the site raises a later signed-in update to 100 MB and 5,000 files. It does not raise this first upload.
Your AI can find a free name. Only you can pay for it.
Route 2. Allow dropthehassle.com and run the command
A free HTTPS link from one command, no account:
On claude.ai/code, open the environment selector (the cloud icon above the message box) and edit the environment.
Set network access to Custom.
Add dropthehassle.com and tick Also include default list of common package managers, so npm keeps working.
Start a session and ask Claude to build the site and run:
npx -y dropthehassle@latest deploy
The command uploads the folder you point at (the current folder, if you name none). The server publishes index.html, or dist/, build/, out/, or _site/ when that is where the built site is. public/ is used only when the upload is not a JavaScript project. It prints the live link and a claim link. You do not need --login. That flag waits for a browser approval and then publishes a new address on your account. DTH_NO_OPEN=1 only stops the command from trying to open a browser. The no-account deploy does not open one.
Full access also works. Anthropic describes Full as any domain, so it opens the session to every site. Custom with one domain plus the default list is the smaller change.
The same 25 MB and 1,000 file cap applies here until you claim the site. An unclaimed upload also refuses executable and archive files. A claimed upload can be 5,000 files.
If you prefer to keep the setting in the repo, claude mcp add --scope project writes .mcp.json. Commit that file. A cloud session with one repository loads it. Unlike a connector you enable on the session, that file is not listed as traffic that skips the allowlist, so dropthehassle.com still has to be allowed. A session with several repositories does not load it.
Claim it to keep it
Ship it on a free link first. Buy the domain when it has visitors. Open the claim link and the site is yours. An unclaimed site is kept for at least 7 days. Once claimed, the free link stays. From one network you can put 5 new unclaimed sites online per hour, and 20 a day.
The cloud machine is temporary. The first deploy writes .dropthehassle.json in that folder so the next deploy from the same folder updates the same site. If that folder already has a .gitignore, the CLI adds the file to it. Do not commit it. The machine is gone when the session ends, so a later session does not have it.
Without that file, npx -y dropthehassle@latest deploy always creates a new site. The CLI has no flag that takes a token and a site name. --login does not look one up: it asks you to approve a new address in the browser. --slug only applies to that new address, and only together with --login. The hosted connector can set the name with no account: deploy_site takes name, and choose_link renames the unclaimed site when you pass the claim link. A taken name is refused, with a few free suggestions. It is not replaced with a random one. When you pass no name, the page title is the default.
To update a site you already claimed:
Sign in and drop the new folder on that site, or
On that site, choose Update and let your AI do it. The dashboard shows a code that lasts 15 minutes. In the new session run npx -y dropthehassle@latest deploy --code XXXX-XXXX. The code fills the site it was made for, not a name you pass on the command, or
Connect with the token from Connect your AI and ask the agent to list your sites, then publish with deploy_site and that site's site_id. The free-link name is not enough on its own.
The connector at https://dropthehassle.com/mcp with no token cannot do this update. It always starts a new site and returns a new claim link. Do not commit .dropthehassle.json or any token.
Add your own domain
When it takes off, add a .com without untangling a subdomain. No DNS records to edit: the domain lives with the site.
Buy it here. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
Already own one. Add one A record at your registrar, to the address shown on your screen.
Claude can search for a free name. It can never pay. The checkout is your click. Building it for a client is a separate step: hand them the domain after you are paid your own way.
Publish your site for free
Keep secrets out of the environment
Environment variables in Claude Code on the web can be read by anyone who uses that environment. Do not store a DropTheHassle token there. The zero-account route needs no token at all.
Questions
Why does npx work but the deploy fail in Claude Code on the web?
The default Trusted network allows registry.npmjs.org and does not list dropthehassle.com. Add dropthehassle.com under Custom network access, or use a connector. Anthropic's docs say a connector you enable on a session does not go through the sandbox network.
Do I need a DropTheHassle account to deploy from a cloud session?
No. The command and the connector both work without an account and return a live yourname.dropthehassle.app link with HTTPS, plus a claim link. Before you claim it, the upload can be at most 25 MB and 1,000 files.
What happens if I don't claim the site?
The claim link works until the site is removed. An unclaimed site is kept for at least 7 days. Once claimed, the free link stays.
Can Claude buy the domain for me?
No. Claude can search for a free name, but paying is always your click. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
My app has a server part. Can I still use this?
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.
Why did a second session create a new site?
Cloud sessions start on a fresh machine, so .dropthehassle.json is gone. Without that file, npx -y dropthehassle@latest deploy creates a new site. The CLI has no flag for a token plus a site name. Claim the first site, then update it while signed in: drop the folder on that site, use the dashboard code with --code, or publish with your account token and the site id from list_sites.
Should I switch the environment to Full network access?
Full allows any domain, so the deploy works, and it opens the session to every site. Custom access with dropthehassle.com plus the default package-manager list is the smaller change.
How large can the first upload be?
25 MB and 1,000 files before you claim the site, on both the connector and the command. After you claim it, a signed-in update can be 100 MB and 5,000 files.

---
# https://dropthehassle.com/guides/codex-deploy-custom-domain

Deploy a Codex-built site to your own domain
Short answer: Codex turns network access off by default, so the deploy needs one approval. Ask Codex to run npx -y dropthehassle@latest deploy in the folder with your built site and approve the network request (in Codex cloud, first allow dropthehassle.com under the environment's internet access). You get a live yourname.dropthehassle.app link with HTTPS and a claim link, with no account; add a .com for €19 / $19 a year after you claim it.
Codex builds the site well. Publishing it is a separate step, and Codex turns network access off by default. That applies both in the CLI or IDE on your machine and in Codex cloud. Here is how to allow exactly one deploy and get a live HTTPS link without creating an account. If the side project still has 0 visitors, ship the free link first and buy the domain when it has visitors.
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: 2 October 2026. Local sandbox settings are from OpenAI's agent approvals docs. Current cloud internet settings are from cloud environments. The HTTP-method limit is from the legacy internet-access page. MCP is from Codex MCP.
Made it in ChatGPT instead? Put a ChatGPT website online. The connector details are on the MCP guide.
Which Codex are you using?
Codex CLI, IDE extension, or desktop app: the task runs on your machine in a sandbox. See the next section.
Codex cloud: the task runs in a container OpenAI manages. Skip to Codex cloud.
Codex on your machine: allow the deploy
By default the workspace-write sandbox keeps network access off, and Codex asks before it runs a command that needs the network. You have three options. A free HTTPS link from one command, no account, is the first.
Approve it once. Ask Codex: "Build the site and deploy it with npx -y dropthehassle@latest deploy." When Codex asks to run the command with network access, approve it. This is the narrower choice.
Allow network in config. In ~/.codex/config.toml:
[sandbox_workspace_write]
network_access = true
This allows network for every sandboxed command, not only the deploy.
Add the MCP server. Run:
codex mcp add dropthehassle --url https://dropthehassle.com/mcp
Or add this to config.toml:
[mcp_servers.dropthehassle]
url = "https://dropthehassle.com/mcp"
Then ask Codex to publish the built files with DropTheHassle and give you the claim link. No token. The remote tool receives the file contents directly. Before the site is claimed, that upload can be at most 25 MB and 1,000 files, same as the command. After you claim it, a signed-in update can be 100 MB and 5,000 files. Your AI can find the name. Only you can pay for it.
Every route returns a live address like yourname.dropthehassle.app with HTTPS, plus a claim link. The server publishes index.html, or dist/, build/, out/, or _site/ when that is where the built site is. public/ is used only when the upload is not a JavaScript project.
A re-deploy from the same folder updates the same site, because the command writes .dropthehassle.json there. Keep that file out of git. It holds the site's key. npx -y dropthehassle@latest status and rollback need the deploy token from --login or --code. After a no-account deploy they do not work: that link file stores a site token, not a deploy token.
Codex cloud: turn on internet for the task
Current Codex cloud and Codex Cloud (Legacy) describe internet access differently. Use the screen your environment actually has.
Current environment. OpenAI's cloud environment docs say you turn on Allow Codex to access internet, then under Allow domains choose Package managers (so npm works) or Custom domains only, and add dropthehassle.com under Additional allowed domains. All (unrestricted) also works, and it is the wider setting. Those docs do not describe an HTTP-method filter.
Legacy environment. The legacy page says setup scripts have internet access and the agent phase does not, until you enable it for that environment. You can restrict requests to GET, HEAD, and OPTIONS. That blocks the upload. Allow POST if that restriction is on.
Then ask Codex to build the site and run npx -y dropthehassle@latest deploy. The same 25 MB and 1,000 file cap applies until you claim the site. After you claim it, a signed-in update can be 100 MB and 5,000 files.
Codex's MCP docs list MCP support for the Codex CLI, the IDE extension and the ChatGPT desktop app. They do not list Codex cloud tasks, so in a cloud task use the command.
You do not need a token for this deploy, so you do not need to store one. On the legacy page, secrets are available only during setup and are removed before the agent phase. Current docs describe environment variables as values programs can read, and network secrets as values a proxy substitutes during setup and tasks. Leave the token out of both.
Claim it to keep it
Ship it on a free link first. Buy the domain when it has visitors. Open the claim link and the site is yours. An unclaimed site is kept for at least 7 days. Once claimed, the free link stays. From one network you can put 5 new unclaimed sites online per hour, and 20 a day.
A cloud task starts from a fresh container, so it does not have .dropthehassle.json. Without that file, npx -y dropthehassle@latest deploy creates a new site. The CLI has no flag that takes a token and a site name. --login asks you to approve a new address in the browser. It does not look up a site you already claimed.
To update the one you claimed: sign in and drop the new folder on that site, or on that site choose Update and let your AI do it, then run npx -y dropthehassle@latest deploy --code XXXX-XXXX with the code the dashboard shows (it lasts 15 minutes and fills that site). With the token from Connect your AI, the agent can list your sites and publish with deploy_site and that site_id. The name alone is not the key. The remote connector with no token always starts a new site.
Add your own domain
When it takes off, add a .com without untangling a subdomain. No DNS records to edit: the domain lives with the site.
Buy it here. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
Already own one. Add one A record at your registrar, to the address shown on your screen.
Codex can look up a free name. It can never pay. The checkout is your click.
Site looks fine locally but not online? See why a site works locally but not online.
Publish your site for free
Questions
Why can't Codex deploy my site?
Codex turns network access off by default: in the CLI workspace-write sandbox, and until you turn on internet access for a Codex cloud environment. Approve the deploy command, enable network access, or allow dropthehassle.com in the cloud environment.
Can I use DropTheHassle as an MCP server in Codex?
Yes, on the CLI, IDE, or desktop app. Run codex mcp add dropthehassle --url https://dropthehassle.com/mcp. No token is needed to publish. You get a live link and a claim link. In cloud tasks, use the command instead.
Do I need an account?
No. You get a free yourname.dropthehassle.app address with HTTPS and a claim link. Claim it to keep it; an unclaimed site is kept for at least 7 days. Before you claim it, the upload can be at most 25 MB and 1,000 files.
What does a .com cost?
€19 / $19 a year, including VAT in the EU, the same every year. Codex cannot pay. You check out yourself.
My Codex project has a server part. What then?
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.
Can I put my DropTheHassle token in Codex cloud secrets?
You do not need to. The zero-account deploy needs no token. On Codex Cloud (Legacy), OpenAI says secrets are available only during setup and are removed before the agent phase. Current Codex Cloud docs describe environment variables as values programs can read, and network secrets as values a proxy substitutes. Do not put a token in either place for this deploy.
Why did a cloud task create a second site?
Each cloud task starts without .dropthehassle.json. Without that file, npx -y dropthehassle@latest deploy creates a new site. The CLI has no flag for a token plus a site name. Claim the one you want, then update it while signed in.

---
# https://dropthehassle.com/guides/deploy-with-your-ai-mcp

Is there an MCP server to publish my site and manage the domain?
Short answer: Yes. Add the hosted connector https://dropthehassle.com/mcp (no token), or run the local server with claude mcp add dropthehassle -- npx -y dropthehassle-mcp@latest (Cursor and Windsurf use the same npx -y dropthehassle-mcp@latest in mcp.json). Your AI can then publish the site with deploy_site and check free names with search_domain, with no account: a first deploy returns a live HTTPS link and a claim link, and no tool can spend your money.
From a terminal the same deploy is npx -y dropthehassle@latest deploy.
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: 5 October 2026. Connector shapes are from Claude Code's MCP docs, Cursor's MCP docs, and Devin's MCP docs.
Claude Code on the web runs in a cloud machine with its own network rules: deploy from Claude Code on the web. Codex turns network access off by default: deploy a Codex-built site.
Connect it
A first deploy needs no token. On the hosted connector and on the local stdio server (npx -y dropthehassle-mcp@latest), deploy_site publishes an anonymous site and returns a claim link. search_domain and whoami work with no account too. Account tools need a token.
For a site already on your account, get your token in the dashboard, then Connect your AI. It starts with dth_. Put it in the server's environment as DTH_TOKEN. Do not commit the token. Do not paste a placeholder. Leave DTH_TOKEN unset until you have the real token.
The hosted connector is https://dropthehassle.com/mcp. Add it with no Authorization header. initialize, tools/list, ping, deploy_site, search_domain and whoami need no token. Account tools do: send the real token as Authorization: Bearer plus the value from Connect your AI. No tool spends money. On this URL, deploy_site takes the files inline (path, content, and encoding utf8 or base64) instead of a folder on your computer. Without a token, that publish is anonymous and returns a claim link. The stdio server does the same.
Add to Cursor
Claude Code
Claude Code's docs take the program after --. The server name comes first. In the project folder:
claude mcp add dropthehassle -- npx -y dropthehassle-mcp@latest
Cursor
Cursor reads mcp.json in the project (.cursor/mcp.json) or for every project (~/.cursor/mcp.json). Its stdio table lists type as required:
{
"mcpServers": {
"dropthehassle": {
"type": "stdio",
"command": "npx",
"args": ["-y", "dropthehassle-mcp@latest"]
}
}
}
Windsurf (Devin Local)
New tabs in Windsurf use the Devin Local agent. Its docs say to keep secrets in the gitignored local file .devin/mcp_config.local.json:
{
"mcpServers": {
"dropthehassle": {
"command": "npx",
"args": ["-y", "dropthehassle-mcp@latest"]
}
}
}
devin mcp add dropthehassle -- npx -y dropthehassle-mcp@latest saves a server in that local scope. Add DTH_TOKEN in the env block of the same file. Cascade, the older agent, opens its own MCP config from the Cascade panel and uses the same mcpServers shape. Windsurf's own Netlify deploy is a different feature, and the docs say it runs in Cascade, not in the Devin Local agent. That path is on the Windsurf guide.
What you can ask
Ask it to put ./dist online, update my site, or is studioname.com free. Point it at the folder that contains index.html. Before the first deploy it should offer a short name from the project, in the same question as your email. Say yes, or type another. Without a token the upload can be at most 25 MB and 1,000 files. Signed in, or after you claim the site, it can be 100 MB and 5,000 files. A folder that still needs a build is refused. So is a site that is itself a server (PHP, Node or Python): host that part on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card.
What the agent can do
Tool What it does
whoami Confirms which account the token belongs to.
list_sites Lists your sites, their live links, and which domains point at each.
search_domain Checks whether a name is free and what it would cost. Read only. A .com is €19 / $19 a year, including VAT in the EU, the same every year, the same .com prices as search in the dashboard.
deploy_site Publishes a folder with index.html on a free link, or updates a site you already have. Pass a name and it uses that address. With no name, the page title is the default. With no token, on the remote URL, it publishes an anonymous site and returns a claim link. It never buys a name. A taken name is refused, with a few free suggestions.
point_domain Rearranges a domain already on the account. It does not buy a name and it does not edit DNS at someone else's registrar.
choose_link Renames the free link after you say yes. With no account, pass the claim link from the deploy. The old link keeps redirecting.
award_readiness Checks whether a site on your account is ready for Site of the Month: favicon, share image, title and description, mobile view, page weight, your own domain, https and a real page. It needs your token.
There is no tool that buys a domain, turns email on, or gives the site to a client. Those stay clicks you make. Giving a finished site to a client is a separate step.
Paste this into CLAUDE.md or a Cursor rule.
# DropTheHassle
Never buy anything without asking me. Never buy a domain, email or subscription for me without asking first. When something costs money, give me the payment link and let me pay.
The token cannot pay.
Connect from ChatGPT or Claude
You can add DropTheHassle to ChatGPT or Claude as an app or connector with the address https://dropthehassle.com/mcp/app. You sign in with your DropTheHassle account (OAuth) instead of a dth_ token.
The app can check whether a domain name is available, and it can publish and manage your sites. It cannot buy a domain, turn on paid email, or charge a card. Buying happens on dropthehassle.com.
To revoke access, disconnect DropTheHassle in the app. In ChatGPT, open Settings, then Plugins (on older apps: Apps), and disconnect DropTheHassle. In Claude, open Customize, then Connectors, and disconnect DropTheHassle. You can also email info@dropthehassle.com and we will revoke it.
The domain is still your click
A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year, and needs no DNS edit. A domain you already own needs one A record: one line at the company where you bought it, set to the address shown on your screen. Press Check now. HTTPS follows.
Publish your site for free
Questions
Do I need a token or account to use the MCP server?
Not for a first deploy. deploy_site publishes an anonymous site and returns a claim link; search_domain and whoami also work without an account. Account tools need your dth_ token from Connect your AI, sent as Authorization: Bearer on the hosted connector or as DTH_TOKEN for the local server.
What is the hosted MCP connector URL?
https://dropthehassle.com/mcp. Add it with no Authorization header to publish. On this URL deploy_site takes the files inline instead of a folder.
How large can the first upload be?
25 MB and 1,000 files before you claim the site. After you claim it, a signed-in update can be 100 MB and 5,000 files.
Can my AI buy the domain?
No. Your AI can publish. It can never spend your money.
Does this include email?
No. Email is €5 / $5 a month, including VAT in the EU, for the first inbox and €3 / $3 a month per extra inbox. You turn it on yourself.
Can the MCP connect my backend?
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.
Related
Claude Code-website online zetten (Nederlands)

---
# https://dropthehassle.com/guides/cursor-site-own-domain

Put your Cursor website online, then on your own domain
If Cursor built your site (a folder with an index.html, or a dist folder after npm run build), you can put it online for free in minutes and add your own domain later. If it needs a database, logins or file uploads, the pages still go here and can call a backend such as Supabase. 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.
Short answer: How do I get my Cursor project online?
You already built it. Now it's on your name.
Your AI can publish. It can never spend your money.
The one command is npx -y dropthehassle@latest deploy, in the folder with your built site.
Built it with ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf or by hand? Same steps.
Last updated: 27 September 2026. The mcp.json locations are from Cursor's MCP docs.
What did Cursor build?
A website. A folder with index.html, or a dist folder after npm run build. This guide is for that.
It needs a backend. A database, logins, or file uploads need a backend. The pages can call one such as Supabase directly, or you host a server on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card: it then runs behind your own domain. We don't run the server ourselves.
An internal tool. Something only your team should open needs hosting with access control. DropTheHassle does not provide that.
Does it look like every other AI-built site? Fix that before you publish: 12 before and after fixes, and the design skills worth installing in Cursor.
Put it online in 2 minutes
If the project needs a build, run npm run build and use dist. If it is already HTML, use the folder that contains index.html. Put keys in a .env file before you build. DropTheHassle does not add them later.
Open dropthehassle.com, press Upload (free), then Drop your folder. You do not sign in first. You get https://yourname.dropthehassle.app on HTTPS. No card. Claim it with your email afterwards. An unclaimed site is kept for at least 7 days. The domain can wait.
You do not sign in first, so the upload is a zip of at most 25 MB and 1,000 files until you claim the site. After you claim it, uploads can be 100 MB and 5,000 files. It needs a page to open first (an index.html, or a single HTML page). A folder that still needs a build is refused. So is a site that is itself a server (PHP, Node or Python): host that part on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card.
Keys left out of .env before the build are not in the site. Add them, build again, and drop dist again.
Single-page apps work. When an address is not a real file, we serve your index.html with a 200, so a Vite or React app opens on any of its own routes, also after a refresh.
The Vercel CLI, the Netlify CLI, and GitHub Pages will also publish a built folder. A domain you already own still needs DNS records there. They do not include a mailbox. GitHub Pages says it is not meant as a shop. Vercel's hobby plan is published as personal, non-commercial use.
Let Cursor deploy it for you
Cursor's docs put a project connector in .cursor/mcp.json, and a connector for every project in ~/.cursor/mcp.json. A first deploy needs no token. Leave DTH_TOKEN unset, or call https://dropthehassle.com/mcp with no Authorization header. deploy_site publishes an anonymous site and returns a claim link. Copy the token from Connect your AI when the site is already on your account, and put that real value in env. Do not paste a placeholder. The full tool list is on the MCP guide. This is the project file for a first deploy:
{
"mcpServers": {
"dropthehassle": {
"type": "stdio",
"command": "npx",
"args": ["-y", "dropthehassle-mcp@latest"]
}
}
}
Then ask Cursor to put ./dist online or update my site. It can deploy, update, and check names already on your account. It cannot buy a domain, turn on email, or edit DNS at another company. Do not commit the token. Or let Cursor publish it.
Add a custom domain
A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year. No DNS edit. A domain you already own needs one A record: one line at the company where you bought the domain, set to the address shown on your screen. Press Check now. HTTPS follows. Other hosts are in the general guide.
Site looks fine locally but not online? See why a site works locally but not online.
Publish your site for free
Building it for a client?
Get paid your own way, then give them the domain. Cursor cannot do that handoff. DropTheHassle does not collect your fee.
When it has a backend too
If the project needs a server to store data, sign people in, or accept uploads, host that part on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card; the pages stay here. A database such as Supabase that the pages call directly needs nothing extra. A folder that still needs Node, PHP, or Python to answer requests can't be uploaded as it is.
If Cursor already built the folder, and the data lives in a service the browser calls, that folder can still go on the free link. The database stays on that service.
Questions
Do I need a domain?
No, not to see it working. The free link is enough to test it and to send to someone. Buy a domain when you share it more widely or sell it. A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year. Read that renewal price before you buy a name anywhere else.
What if it breaks?
Your site is a folder of files, so there are few moving parts. Keep the folder or the repo. Fix it in Cursor and publish the folder again, by dropping it or by asking Cursor to update the site.
Can I charge for access?
Not with DropTheHassle alone. You need a course platform or a payment platform. This host serves the files. It does not sign visitors in or take their payment.
Can Cursor buy the domain?
No. Your AI can publish. It can never spend your money.
Do I have to connect Cursor?
No. Dropping the folder yourself is the same publish.

---
# https://dropthehassle.com/guides/get-my-site-online

How do I get my site online?
Drop the folder with your index.html on dropthehassle.com and DropTheHassle puts it on a free HTTPS link, yourname.dropthehassle.app, in minutes. No card and no password: you give your email, get your claim link right away, and claim the site to keep it. Rather not do it yourself? Connect your AI to DropTheHassle and say put this site online with DropTheHassle.
Or from a terminal, in the folder with your built site: npx -y dropthehassle@latest deploy. No account, and you get the same free HTTPS link plus a claim link.
Last updated: 3 October 2026.
Put it online in 4 steps
Find the built folder. It's the folder with index.html in it. If your project has a build step, run npm run build first and use dist (or build or out).
Open dropthehassle.com and press Upload (free). You don't sign in first.
Drop the folder. Before you claim the site it can be up to 25 MB and 1,000 files. Give your email when the page asks, right after the drop.
Open your link and claim it. Your site is live at https://yourname.dropthehassle.app. Claim it on the same screen to keep it: an unclaimed site is removed after at least 7 days.
Or let your AI do it
Connect the DropTheHassle MCP server once and ask in plain words:
https://dropthehassle.com/mcp
Then say: Put this site online with DropTheHassle. Your AI publishes the site and gives you the live link and the claim link. It can hand you a payment link for a domain, but it can never spend your money.
Set-up per tool: Claude Code, Cursor, all tools.
What it costs
What Price
Free link yourname.dropthehassle.app with HTTPS Free, no card. Claim it and it stays.
.com, .org or .net €19 / $19 a year, including VAT in the EU, the same every year
.nl or .eu €12 / $12 a year, including VAT in the EU
.app €25 / $25 a year, including VAT in the EU
Email at your own name €5 / $5 a month, including VAT in the EU, for the first inbox. €3 / $3 a month per extra inbox.
A name bought here needs no DNS setup. A domain you already own needs one A record. We don't offer .co, .shop, .studio, .io or .ai. Check a name.
Questions
Is it really free?
Yes. The yourname.dropthehassle.app link with HTTPS costs nothing and needs no card. Claim it to keep it: an unclaimed site is removed after at least 7 days.
Why can't my friends open my localhost link?
localhost is your own computer, so only you can open it. Put the built folder on DropTheHassle and send the yourname.dropthehassle.app link instead. It keeps working when your laptop is off.
Can my AI put my site online for me?
Yes. Connect https://dropthehassle.com/mcp and say put this site online with DropTheHassle. It can publish and give you a payment link, but it can never spend your money.
How do I get my own .com?
Search the name on dropthehassle.com. A .com is €19 / $19 a year, including VAT in the EU, the same every year, and a name bought here needs no DNS setup. A domain you already own needs one A record.
Does it work with a React or Vite app?
Yes. Run npm run build and drop the dist folder. Single-page apps work: an address that is not a file serves your index.html with a 200.
My app has a server part. Can it go online too?
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.
More
Only have one HTML file from ChatGPT or Claude? Put an HTML file online
No GitHub account? Put your site online without GitHub
Already online? Update your site
Comparing hosts? HostScore's guide to the best hosting for vibe coding
All guides
Publish your site for free

---
# https://dropthehassle.com/guides/get-claude-code-site-online

How do I get my Claude Code site online?
Connect DropTheHassle to Claude Code once, then say Put ./dist online with DropTheHassle: Claude Code sends your site and you get a free HTTPS link, yourname.dropthehassle.app. Claude Code builds the site but doesn't host it, and DropTheHassle is the host, free to start with no card. You can also drop the folder on dropthehassle.com yourself.
Last updated: 3 October 2026. The connector command follows Claude Code's MCP docs.
Put it online from Claude Code
Build it. Ask Claude Code to build the site, or run npm run build. You get a dist folder. A plain HTML site is ready as it is: use the folder with index.html.
Connect DropTheHassle once. In your project folder, run:
claude mcp add --transport http dropthehassle https://dropthehassle.com/mcp
No account and no token needed for a first deploy.
Prefer one command? In the same folder, tell Claude Code to run npx -y dropthehassle@latest deploy and approve it. Same free link.
Ask for it. Start Claude Code and type: Put ./dist online with DropTheHassle. Give your email when it asks.
Open your link and claim it. Claude Code replies with your live link and a claim link. Open the claim link to keep the site: an unclaimed site is removed after at least 7 days.
Rather click than type? Open dropthehassle.com, press Upload (free) and drop the dist folder. It's the same free link.
What Claude Code can and can't do here
It can publish your site, check whether a name is free and what it costs, and hand you a payment link. It can't buy a domain or spend your money: paying is always your click. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
Questions
Can Claude Code host my website?
No. Claude Code builds the site and can deploy it, but it needs a host. With DropTheHassle connected, it puts the site on a free HTTPS link and gives you a claim link.
Do I need GitHub or an account?
No. A first deploy needs no GitHub, no account and no token. Give your email when it asks, and claim the site to keep it.
How big can the site be?
Up to 25 MB and 1,000 files before you claim it, and 100 MB and 5,000 files after. Too big for Claude Code to send? Drop the folder on dropthehassle.com yourself.
Can Claude Code buy my domain?
No. It can check names and hand you a payment link, but it can never spend your money. Paying is your click.
How do I update the site later?
Claim the site, then add your token from Connect your AI in the dashboard. After that, ask Claude Code to update my site and it updates the same address.
My app has a server part. Can it go online too?
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.
More
Full guide: Claude Code site on your own domain
Using Claude Code in the browser?
Everything the connector can do
How do I get my site online?
Check a name
All guides
Publish your site for free

---
# https://dropthehassle.com/guides/get-cursor-project-online

How do I get my Cursor project online?
Add DropTheHassle to Cursor's mcp.json, then ask the agent Put ./dist online with DropTheHassle: you get a free HTTPS link, yourname.dropthehassle.app, with no card. Cursor builds the project, and DropTheHassle hosts it. You can also drop the built folder on dropthehassle.com yourself.
Last updated: 3 October 2026. The mcp.json shape follows Cursor's MCP docs.
Put it online from Cursor
Build it. Ask the agent to run npm run build, or run it yourself. Use the dist folder (or build or out). A plain HTML project is ready as it is.
Connect DropTheHassle once. Add this to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for every project):
{
"mcpServers": {
"dropthehassle": {
"url": "https://dropthehassle.com/mcp"
}
}
}
No account and no token needed for a first deploy.
Prefer one command? In the agent chat, ask it to run npx -y dropthehassle@latest deploy in the built folder. Same free link.
Ask for it. In the agent chat, type: Put ./dist online with DropTheHassle. Give your email when it asks.
Open your link and claim it. The agent replies with your live link and a claim link. Open the claim link to keep the site: an unclaimed site is removed after at least 7 days.
Rather click than type? Open dropthehassle.com, press Upload (free) and drop the dist folder. It's the same free link.
Questions
Why does my Cursor project only work on localhost?
localhost is your own computer, so only you can open it. Put the built folder on DropTheHassle and you get a link anyone can open.
Do I need GitHub or an account?
No. A first deploy needs no GitHub, no account and no token. Give your email when it asks, and claim the site to keep it.
Does it work with a React, Vite or Next.js static export?
Yes, when the build gives you a folder with index.html. Single-page apps work: an address that is not a file serves your index.html with a 200.
Can Cursor buy my domain?
No. It can check names and hand you a payment link, but it can never spend your money. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
How do I update the site later?
Claim the site, then add your token from Connect your AI in the dashboard. After that, ask the agent to update my site and it updates the same address.
My app has a server part. Can it go online too?
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.
More
Full guide: Cursor site on your own domain
Everything the connector can do
How do I get my site online?
Check a name
Using Windsurf?
All guides
Publish your site for free

---
# https://dropthehassle.com/guides/windsurf-deploy-custom-domain

Put your Windsurf website online, then on your own domain
If Windsurf built your site (a folder with an index.html, or a dist folder after npm run build), you can put it online for free in minutes and add your own domain later. If it needs a database, logins or file uploads, the pages still go here and can call a backend such as Supabase. 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.
You already built it. Now it's on your name.
Your AI can publish. It can never spend your money.
The one command is npx -y dropthehassle@latest deploy, in the folder with your built site.
Built it with ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf or by hand? Same steps.
Last updated: 27 September 2026. Windsurf facts are from the App Deploys docs and the Devin MCP docs.
What did Windsurf build?
A website. A folder with index.html, or a dist folder after npm run build. This guide is for that.
It needs a backend. A database, logins, or file uploads need a backend. The pages can call one such as Supabase directly, or you host a server on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card: it then runs behind your own domain. We don't run the server ourselves.
An internal tool. Something only your team should open needs hosting with access control. DropTheHassle does not provide that.
What App Deploys already does
App Deploys is in beta. The docs say it runs through Cascade, and it does not run with the Devin Local agent. You ask Cascade to deploy the project to Netlify, or you use Deploy. Cascade uploads the project to Windsurf's servers and publishes it on Netlify under their account. You get a public address like name.windsurf.build, a claim link, and a windsurf_deployment.yaml file so a later deploy can hit the same project.
Claiming the project moves it to your own Netlify account. The docs say that gives you control, logs, and the ability to change the domain name there. They do not describe Windsurf selling a domain, and they do not describe a mailbox. Unclaimed deploys may be deleted. The rate limits on that page are 1 deployment a day and 1 unclaimed site on Free, and 5 of each on Pro. Supported projects on that page are Next.js, React, Vue, Svelte, and static HTML, CSS, and JavaScript.
You cannot rename a windsurf.build address after it exists. The docs say to delete windsurf_deployment.yaml and deploy a new site. A .netlify.app name, after you claim, is changed in Netlify's settings. For a domain you own, and for mail if you want it, publish the built folder on DropTheHassle.
Put it online in 2 minutes
The project is already on your computer. If it needs a build, run npm run build and use dist. If it is already HTML, use the folder that contains index.html. Put keys in a .env file before you build.
Drop that folder at dropthehassle.com. You get https://yourname.dropthehassle.app on HTTPS. No card. The domain can wait. You do not sign in first, so the upload is a zip of at most 25 MB and 1,000 files until you claim the site. After you claim it, uploads can be 100 MB and 5,000 files. It needs a page to open first (an index.html, or a single HTML page). A folder that still needs a build is refused. So is a site that is itself a server (PHP, Node or Python): host that part on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card.
Single-page apps work. When an address is not a real file, we serve your index.html with a 200, so a Vite or React app opens on any of its own routes, also after a refresh.
Let Windsurf deploy it for you
The Devin Local agent can publish the same folder. A first deploy needs no token. Omit DTH_TOKEN, or use https://dropthehassle.com/mcp with no Authorization header. deploy_site publishes an anonymous site and returns a claim link. Put the token from Connect your AI in .devin/mcp_config.local.json when the site is already on your account, so it is not committed. The shape is on the MCP guide. Then ask it to put ./dist online. It can deploy and update. It cannot buy a domain, turn on email, or edit DNS at another company.
App Deploys is the other path, and it stays a windsurf.build preview. The docs say that path runs in Cascade, not in the Devin Local agent.
Add your own domain
A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year. No DNS edit. A domain you already own needs one A record: one line at the company where you bought the domain, set to the address shown on your screen. Press Check now. HTTPS follows.
Staying on the claimed Netlify site is a real option. A domain you already own then uses Netlify's DNS instructions, and that host does not include a mailbox.
Site looks fine locally but not online? See why a site works locally but not online.
Publish your site for free
Building it for a client?
Get paid your own way, then give them the domain. The connector cannot give a name away. DropTheHassle does not collect your fee.
When it has a backend too
If the project needs a server to store data, sign people in, or accept uploads, host that part on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card; the pages stay here. A database such as Supabase that the pages call directly needs nothing extra. A folder that still needs Node, PHP, or Python to answer requests can't be uploaded as it is.
If Windsurf already built the folder, and the data lives in a service the browser calls, that folder can still go on the free link. The database stays on that service.
Questions
Do I need a domain?
No, not to see it working. The free link is enough to test it and to send to someone. A windsurf.build address is a preview, not a domain you own. Buy a domain when you share it more widely or sell it. A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year.
What if it breaks?
Your site is a folder of files, so there are few moving parts. Keep the folder or the repo. Fix it in Windsurf and publish the folder again, by dropping it or by asking the agent to update the site.
Can I charge for access?
Not with DropTheHassle alone. You need a course platform or a payment platform. This host serves the files. It does not sign visitors in or take their payment.
Does Windsurf include my own domain?
The preview address is on windsurf.build. A custom domain, in their docs, comes after you claim the deploy on your Netlify account and change it there. That is not a domain Windsurf sells, and it is not email.

---
# https://dropthehassle.com/hand-a-domain-to-a-client

How do I hand a website and domain to a client?
Get paid first, your own way. Then choose Give a domain to someone, enter their email, and the site becomes theirs when they claim it. You already built it. Now it's on their name.
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: 26 September 2026.
Get paid, then hand it over
DropTheHassle does not invoice your client and does not send you their payment for the build. Send your invoice however you already do. When that is settled, the handover below moves the site off your account.
Publish the built folder first, on the free link or on the domain. A free link with no domain cannot be given. Buy a domain here, or connect one you already own, before you give it.
In the dashboard, choose Give a domain to someone. Pick one name, or the whole group of names on that site. Giving a single name out of a group splits that name onto its own site first, then sends it.
Type their email and send it. They get a code at that address. The name stays on your account until they claim it, and you can cancel until then. You are not charged again for the time you already paid.
They log in with that same email, enter the code, and see the renewal price and date. They add a card, or we use the card already on their account. The screen says they are not charged now.
If the site has email, they can take the mailbox too. If they do not, email pauses. A mailbox they take over stays free until the month you already paid ends, then the first inbox is €5 / $5 a month, including VAT in the EU, and €3 / $3 a month per extra inbox.
When they claim it, the site leaves your account. A connector that was publishing that site stops with the handoff. If they want their own AI to update it, they connect theirs from Connect your AI. The agent on your side cannot give the domain away.
What moves, and what does not
A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year, on their card from the next renewal. They see that price before they take it over. The site is theirs as soon as they claim it. The registration contact for a domain bought here is updated afterwards. It is not finished in that same click. If it has not moved, mail info@dropthehassle.com.
A domain you connected from another company moves the site on DropTheHassle. It does not move the registration at that other company. The client still needs that login, or you transfer the name there yourself.
Publish your site for free
Questions
Can I hand over the free link only?
No. Give a domain to someone needs a domain on the account. The free link is how you show the work before that.
Can my AI do the handover?
No. Your AI can publish the folder. Giving the domain away is your click, after you have been paid.
Who pays the renewal?
They do, on the card they add, starting at the next renewal. A .com bought here stays €19 / $19 a year, including VAT in the EU, the same every year. They are not charged for the period you already paid.

---
# https://dropthehassle.com/guides/chatgpt-website-online

ChatGPT made me a website: how do I put it online?
Save what ChatGPT gave you as index.html, drop the folder on dropthehassle.com, and it's online on a free HTTPS link in minutes; add your own .com for €19 / $19 a year when you want it. You don't need Plus, FTP or a hosting plan for any of it.
If you pay for Plus or higher, there's a second option: ChatGPT Sites can host it on a chatgpt.site address and connect a domain you already own. You buy that domain somewhere else and add the DNS records yourself. With Plus and a domain already in hand, that works fine; when Sites makes sense is further down.
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. ChatGPT Sites facts are from OpenAI Help and the Sites guide (help.openai.com/en/articles/20001339, learn.chatgpt.com/docs/sites) and the 9 July 2026 release notes.
Built it with Codex instead? Deploy a Codex-built site to your own domain.
ChatGPT gave me code blocks, a zip or a Canvas: what to do with each
ChatGPT hands you code, not a website that's already live somewhere. Here's what to do with each thing it might give you:
One HTML code block. Hit Copy or Download on the block and save it as index.html in a new, empty folder. Done.
Separate blocks for HTML, CSS and JavaScript. Save each one under the name the code uses, such as style.css and script.js, all in the same folder. Or save yourself the bother and ask: Rewrite this as one self-contained index.html with all CSS and JavaScript inline.
A zip. Unzip it and look for the folder with index.html. A package.json in there means it needs a build first: run npm run build, then use the dist folder.
A Canvas. The preview only shows inside ChatGPT. Copy the code out of the Canvas and save it as index.html, same as a code block.
A preview or share link for that code stays inside ChatGPT, so it isn't something you can hand people as a website.
Watch out when saving. Notepad likes to quietly add .txt: set the type to All files and name it index.html. TextEdit saves rich text unless you choose Format, then Make Plain Text first.
Put it online in 4 steps
One folder, everything in it: index.html plus any CSS, scripts and images it uses.
Go to dropthehassle.com and press Upload (free). You don't make an account first.
Press Drop your folder and drag the folder in, or a .zip of it. The page asks for your email right after. Until you claim, uploads can be 25 MB and 1,000 files.
Keep it. It's already live on https://yourname.dropthehassle.app, with HTTPS and no card. Press Claim this site on the same screen, or it's removed after at least 7 days. Claimed sites can be 100 MB and 5,000 files.
Until you claim it, a small Made with DropTheHassle bar sits at the bottom (visitors can close it), and search engines are asked to leave the site out for now.
Several pages that link to each other work as they are: keep index.html as the front page and link the rest by file name, like about.html. If ChatGPT built an app with its own routes, refreshing still works, because an address that isn't a file gets your index.html.
Or let your AI publish it
Coding with Codex, Claude Code or Cursor as well? Then you can skip the dragging. Connect DropTheHassle once and say publish this site with DropTheHassle. The hosted server is https://dropthehassle.com/mcp, with no token for a first deploy; tools that run a local server use npx -y dropthehassle-mcp@latest. You get the live link and a claim link back. Setup for each tool is in Publish from your AI.
Using the Claude app? Add https://dropthehassle.com/mcp as a custom connector (on claude.ai or Claude Desktop; it shows up in the phone app).
Images or styling missing after upload
The page loads but looks bare, or the pictures are gone? The HTML is pointing at files that aren't in the folder you uploaded. The usual suspects:
Files you never saved. If the code mentions style.css or images/photo.jpg, those files have to sit in the folder, in exactly that spot. ChatGPT often writes the reference while you only saved the HTML.
Paths to your computer. Something like C:\Users\you\Pictures\photo.jpg only works on your laptop. Use images/photo.jpg.
Capital letters. Online, Photo.JPG and photo.jpg are different files. Make the code match the file.
Placeholder images. Some code borrows example pictures from other sites. Swap in your own.
Still stuck? Go through the five usual causes one by one.
Netlify Drop, Tiiny Host or DropTheHassle?
All three let you put a folder or an HTML file online without touching a terminal. Side by side:
Netlify Drop Tiiny Host DropTheHassle
How Drag a folder onto netlify.com/drop Upload an HTML file or zip Drop your folder or .zip on dropthehassle.com
Account first No. Claim the site or it expires Sign-up with an email for the free plan, which asks you to log in again every 3 months. No. Claim the site or it is removed after at least 7 days
Free plan A live link on a Netlify address 1 site, 3 MB, 5,000 visits a month, with a banner A link on dropthehassle.app, up to 25 MB and 1,000 files before claim, 100 MB and 5,000 files after
Your own domain Can be connected On the paid Solo plan and up A .com bought here is €19 / $19 a year with no DNS setup, or one A record for a domain you own
Email on your domain Not part of Drop Not on the free plan €5 / $5 a month for the first inbox
Sources: Netlify's post on Netlify Drop (netlify.com/blog/thirteen-years-of-netlify-drop) and Tiiny Host's HTML hosting page (tiiny.host/host-html-file), both checked 3 October 2026. Plans change, so look at their pages before you pick. More hosts are lined up in Compare hosts.
ChatGPT Sites, on a paid plan
ChatGPT Sites has been in public beta since 9 July 2026 for Plus, Pro, Business, Enterprise and Edu. It's not on Free or Go. It hosts the site, including a light app with a database, sign-in and analytics, on an address on chatgpt.site. You can rename that address, and the old one redirects.
Sites doesn't sell domains. To connect one you already own:
Add domain.
Add the DNS records Sites shows, wherever you bought the domain. Use the values on that screen. This page does not print them.
Refresh the domain status.
Custom domains aren't available in Enterprise at launch, and plan limits apply during the beta. OpenAI's help doesn't mention email, an export button or an API. Anything in the page that calls ChatGPT stops working once the file is hosted elsewhere, and saved records and uploaded files stay on Sites.
So which one? Already paying for Plus, already own a domain, fine with DNS records: Sites will do. On the free plan, want the domain bought without DNS work, want email on your name, or want the site to outlive your ChatGPT plan: go with the steps above.
Your own domain
Buy it here and there's no DNS to edit: a .com is €19 / $19 a year, including VAT in the EU, the same every year, and a .nl or .eu is €12 / $12 a year. You pick the name in your dashboard and pay through Stripe yourself, and it's hooked up to your site for you.
Already have a domain somewhere? Add one A record there, pointing at the address on your screen, and press Check now. That's a single line in the domain's settings telling it which server your site lives on. HTTPS follows without you uploading a certificate. If the name already gets mail, leave the MX records alone: MX decides where mail goes, the A record is only the website.
The first inbox here is €5 / $5 a month, including VAT in the EU, and €3 / $3 a month per extra inbox. This page does not suggest forwarding mail to a free personal inbox. DNS, HTTPS and other hosts are also in the general guide.
Common mistakes
The browser shows your code as text. The file is really index.html.txt, or it was saved as rich text. Save it again as plain text called index.html.
Uploading just the HTML file. When ChatGPT made several files, the whole folder goes up, not only index.html.
A project that still needs a build. A project zip before build is refused. Run npm run build and use dist.
Sending people the ChatGPT preview. It only opens inside ChatGPT. Share your own link instead.
Forgetting to claim. An unclaimed site is gone after at least 7 days, so claim it while the screen is still open.
Copy this prompt to ChatGPT
Paste this into the same chat. It turns whatever ChatGPT made into one file that works anywhere, plus a list of the images to put next to it.
Rewrite this website as one self-contained index.html file, with all CSS and JavaScript inline.
Keep every image as a relative path like images/photo.jpg, and give me a list of the image files I need to put in an images folder next to index.html.
Do not use anything that only works inside ChatGPT.
Questions
How to host a website made by ChatGPT?
Save the code as index.html in a folder and drop the folder on dropthehassle.com. It's on a free yourname.dropthehassle.app link with HTTPS within minutes, no card needed. On Plus or higher, ChatGPT Sites can host it too.
How do I put my website online?
Get all the files into one folder with index.html at the top. Press Upload (free) on dropthehassle.com, drop the folder, and claim the site so it stays. Your own domain can come later.
Can ChatGPT actually create a website?
Yes. It writes the HTML, CSS and JavaScript for a whole site. Getting it online is a separate step: ChatGPT Sites on paid plans, or on any plan by saving the code as index.html and putting the folder on a host.
Can ChatGPT connect my own domain?
Yes, with ChatGPT Sites on paid plans, for a domain you already own.
What if my site uses a database or ChatGPT sign-in?
The pages can still go here. 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. ChatGPT sign-in itself only works on Sites.
Does that include email?
Email on ChatGPT Sites is not documented. A mailbox you can send from is €5 / $5 a month, including VAT in the EU, for the first address on DropTheHassle, then €3 / $3 a month per extra inbox.
Can my AI buy the domain?
No. It can publish the folder and send you a payment link, but buying the domain is your click.
Keep going
Made it with Claude instead? Publishing a Claude site
My site works on my computer but not online
Any AI-made HTML page, online for free
Deze gids in het Nederlands
Got your index.html saved? You're one drag away from a link you can text to someone.
Put my ChatGPT site online

---
# https://dropthehassle.com/guides/claude-website-online

Claude made me a website: how do I publish it?
Download the code Claude made as index.html (or the zip), drop it on dropthehassle.com, and you get a public HTTPS link in minutes, with no GitHub, no terminal and no card. When you want a real name on it, a .com is €19 / $19 a year, including VAT in the EU, the same every year.
If you've been sending people the artifact link and wondering why it still says claude.ai, this is the fix.
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. Artifact sharing facts are from Anthropic's help pages on publishing and sharing artifacts.
Publish it in 4 steps
Get the code out of Claude. In the artifact, use Copy or Download and save it as index.html in a new folder. Did Claude give you a zip? Unzip it and find the folder with index.html. Several files? Ask Claude: Put all of this in one self-contained index.html, with the CSS and JavaScript inline.
Head to dropthehassle.com and press Upload (free). There's no sign-up step before this.
Press Drop your folder and drag it in, or the .zip. When the page asks for your email, give it. The cap before you claim is 25 MB and 1,000 files.
Claim it. You're now live on https://yourname.dropthehassle.app, on HTTPS. Hit Claim this site on that screen so it stays; unclaimed sites go after at least 7 days. Once it's claimed you get 100 MB and 5,000 files.
Anyone can open your link, Claude account or not. Until you claim, there's a small bar at the bottom and the site stays out of search results.
Artifact, Claude Design or Claude Code: which one did you use?
Claude can make a website in three places, and each hands you the code a little differently.
Where you made it What you have What to publish
A Claude chat (an artifact) Code in a panel next to the chat Copy or download it as index.html
Claude Design A design or prototype in Claude Ask Claude for the design as one index.html or a zip, then publish that
Claude Code A project folder on your computer The folder with index.html, or dist after npm run build
Used Claude Code? It can publish the site itself. Can Claude Code host my website? has the short answer, and the full Claude Code guide walks through the rest.
Why not just share the artifact link?
You can, as a demo. Older chat artifacts have Publish (Free, Pro or Max): a public link on claude.ai that anyone can open without an account. Newer artifacts use Share: on Pro and Max you can share by link, and viewers need a Claude account. On Team and Enterprise, artifacts stay inside the organisation unless external sharing is switched on.
The catch is that none of those links is yours. They live on claude.ai with Claude's frame around your page, you can't put your own domain on them, and search engines don't treat them as your site. Your own link opens on its own, for anyone, and can carry your domain and email later. Nothing stops you keeping the claude.ai link up as well.
Or let Claude publish it
Easier still: let Claude do the upload. You connect DropTheHassle once and then just ask.
Using the Claude app? Add https://dropthehassle.com/mcp as a custom connector (on claude.ai or Claude Desktop; it shows up in the phone app).
In Claude Code, run this in a terminal in your project:
claude mcp add --transport http dropthehassle https://dropthehassle.com/mcp
Then ask it to publish this site with DropTheHassle. It'll want your email, and it comes back with the live link and a claim link. The first one needs no account and no token. Claude can also check whether a domain is free and hand you a payment link, but paying for anything is off the table for it.
Can I edit or add pages later?
Yes. Keep working with Claude the way you were, then swap in the new version one of two ways:
By hand. Claim the site first. In your dashboard, press Update website, then Drop your new files. The current site stays up until the new one is on.
Through Claude. Claim the site, open the menu top right on dropthehassle.com and pick Connect your AI. After that, telling Claude update my site publishes the new version to the same address.
Want more pages? Ask Claude to put each one in its own file, like about.html and contact.html, next to index.html, linked by file name. Then upload the whole folder. Don't love the name of your link? You can rename it later, and the old one redirects.
Put it on your own domain
When you're ready for a real name, you've got two routes. Buy a .com here for €19 / $19 a year, including VAT in the EU, the same every year, or a .nl or .eu for €12 / $12 a year. You pick it in your dashboard and check out through Stripe yourself, and you never touch DNS: it's wired to your site for you.
Or use a domain you already have. Add one A record at the company you bought it from, pointing at the address on your screen, then press Check now. HTTPS switches on by itself. If that domain already gets email, leave the mail records exactly as they are.
Email at that name is optional: €5 / $5 a month, including VAT in the EU, for the first inbox and €3 / $3 a month for each extra one. For DNS questions and other hosts, see the general guide.
Common mistakes
Saving only part of the code. If Claude split it over several files, they all go in one folder. Or ask for a single self-contained index.html.
A file called index.html.txt. Notepad adds .txt unless you pick All files, and TextEdit saves rich text unless you switch to plain text. Either way the browser shows code instead of your page.
Images that vanish online. The code points at files that aren't in the folder, or the capital letters don't match. Put the images next to index.html and copy each name exactly.
Features that ask Claude something. Anything in the artifact that calls Claude only works on claude.ai. Data the app stored in Claude doesn't come along with the file either.
Uploading a Claude Code project before building it. A project zip before build, or a folder with no page to open first, is refused. Run npm run build and upload dist.
Fine on your computer, broken online? These five checks find it.
Questions
How do you publish a website you created?
Collect everything in one folder, with index.html at the top level, then press Upload (free) on dropthehassle.com and drop the folder in. A public HTTPS link appears within minutes. Claim it so it stays, and add your own domain whenever you like.
How to publish Claude design?
Ask Claude for the design as one self-contained index.html, or a zip of the files. Then drop that on dropthehassle.com, the same way as an artifact.
Does Claude give me my own domain?
No. Publish or Share gives a public link on claude.ai. Claude does not provide a custom domain.
Will ask-Claude features keep working?
Features that call Claude inside the artifact stop working once the file is hosted elsewhere. Data the app stored in Claude does not come with the file.
Do I need GitHub or a terminal?
No. You drop the file or folder in your browser. The only time you need a terminal is for a project with a build step, and Claude Code can run that build for you.
How do I get Claude to make me a website?
Tell Claude what the site is for, who it's for and which pages you want, and ask for a single index.html with the CSS and JavaScript built in. Keep asking for changes in the same chat until you like it, then download the file and publish it.
How much does it cost to make a website with Claude?
On the Free plan you can make an artifact, but you can share it by link only if it is an older chat artifact with Publish. Sharing a newer artifact by link needs Pro or Max, and viewers need a Claude account. Putting it online here is free: the yourname.dropthehassle.app link on HTTPS costs nothing and needs no card. You only pay for your own domain or email, and you pay yourself.
What if my site has a server part?
The pages people see can go here. 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.
More from here
Put a Claude Code website online
The same question, for a site ChatGPT made
When it works locally but not online
Update your site after it's online
Claude Code-site online zetten, in het Nederlands
Your artifact is already done. Getting it on a link of its own is the quick part.
Publish my Claude site

---
# https://dropthehassle.com/guides/site-works-locally-not-online

My site works on my computer but not online
If your site works on localhost but shows a blank page, missing images or a 404 once it's online, it's almost always one of three things: you uploaded the project instead of the built folder (dist, build or out), your paths point at your own computer, or a file name differs only in capital letters. The other two, settings that only live on your laptop and an app that needs a server, come up less often.
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.
Common mistakes, by what you see
Start with what's actually on your screen. It usually points straight at the cause.
What you see online Usual cause Fix
A blank white page The project went up, not the built folder Run npm run build, upload dist
A list of files, or a 404 on the front page No index.html at the top of the folder Upload the folder that has index.html in it
Text, but no styling or images Paths to your own computer, or capital letters Make paths relative, match file names exactly
A 404 when you refresh a page The host doesn't send unknown addresses to index.html On DropTheHassle this already works
Sign-in or data won't load Settings only on your laptop, or a server that isn't online See causes 4 and 5
Why localhost is not the internet
localhost just means this computer. When you run npm run dev or open a preview, your laptop is serving the site to itself, and nobody else can open that address. The dev server is also forgiving: it builds your code on the fly and usually finds a file even when the capital letters are off.
Once it's online, the host only has the files you gave it. Nothing gets built, nothing on your laptop can be reached, and every name has to match exactly. That gap is why a site can look perfect at home and fall over the moment it goes live.
Cause 1: you uploaded the project, not the built folder
This is the big one. If there's a package.json in your folder (React, Vite, Astro, a Next.js export, most AI builders), the files you've been editing are the source, not the finished site, and a browser can't run them as they are. Run npm run build, or ask your AI to, and a new folder shows up: dist for Vite, build for Create React App, out for a Next.js export. That's the one that goes online.
DropTheHassle refuses a project zip that still needs a build, and a folder with no page to open first (no index.html and no single HTML page), so you see the problem at once instead of a blank page you only notice a week later.
Cause 2: your paths point at your own computer
Search your code for C:\Users\you\site\logo.png, /Users/you/..., file:// or http://localhost:3000. They work at home because the file really is there. Online they point at nothing. Swap them for paths relative to index.html, like images/logo.png.
On Vite, also glance at the base setting in vite.config. If the site sits at the root of its own link, the default is what you want.
Cause 3: capital letters in file names
Windows and macOS mostly don't care whether a file is called Logo.png or logo.png. Web servers do. Code that asks for Hero.JPG when the file is hero.jpg gives you a missing image online and a perfectly fine one at home. The easy rule: lower case for every file name, and make the code match.
Cause 4: keys and settings that only exist on your laptop
API keys and settings often live in a .env file, and that file stays on your computer. For a site that's built into a folder, the values get baked in at build time, so the .env has to be there before npm run build, not after. One warning: visitors can read anything in the built folder, so only public keys belong there, like a Supabase anon key.
Signing in bounces you back to localhost? Your sign-in provider still has the old address. Add your live one, like https://yourname.dropthehassle.app, to its list of allowed redirect addresses.
Cause 5: your app needs a server or a database
If you start the project with node server.js, python app.py or something like it, part of it is a program that has to keep running. A folder of files can't do that on its own. The pages people see can still go online as a folder. 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.
Fix it in 5 checks
Is there a build step? With a package.json, run npm run build and upload dist, build or out.
Are all paths relative? Search the code for C:\, /Users/, file:// and localhost.
Do the capital letters match? Hold each file name in the code up against the real file.
Are your settings in the build? .env in place before you build, and your live address in any sign-in redirect list.
Does anything need a server? Then that part lives on a server, and the pages go online.
Copy this to your AI
Faster than doing the checks by hand: paste this into whichever AI built the site. It goes through all five and tells you what it changed.
My site works on my computer but not once it is online. Please check these five things and fix what you find:
1. Does this project have a build step? If so, run it and tell me exactly which folder to upload (dist, build or out).
2. Find every path that points at my own computer (C:\, /Users/, file://, localhost) and make it relative.
3. Check that every file name in the code matches the real file exactly, including capital letters.
4. List the settings from .env that the site needs, and make sure they are in the build.
5. Tell me if any part needs a server to run, and which part.
Then tell me which folder to upload.
Just want a link that works?
Once you know which folder it is, this part takes a couple of minutes:
Open dropthehassle.com and press Upload (free). There's no account to make first.
Press Drop your folder and drop in dist, or whichever folder has index.html. A .zip works too. Give your email when it asks. Before you claim, the limit is 25 MB and 1,000 files.
A link like https://yourname.dropthehassle.app appears straight away. It has HTTPS, and nobody asks for a card.
Then hit Claim this site on that same screen. Unclaimed sites are removed after at least 7 days; claimed ones can grow to 100 MB and 5,000 files.
Apps with their own routes survive a refresh too: any address without a matching file is answered with your index.html. Want your own name on it later? A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year, with nothing to set up in DNS. The rest is in how to get your site online.
Questions
Why does my website work on my computer but not on the internet?
Your computer has the whole project, a dev server that builds it on the fly, and file names that only need to match loosely. The host only has what you uploaded. Usually the project went up instead of the built folder, a path points at your own computer, or a file name differs in capital letters.
Why is my site a blank page after I upload it?
Nearly always because the project was uploaded instead of the built folder. Run npm run build and upload dist, build or out. Still blank? Open the browser console: a red 404 on a script or style file means a path problem.
How do I share my localhost site with friends?
You can't send a localhost link: it only opens on your own computer. Tunnel tools can show it while your computer stays on. For a link that keeps working when your laptop is shut, put the built folder online, for example on a free yourname.dropthehassle.app link.
Why does my website not work with www in front of it?
www is a separate name in your domain's settings, so it needs its own DNS record pointing at the same place. On DropTheHassle, www works when its DNS points here.
Why do my images show at home but not online?
Either the path in the code points at your own computer, or the capital letters in the file name don't match. Use relative paths like images/photo.jpg and make each name match the real file exactly.
Can my AI fix this for me?
Most of the time, yes. Paste the prompt from this page into the AI that built the site. It checks the five causes, fixes what it finds and tells you which folder to upload.
Where to go next
How do I get my site online?
Getting a Claude Code project live
ChatGPT made me a website: how do I put it online?
Have your AI do the upload
Found the culprit? Then the only thing left is putting the right folder online.
Try it with your dist folder

---
# https://dropthehassle.com/guides/where-to-host-vibe-coded-app

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.
The one command is npx -y dropthehassle@latest deploy, in the folder with your built site. No account for the first deploy.
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
How do I get my site online?
Can I put my site online without GitHub?
How do I update my site after it's online?
Netlify vs Vercel vs Cloudflare Pages, renewal prices included
Move your app off Lovable or Replit
Need Node hosting? GoDaddy Node.js Hosting vs DropTheHassle
In het Nederlands: je vibe-coded website online zetten
Know which folder it is? Then the hosting part takes a couple of minutes.
Drop your folder, free

---
# https://dropthehassle.com/guides/put-site-online-without-github

Can I put my site online without GitHub?
Yes: you don't need GitHub, a repo or a terminal to put a site online. Drop the folder with your index.html (or the dist folder after npm run build) on dropthehassle.com and it's live on a free HTTPS link in minutes, with no card and no account to set up first. GitHub is useful for keeping versions of your code, but it isn't a step you have to take before anyone can see your site.
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. What this page says about Netlify Drop, Vercel Drop and the Vercel CLI, Cloudflare Pages and GitHub Pages comes from their own docs, checked that day.
Why every tutorial tells you to use GitHub
Ask an AI how to deploy and the answer often starts with push your code to GitHub. That's because the best known hosts, like Vercel, Netlify and Cloudflare Pages, like to connect to a repo and rebuild your site every time the code changes. For a developer who changes code every day, that's handy.
If you just want a link you can send to a friend or a client, it's a lot of new things at once: an account, a repository, Git, and often a terminal. None of that is what makes a site work online. What a host needs is the finished folder: the files a browser opens.
Put it online in 4 steps, no GitHub
Find the folder. The one with index.html at the top. If you see a package.json, ask your AI to run npm run build and use the dist folder it makes (some tools call it build or out). A .zip of the folder works too.
Open dropthehassle.com and press Upload (free). You don't need an account first.
Choose Drop your folder, then drag the folder onto the page. You'll be asked for an email address next. Until the site is claimed, an upload can be up to 25 MB and 1,000 files.
Claim it. Your site is already live on an address like https://yourname.dropthehassle.app. To keep it, press Claim this site right there. A site nobody claims is deleted after 7 days at the earliest. Once claimed, you can upload up to 100 MB and 5,000 files.
Does your app have its own pages, like /pricing or /contact? They open after a refresh too. If an address isn't a real file, the visitor gets your index.html and your app takes it from there.
Want your own name on it? A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year, and it's connected to your site without any DNS settings. Already have a name at another registrar? You add a single A record there and it points at your site.
Or let your AI do it, still no GitHub
If you work in Claude Code, Cursor, Codex or Windsurf, your AI can do the last step itself. Connect https://dropthehassle.com/mcp once and say put this site online with DropTheHassle. It sends the finished folder and you get a live link and a claim link back. That first deploy needs no account, no token and no GitHub. The setup per tool is in the MCP guide.
Your AI can also look up a domain name for you and send you a payment link. It never pays: that click stays yours.
Other ways to skip GitHub
You can skip GitHub on other hosts too, with a few catches. The table scrolls sideways on a small screen.
Host Without GitHub? What to know
DropTheHassle Yes, drag and drop or your AI Your email, no account first. Claim it to keep it.
Netlify Drop Yes, drag and drop Dropped without signing in, the site gets a temporary password until you claim it.
Vercel Yes, drag and drop on Vercel Drop, or the vercel command line tool Needs a Vercel account. The free Hobby plan is non-commercial only.
Cloudflare Pages Yes, upload in the dashboard Needs a login. A domain without www needs Cloudflare's nameservers.
GitHub Pages No, it is GitHub Free for a portfolio, not meant for an online business or shop. Sites max 1 GB.
Want them side by side, with what a domain costs in year two? See DropTheHassle vs Netlify, Vercel and Cloudflare Pages.
From Lovable or Bolt, without GitHub
App builders keep your code inside their own tool, so you take it out first.
Bolt. Use Export, then Download, to get a .zip of the project. No GitHub needed.
Lovable. Connecting GitHub works on every plan. On a paid plan you can also use Download codebase and skip GitHub.
Then build it once with npm run build and drop the dist folder. The full walk through is in how to move off Lovable.
What if your app has a server part?
Most AI built sites are pages that open in a browser, maybe talking to a service like Supabase for login and data. That part already runs at Supabase, so the folder is all you upload. If you start your app with something like node server.js or python app.py, part of it has to keep running.
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.
Common mistakes
Uploading the source instead of the build. A project that still needs building is refused. Run npm run build first, then drop dist.
Worrying about the .git folder. Folders and files that start with a dot, like .git or .env, are taken out of your upload before it goes live.
Sending a localhost link. localhost and your tool's preview only open on your computer. Send the dropthehassle.app link.
Forgetting your keys. If your app uses Supabase, put the keys in .env before you build, or the live site can't find your data. Only public keys belong in the browser.
Not claiming. An unclaimed site is gone after at least 7 days. The claim button is on the screen right after your upload, so press it before you close the tab.
Works on your computer but not online? The five usual causes are in My site works on my computer but not online.
Questions
How do I put my site online without GitHub?
Build it first if it has a package.json, then open dropthehassle.com, press Upload (free) and drop the folder with index.html, or the dist folder. A few minutes later it's live on a free yourname.dropthehassle.app link with HTTPS, and you never touched a repo.
Is GitHub required before my site can go live?
No. GitHub is a place to keep your code and its history, and some hosts watch it so they can rebuild your site after every change. The browser that opens your site never asks where the files came from. Your first upload here works without a GitHub account, a DropTheHassle account or a token.
Do I need a terminal?
Not for a plain HTML site: you drag the folder into your browser. If your project has a package.json, it needs one build first, and you can ask your AI to run npm run build for you. Then you drop the dist folder.
Can I deploy to Vercel without GitHub?
Yes. You can drop a folder on Vercel Drop in your browser, or upload it with Vercel's command line tool, both after you log in. Keep in mind that Vercel's free Hobby plan is for non-commercial use only.
Is this the same as Netlify Drop?
Close. Both let you drag a folder in without a repo. On Netlify Drop, a site you drop without signing in gets a temporary password until you claim it. Here an unclaimed site is public on its link right away, and gone after at least 7 days unless you claim it.
My code is already on GitHub. Can I still use this?
Yes. Keep GitHub for your history and backups, build the project, and drop the dist folder here. We don't build from your repo, so each new version is a new drop, either by you or by your AI.
How do I update my site later without GitHub?
After you claim it, press Update website in your dashboard and drop the new folder. Your current site stays live until the new one is on. Or ask your AI to do the update for you.
Can my AI do it without GitHub?
Yes. Connect https://dropthehassle.com/mcp in Claude Code, Cursor, Codex or Windsurf and say: put this site online with DropTheHassle. You get a live link and a claim link back. Your AI can never buy a domain for you: paying stays your click.
Where to go next
How do I update my site after it's online?
Where should I host my vibe-coded app?
How do I get my site online?
Let your AI deploy it with the MCP server
Website online zetten zonder hostingpakket (Dutch)
Got your folder? Then you're a few minutes away from a link you can actually send, without a repo in sight.
Put your site online free

---
# https://dropthehassle.com/guides/update-site-after-its-online

How do I update my site after it's online?
To update a site that's already online, make the change in your project (or ask your AI to), build again if it has a package.json, and drop the new folder on your site under Update website in your dashboard. Your current site stays live until the new one is on, and your link and your own domain stay exactly the same. You don't need GitHub, FTP or a new upload from scratch.
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.
Update your site in 4 steps
Make the change in your project. Edit the files, or tell your AI what should be different. Work in the same project folder you used the first time, so you change the version that's online and not an old copy.
Build again if your project needs it. Does it have a package.json? Then run npm run build, or ask your AI to. The fresh dist folder is what goes online. A plain HTML site skips this step.
Open your dashboard and press Update website. You'll see Update your site on with your address, and the note that your current site stays live until the new one is on.
Press Drop your new files and drop the folder. The whole folder, or a .zip of it. When it's on, refresh your site and you'll see the new version.
Updating from the dashboard works once your site is claimed. Still on the claim screen? Press Claim this site first, so the site is yours to change.
Change the right copy
Most update problems start before the upload. A few things to check:
Change the project, not only the built folder. If you edit a file inside dist by hand, the next npm run build writes over it. Make the change in the project and build again.
From Lovable or Bolt? Make the change there, then get the code out again (GitHub or Download codebase in Lovable, Export and Download in Bolt) and build it once more.
From ChatGPT, Claude or Gemini? Ask for the whole updated file, not just the changed lines, and save it over the old one in the same folder.
Two ways to put the new version on
After you press Update website, you pick one of two buttons.
Drop your new files. You drag the folder in yourself. Good when you've just built it, or when your AI gave you a file to save.
Let your AI do it. Once your site has its own domain, you get a code made for this one site (it works for 15 minutes). Give it to your AI in Claude Code, Cursor, Codex or Windsurf and it uploads the new version for you.
Once your AI is connected to your account (look for Connect your AI in your dashboard), you can skip the button and just say update my site on DropTheHassle with this folder. How to connect it per tool is in the MCP guide.
What changes and what stays the same
An update swaps the files of your site in one go. Visitors see the old version or the new one, never a half finished mix.
Stays the same Changes
Your link on dropthehassle.app and your own domain The pages, pictures and code in the folder you drop
HTTPS, your claim, and email on your domain Anything you removed from the folder is gone from the site
Data in Supabase or another outside service Nothing. That data stays at that service.
The new folder replaces the old one as a whole. So drop the complete site every time, not only the page you changed, or the other pages will be missing.
Changed your mind? Put the old version back
Each update keeps the version before it. If the new one isn't right, ask your connected AI to roll back your site. It asks you for a yes first, then puts the previous version back online. Rolling back again brings the newer version back, so nothing is lost by trying.
Only the one version before your last update is kept. If you want to be able to go further back, keep a copy of each folder you upload, or keep your project on GitHub.
Updating an app with a server part
The pages update here. If your app also has a part that keeps running, like an API you start with node server.js, that part updates where it runs. 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.
On a host that builds from GitHub
If your site is on a host connected to a GitHub repo, like Vercel, Netlify or Cloudflare Pages, an update usually means pushing the change to that repo, after which the host builds and publishes it. That's handy if you already work with Git. If you don't, the steps on this page get you the same result without GitHub.
Common mistakes
Dropping only the changed page. The new folder replaces the old one. Drop the whole site.
Forgetting to build. Edit, then npm run build, then drop dist. Dropping last week's dist puts last week's site back.
Editing inside dist. Your next build writes over it. Change the project instead.
Uploading as a new site. Pressing Upload (free) on the homepage gives you a second site on a new link. Use Update website on the site you already have.
Thinking it didn't work. Often it did, and your browser shows the old files. Do a hard refresh first.
Does the new version work on your computer but not online? The five usual causes are in My site works on my computer but not online.
Questions
How do I update my website?
Change the files in your project, build again if it has a package.json, and drop the new folder in your dashboard under Update website. Your current site stays live until the new one is on. The link and your own domain stay the same.
Can I update the ChatGPT-generated page later?
Yes. Ask ChatGPT for the change, save the new index.html in the same folder as before, and drop that folder under Update website. Ask for the whole file, not just the changed part, so nothing goes missing.
Will my site go offline while I update?
No. Your current site stays live until the new one is on, and then it swaps over in one go. Visitors see the old version or the new one, never a half finished mix.
Can I go back to the old version?
Yes, to the version right before your last update. Ask your connected AI to roll back your site. It asks you first, and rolling back again brings the newer version back.
Do I have to claim my site again or buy a new domain?
No. An update replaces the files, nothing else. Your claim, your link, your own domain and any email on it stay as they are, and a .com bought here stays €19 / $19 a year, including VAT in the EU, the same every year.
Can my AI update the site for me?
Yes. Once your site has its own domain, press Update website, then Let your AI do it, and you get a code made for that one site to give to your AI. If your AI is already connected to your account, you can also just ask it to update the site.
Why do I still see the old version?
Usually your browser is holding on to the old files. Do a hard refresh with Ctrl+Shift+R, or Cmd+Shift+R on a Mac. If it's still old, check that you dropped the newly built folder and not last week's copy.
Where to go next
Can I put my site online without GitHub?
How do I get my site online?
Let your AI deploy it with the MCP server
Make your site look less AI
Website online zetten zonder hostingpakket (Dutch)
Got your new version ready? Then it's one drop, and your visitors see it on the same address as before.
Open your dashboard

---
# https://dropthehassle.com/guides/gemini-canvas-website-online

Publish a Gemini Canvas app as a real website, on your own domain
A Gemini Canvas share link opens inside Gemini, not on a domain you own. Gemini does not provide a custom domain. Copy the code, save it as index.html, drop it on DropTheHassle for a free HTTPS link, then buy a .com for €19 / $19 a year, including VAT in the EU, the same every year, or point a domain you own. You already built it. Now it's on your name.
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: 26 September 2026.
What the share link does
Share and export gives a g.co/gemini/share link that opens only in Gemini. Anyone with the link can view the content. Google's Canvas help also says that for a shared app, anyone with the link can see and change the app's data. Do not use that link for something private. Export from Canvas goes to Docs, Slides, or Colab, not to a website on your name. The share link is fine for a quick demo.
In Canvas, open Code. Copy the code (or Copy contents) and save it as index.html.
If it is more than one file, ask: "Rewrite this as one self-contained index.html with all CSS and JavaScript inline."
Drop the folder at dropthehassle.com. You get https://yourname.dropthehassle.app. No card. Visitors do not need a Gemini account.
Features that call Gemini inside the app, including "add Gemini features", stop working once the file is hosted elsewhere. Data the app stored in Gemini does not come with the file.
On your own domain
A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year. No DNS edit. A domain you already own needs one A record: one line at the company where you bought the domain, set to the address shown on your screen. Press Check now. HTTPS follows. The rest, including Netlify Drop and GitHub Pages, is in the general guide.
Publish your site for free
Questions
Can Gemini Canvas use my own domain?
No. Gemini does not provide a custom domain. The share link opens inside Gemini, and anyone with the link can view the content.
How do I publish a Gemini Canvas app as a real website on my own domain?
Copy the code, save it as index.html, drop it on DropTheHassle, then buy or point a domain.
Will Gemini features keep working?
Features that call Gemini inside the app stop working once the file is hosted elsewhere. Data the app stored in Gemini does not come with the file.

---
# https://dropthehassle.com/guides/lovable-custom-domain-not-working

Lovable custom domain not working
If your Lovable domain is stuck, open Project, Settings, Domains and read the status. Setting up means SSL is still issuing, a Cloudflare 1001 or 1003 means the orange cloud is on, www stays dark when that hostname was not added, and Offline means the DNS records no longer point at the project. The checks below are from Lovable's custom domain docs.
Short answer: If your Lovable custom domain isn't working, it's almost always one of four things: SSL still pending, Cloudflare's orange cloud (proxy) switched on, a missing www record, or the domain showing Offline. Each has a fix below. If you'd rather not deal with DNS at all, you can publish the built app on DropTheHassle and buy the .com with the site: then there are no DNS settings to edit. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
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: 30 September 2026. Steps were checked against Lovable's custom domain page on 27 September 2026.
SSL pending, stalled, or failed
Status Setting up: verification is done and the certificate is being issued. Lovable says the browser can show a security warning until then. Wait for Live before you send people there.
Status Stalled or Failed: click Retry. You do not have to remove the domain and add it again.
If the domain has CAA records, those records must allow Lovable to issue the certificate. Lovable's page names the issuers to allow, including ssl.com.
Do not upload a certificate at your registrar. Lovable issues its own. If it still has not been issued after 72 hours, Lovable says to contact Lovable Support.
While status is Verifying, leave the A record and the TXT record exactly as Lovable showed them. The docs say that changing the A record before verification finishes blocks the certificate. The A record they document points at 185.158.133.1. The TXT host is _lovable, and the value starts with lovable_verify=. An old AAAA record can send traffic elsewhere. Remove it for the hostname you are connecting.
Cloudflare error, orange cloud
Lovable says errors 1001 and 1003 come from Cloudflare's proxy, not from Lovable. In the DNS settings for that hostname, set the record to DNS only (gray cloud), not Proxied (orange cloud). Wait a few minutes and open the site again.
Use the orange cloud only if you meant to. Lovable has a separate option, Uses Cloudflare or similar proxy. In that mode Lovable gives you a CNAME to your lovable.app URL instead of the A record, and it does not ask for the verification TXT. You maintain that proxy yourself. The docs are on the same custom domain page.
www was not added
A domain bought through Lovable gets the root and www set up automatically. Both show as their own rows.
A domain you bought somewhere else connects www only when Redirect www to the root stays on. That is the default. Lovable then lists www separately.
If you turned that option off, www shows as Not connected after the root is Live. Click Connect next to it.
The domain says Offline
Lovable's status table says Offline means the domain was Live and the DNS records are no longer valid. The name is not pointing at the project. Click Recover, read the records on the screen, and put those records back at your DNS host.
Removed is different. Lovable says the domain was removed because it was added to another project, or DNS verification never finished. Click Reconnect.
Custom domains on Lovable are on paid plans, from the same docs. Connecting the name is a separate job from publishing the project: the domain will not serve the app until the project is published.
Entri or manual records
Lovable offers two ways to connect a domain that you did not buy there. Both still ask you to prove you own it.
Automatic setup with Entri. Lovable detects the DNS host. You log in and let Entri write the records.
Manual setup. Pick the host from the list, or choose manual setup if it is missing. Copy the A record and the TXT record and paste them at the registrar yourself.
The host name on the A record depends on the registrar. Lovable says it may be @, blank, the domain name, or the subdomain label. DNS can take a while. Lovable says up to 72 hours, and that most updates show within a few hours.
If you would rather not debug DNS
Publish the built folder on DropTheHassle instead. You get a free yourname.dropthehassle.app link on HTTPS, with no card. A domain you already own connects for free after one A record, to the address shown on your screen. A .com bought in the dashboard is €19 / $19 a year, including VAT in the EU, the same every year, and that purchase needs no DNS edit. A mailbox is optional: €5 / $5 a month, including VAT in the EU, for the first inbox, €3 / $3 a month per extra inbox.
The how-to, including the Lovable export, is Put your Lovable app on your own domain, step by step. Your AI can publish the folder. It can never spend your money.
Publish your site for free
Questions
Why is my Lovable domain not working?
Usually SSL is still pending, Cloudflare's proxy (orange cloud) is on, the www record is missing, or the domain shows Offline. Fix the one that matches, or publish the built folder elsewhere and skip DNS.
Why is SSL stuck?
Setting up means the certificate is still being issued. Stalled or Failed means click Retry. If CAA records are in the way, allow the issuers Lovable lists. After 72 hours, contact Lovable Support. Source: Lovable custom domains.
What is Cloudflare error 1001 or 1003?
Lovable says it is the proxy. Set the record to DNS only, the gray cloud.
Why does www not load?
For a domain bought outside Lovable, www is a second hostname. Leave the redirect on, or click Connect next to www after the root is Live.
What does Offline mean?
The DNS records stopped pointing at the project. Click Recover and put them back.
Entri or manual?
Entri writes the records after you log into the DNS host. Manual means you paste the A record and the TXT record yourself.
Can I skip this?
Yes. Publish the built folder here. Press Upload (free), then Drop your folder. You do not sign in first. A .com is €19 / $19 a year, including VAT in the EU, the same every year, with no DNS edit. Connecting a domain you already own is free.
Related
Put your Lovable app on your own domain, step by step
Downgrading Lovable: does your domain keep working?
Netlify vs Vercel vs Cloudflare Pages, with renewal
Any site you already built
Works locally, not online? Here's why

---
# https://dropthehassle.com/guides/make-website-look-less-ai

Make your AI-built website look less AI
Sites built with Lovable, Bolt, v0, Claude Code or Cursor tend to arrive with the same look: a purple-to-indigo gradient, Inter in one weight, everything centered, three rounded cards with emoji, and a fade-up on every section. None of it is broken. It reads as AI because it is the default, and because nothing on the page could only belong to you. Below are 12 fixes, each with the default and a better version, and the file that makes your AI keep them.
Short answer: give the AI decisions instead of adjectives. Pick 4 to 6 colors with one accent, one or two typefaces chosen on purpose, two corner radii, and left-aligned text. Replace generic copy and icons with things only your business has: real photos, prices, opening hours, names. Write those rules into a file your tool reads on every edit (project knowledge in Lovable, CLAUDE.md or AGENTS.md, a Cursor rule), then check the result with a detector.
Last updated: 1 October 2026. Every tool, command and link on this page was opened or run on that date.
Default
yourbakery.lovable.app
✨ Artisan freshness
Elevate your mornings with artisan bread
Cutting-edge baking, seamlessly delivered.
Get started →Learn more
🍞Fresh
🚀Fast
💜Loved
Decided
yourbakery.com
Sourdough out of the oven at 6:00.
Order by 21:00 and pick it up tomorrow from 7:00.
Order for tomorrow
Rye sourdough5.20
Seeded loaf5.80
Butter croissant2.40
Open Tue to Sat, 7:00 to 15:00Baked on site
Illustration. Kade Bakery is made up. Left: the kind of page a one-line prompt like "a homepage for a bakery" tends to produce. Right: the same business after the fixes below: left-aligned, one accent color, a serif headline, real prices and opening hours where the feature cards were, and its own domain.
On this page
What makes a site look AI-made
12 fixes, before and after
Make your AI keep the decisions
Check your site for AI tells
Put it on your own name
Questions
What makes a site look AI-made
This list is not our opinion alone. Anthropic's own frontend-design skill describes the traits AI-generated design clusters around, and Impeccable turns many of them into detector rules. The ones you see most on vibe-coded sites:
Purple or violet gradients as the background or the accent.
Inter, or another default sans, for everything, often in one weight.
Every block centered, every section the same height and padding.
The template order: hero, logo strip, three feature cards, testimonials, pricing, call to action.
Identical rounded cards with the same soft grey shadow, and one border radius on everything.
Gradient text, or one word of the headline in a different color.
A tracked-out ALL-CAPS label above every heading, 01 / 02 / 03 on content that is not a sequence, and an arrow on every button.
Emoji or a rounded icon tile standing in for pictures.
Copy that would fit any company: "elevate", "cutting-edge", "seamless".
A fade-and-slide-up on every section as you scroll.
Any one of these is fine when you chose it. A page with six of them reads as a first draft.
12 fixes, before and after
1. One accent color, no purple gradient
Indigo and violet are what a model reaches for when nobody gave it a color. Take a palette from your subject instead: a bakery's crust, a climbing gym's chalk and rope, a law firm's navy. Write it down as named hex values so the AI cannot drift back.
Before
.hero {
background: linear-gradient(135deg, #667eea, #764ba2);
}
.btn { background: #7c3aed; }
After
:root {
--ink: #1d1b16;
--paper: #ffffff;
--accent: #6b3f14; /* the only accent */
--line: #e7e3da;
--muted: #4a463e;
}
.hero { background: var(--paper); color: var(--ink); }
.btn { background: var(--accent); color: #fff; }
Keep the accent for the one thing you want clicked. When everything is colored, nothing stands out.
2. Choose the typeface on purpose
Inter is a good font. It is also the font of a great many starter templates and generated sites, so on its own it says nothing about you. Anthropic's skill asks for one or two families, clearly different if two, with a real type scale and lines under about 80 characters. A serif for headings and a plain sans for body text is an easy start.
Before
body { font-family: Inter, sans-serif; }
h1, h2, h3, p { font-weight: 600; }
After
h1, h2 {
font-family: "Iowan Old Style", Palatino, Georgia, serif;
font-weight: 600;
}
body { font: 400 17px/1.55 system-ui, sans-serif; }
h1 { font-size: 2.5rem; line-height: 1.1; }
h2 { font-size: 1.6rem; }
p { max-width: 65ch; }
If you pick a web font, host the files yourself next to the site so the page does not wait on another server.
3. Stop centering everything
Centered text gets hard to read after two lines, and a page where every block is centered gives the eye no edge to follow. Left-align body text and most headings. Center only a short block with one message, like the final call to action.
Before
section { text-align: center; }
After
section { text-align: left; max-width: 68rem; }
.final-cta { text-align: center; }
4. Break the template order and move proof up
Hero, logos, three features, testimonials, pricing, call to action is the order a model reaches for whatever the business is. Ask what a visitor needs to decide, and put that near the top: the product itself, a screenshot of the app working, the menu with prices, the opening hours, the area you serve. Cut sections that do not help that decision.
Before Hero, logo strip, three feature cards, three testimonials, pricing table, call to action.
After Headline with the menu and prices beside it, opening hours and pickup address, photos of today's bread, one order button.
5. Write copy only you could write
Cover your logo and read the headline. If a competitor could use it unchanged, rewrite it. Name the thing, the place, the price, the time.
Before Elevate your mornings with artisan bread. Cutting-edge freshness, seamlessly delivered.
After Sourdough out of the oven at 6:00. Order by 21:00 and pick it up tomorrow.
6. Drop gradient text and the one colored word
A gradient-filled heading and a single word in the accent color are on both Anthropic's and Impeccable's lists of tells. Let size and weight carry the headline. It fixes a contrast problem too: gradient text is often hard to read along part of its length.
Before
h1 span {
background: linear-gradient(90deg, #a855f7, #3b82f6);
-webkit-background-clip: text;
color: transparent;
}
After
h1 {
color: var(--ink);
font-size: 2.5rem;
}
/* no span, no gradient */
7. Two corner radii, not 24px on everything
Generated pages often put one large radius on cards, buttons, images and inputs alike. Pick two values, small for controls and a little larger for containers. Keep an inner radius smaller than the outer one so the curves line up. Vercel's Web Interface Guidelines call this nested radii.
Before
.card, .btn, img, input {
border-radius: 24px;
}
After
:root { --r-sm: 6px; --r-md: 12px; }
.btn, input { border-radius: var(--r-sm); }
.card { border-radius: var(--r-md); padding: 6px; }
.card img { border-radius: var(--r-sm); }
8. Borders and real shadows instead of one soft grey
The default is one shadow, 0 4px 6px rgba(0,0,0,.1), under every card. On a light page a 1px border often does the job alone. When something should float, layer a tight shadow with a wide soft one, as Vercel's guidelines suggest, and tint it toward your palette.
Before
.card {
box-shadow: 0 4px 6px rgba(0,0,0,.1);
}
After
.card { border: 1px solid var(--line); }
.popover {
box-shadow: 0 1px 2px rgba(29,27,22,.08),
0 8px 24px rgba(29,27,22,.06);
}
9. Real pictures, and fewer icons
Emoji in headings, a rounded icon tile above every feature and abstract gradient blobs fill space without telling anyone anything. One photo of your actual product, shop or team does more than six icons. If you use icons, use one set at one stroke weight, only where they help someone scan. Give every image a width, a height and real alt text so the page does not jump while it loads.
Before
<h3>🚀 Fast delivery</h3>
After
<img src="/img/todays-bread.webp"
width="800" height="600"
alt="Rye and seeded loaves on the shop counter">
<h3>Delivered before 8:00</h3>
10. Cut the template chrome
Three small habits give a page away: a tracked-out ALL-CAPS label above every heading, numbered markers on things that are not steps, and an arrow added to every link and button. Keep a label only when it carries information, keep numbers for real sequences, and let the button say what happens when you press it.
Before
<p class="eyebrow">WHY CHOOSE US</p>
<h2>Features</h2>
<a class="btn">Get started →</a>
After
<h2>Order by 21:00, pick up from 7:00</h2>
<a class="btn" href="/order">Order for tomorrow</a>
11. One moment of motion, not a fade on every section
Anthropic's skill calls fade-and-slide-up entrances on each section the generic default. Emil Kowalski's Agents with Taste lists the rules agents tend to miss: ease-out for things that enter, interface animation under 300ms, start a scale at 0.95 instead of 0, and a small press effect on buttons. Animate what responds to the visitor, and respect reduced motion.
Before
section {
animation: fadeUp 0.8s ease-in both;
}
After
.btn:active { transform: scale(0.97); }
.menu { transition: transform 200ms ease-out,
opacity 200ms ease-out; }
@media (prefers-reduced-motion: reduce) {
.menu { transition: none; }
}
12. Finish the details people notice when they are missing
A page title and description written for this page, not the template's Vite + React.
A favicon and a share image, so a link in WhatsApp or Slack shows your name and a picture.
A visible focus ring for keyboard users, and tap targets of at least 44px on phones.
Body text of 16px or more, with a contrast of at least 4.5:1.
A real 404 page, and footer links that go somewhere.
Your own domain. An address like yourproject.lovable.app tells visitors the site is still a project.
Make your AI keep the decisions
A fix you prompt once is gone three prompts later. Put the rules where your tool reads them on every request.
Tool Where the rules go
Lovable Project settings, Knowledge (up to 10,000 characters), or an AGENTS.md at the root of the repository, which Lovable's docs say it always reads.
Claude Code CLAUDE.md in the project, or a skill in .claude/skills/.
Cursor AGENTS.md, a rule in .cursor/rules/, or a skill in .cursor/skills/.
Codex AGENTS.md, or a skill in .agents/skills/.
Windsurf A rule, AGENTS.md, or a skill in .windsurf/skills/.
Bolt, v0, others Paste the block into the first message of a redesign chat.
A starting file. Change the values to yours; the point is that every line is a decision the AI can check, not an adjective like "modern" or "clean".
# Design rules (read before any UI change)
Palette, use only these:
ink #1d1b16, paper #ffffff, accent #6b3f14, line #e7e3da, muted #4a463e
The accent is for the main action only. No gradients. No purple.
Type:
Headings: "Iowan Old Style", Palatino, Georgia, serif, weight 600
Body: system-ui, 17px, lines under 70 characters
Sizes: 40 / 26 / 20 / 17 px
Shape:
Radius 6px on controls, 12px on containers. Nothing else.
Borders 1px #e7e3da. Shadows only on things that float.
Layout:
Left-align text. Center only the final call to action.
Put the menu with prices and the opening hours near the top.
Never:
gradient text, emoji as icons, ALL-CAPS labels above headings,
01 / 02 / 03 on things that are not steps, arrows on every button,
a fade-in on every section, "elevate", "seamless", "cutting-edge".
Motion:
Only in response to the visitor. ease-out, under 300ms.
Respect prefers-reduced-motion.
The redesign prompt
Before Make it look more modern and professional.
After Restyle the homepage using the rules in AGENTS.md. Change only styling and layout. Do not change text, routes, data or functionality. Start with the hero, then stop so I can look before you do the next section.
Screenshots help more than words. Attach one or two sites you like and say which part to take from each: the type, the spacing, the way the menu sits. A design skill gives the AI more of this judgment up front; the ones worth installing are in design skills for Claude Code, Cursor and Codex.
Check your site for AI tells
Impeccable's command line tool runs its detector rules without an AI model or an API key. Point it at a file, a folder or a live address:
npx impeccable detect index.html
npx impeccable detect https://yourname.com
We ran it (version 4.1.0) on a test page with a purple gradient, Inter, gradient text, emoji cards and buzzword copy. It reported 7 issues: the purple palette, Inter, the gradient text twice, the buzzwords, and low contrast on the purple background twice. It did not flag the emoji. The package asks for Node 22.18 or newer. For a review against accessibility and interface rules, have your agent run Vercel's web-design-guidelines skill.
When it looks right, put it on your own name
A redesign is a good moment to move off the builder's address. On DropTheHassle you publish the built folder (the dist folder after npm run build, or any folder with an index.html) and get a free yourname.dropthehassle.app link on HTTPS, with no account and no card. Claim it and it stays. An unclaimed site is kept for at least 7 days. A .com bought there is €19 / $19 a year, including VAT in the EU, the same every year, and it needs no DNS edit. Email at the same name is optional.
Your AI can publish it for you through the MCP server. It can never spend your money. Steps per tool: Lovable, Claude Code, Cursor, Bolt, or any HTML file or zip.
Publish your site for free
Questions
Why do AI-built websites all look the same?
Without specific rules, a model falls back to the patterns that dominate the templates it learned from: purple gradients, Inter, centered heroes and three rounded feature cards. Every vague prompt lands on the same defaults.
How do I make my Lovable site look less AI?
Put your palette, fonts, corner radii and a list of things to avoid in Project settings, Knowledge, or in an AGENTS.md at the root of the repository. Then ask for a styling-only redesign, one section at a time, with screenshots of sites you like as reference.
Is it bad to use Inter?
No. Inter is well made and easy to read. It reads as a default because so many generated sites use it. If you keep it, make the rest of the page specific: your colors, your photos, your copy.
What prompt makes a website look less AI?
Replace adjectives with decisions. Name the colors as hex values, the typefaces, two corner radii, the alignment and a list of things to avoid, then say: change only styling and layout, do not change text or functionality.
Can a tool check my site for AI design tells?
Yes. npx impeccable detect runs Impeccable's detector rules on a file, a folder or a live address without an AI model. It flags things like purple palettes, gradient text, overused fonts and low contrast.
Does my own domain make the site look more professional?
It removes one more sign of a draft. A builder address like yourproject.lovable.app says the site is still a project. On DropTheHassle a .com is €19 / $19 a year, including VAT in the EU, the same every year, with no DNS edit.
Related
Design skills for Claude Code, Cursor and Codex
Put your Lovable app on your own domain, step by step
Put your Claude Code website online, then on your own domain
Made a website with ChatGPT or Claude? Put it online

---
# https://dropthehassle.com/guides/design-skills-claude-code-cursor

Design skills for Claude Code, Cursor and Codex: which to install
A skill is a folder with a SKILL.md file. Your agent reads its short description, and loads the full instructions when a task matches. Design skills are the cheapest way to stop Claude Code, Cursor, Codex or Windsurf from shipping the same purple-gradient page as everyone else. Here are the six worth knowing, what each one is for, and install commands we ran ourselves.
Short answer: start with Anthropic's frontend-design for a new page. Add Emil Kowalski's emil-design-eng when motion and small interactions matter. For a site that already exists, use Impeccable or Taste Skill's redesign skill, and run Vercel's web-design-guidelines as the last review before launch. Most of them install with npx skills add, which writes to the folder each agent reads.
Last updated: 1 October 2026. Every repository was opened and every install command below was run on that date, with skills CLI 1.7.0.
On this page
Which skill for which job
The six skills
Where each tool looks for skills
How to prompt with a design skill
Read before you install
Questions
Which skill for which job
Job Skill
A new landing page or section frontend-design (Anthropic)
Animations, hovers, drawers, toasts emil-design-eng (Emil Kowalski)
An existing site that looks vibe coded Impeccable, or Taste Skill's redesign-existing-projects
More visual personality Taste Skill
A review before launch web-design-guidelines (Vercel), plus npx impeccable detect
Browsing more design skills UI Skills
Keep the stack small. Two skills that both try to set the visual direction will pull against each other. One for direction and one for review is a good pair.
The six skills
Most skills install with the open skills CLI. Run it in your project folder. Add -a claude-code, -a cursor or -a codex to choose the agent, or leave it out and pick from the list it shows.
npx skills add <owner/repo> --skill <skill-name>
frontend-design
By Anthropic. anthropics/skills, Apache 2.0. Also in Claude Code's official plugin marketplace.
The baseline most other design skills start from. It tells the agent to ground the design in the subject, then work in two passes: first a compact plan with 4 to 6 named hex colors, the typefaces and their roles, and a layout sketch; then a check of that plan against generic defaults before any code is written. It names the looks AI design keeps landing on, such as the SaaS card kit and an ALL-CAPS label above every heading, and sets a quality floor: responsive to mobile, visible keyboard focus, reduced motion respected.
In Claude Code:
/plugin install frontend-design@claude-plugins-official
In Cursor, Codex and other agents:
npx skills add anthropics/skills --skill frontend-design
In Lovable (workspace owners and admins): Workspace settings, Skills, Add, Import from GitHub, and paste https://github.com/anthropics/skills/tree/main/skills/frontend-design. Lovable's docs accept a link to a folder that holds a SKILL.md.
emil-design-eng
By Emil Kowalski, design engineer and author of Sonner. emilkowalski/skills, MIT.
In his words, "mostly animation, but also some design advice". It gives the agent strict rules where it would otherwise guess: which easing for which movement, how long an animation should take, when not to animate at all, and how components should feel. When it reviews code it has to answer in a table with Before, After and Why columns, so you see each change and the reason.
npx skills add emilkowalski/skills --skill emil-design-eng
The same repository has narrower skills: review-animations, improve-animations, find-animation-opportunities, animation-vocabulary, apple-design, pick-ui-library, prototype and mobile-native. Run npx skills add emilkowalski/skills without --skill to choose from the list. To see the thinking behind them, read Agents with Taste and 7 practical animation tips, or his course at animations.dev. His drawer component Vaul is still on GitHub, but its README says it is unmaintained.
Impeccable
By Paul Bakaus. pbakaus/impeccable, Apache 2.0. Docs at impeccable.style.
Its README says it started from Anthropic's frontend-design and grew from there: one skill with 24 commands and 61 detector rules. /impeccable init writes a PRODUCT.md with your audience, purpose and voice, so later commands know what the site is for. Then you work with commands such as critique, audit, polish, typeset, layout, bolder and quieter. It suits a site that already exists and that you keep improving.
npx impeccable install
# then, inside your agent:
/impeccable init
The installer can also add a hook that runs the detector whenever the agent edits a UI file, in Claude Code, Cursor, Codex, GitHub Copilot and Grok Build. The detector runs on its own too, with no model and no API key: npx impeccable detect https://yourname.com. The package asks for Node 22.18 or newer.
Taste Skill
By Leonxlnx. Leonxlnx/taste-skill, MIT.
A set of anti-slop skills. The default, design-taste-frontend, reads the brief and tunes three dials: layout variance, motion intensity and visual density. The README marks this v2 as experimental. For a site you already have, redesign-existing-projects audits the current UI first, then fixes layout, spacing, hierarchy and styling. There are style variants (minimalist-ui, industrial-brutalist-ui, high-end-visual-design) and a stricter gpt-taste for GPT and Codex.
npx skills add https://github.com/Leonxlnx/taste-skill --skill design-taste-frontend
npx skills add https://github.com/Leonxlnx/taste-skill --skill redesign-existing-projects
web-design-guidelines
By Vercel. vercel-labs/agent-skills, based on the Web Interface Guidelines.
A reviewer, not a stylist. Ask "review my UI" and it checks your code against the guidelines, which its README says cover more than 100 rules on accessibility, performance and UX: focus rings, hit targets, contrast, image sizes that prevent layout shift, prefers-reduced-motion. It fetches the latest guidelines from Vercel each time it runs, so the agent needs network access.
npx skills add https://github.com/vercel-labs/agent-skills --skill web-design-guidelines
UI Skills
By ibelick. ibelick/ui-skills, MIT. Site: ui-skills.com.
A registry of design engineering skills you can browse from the terminal or from your agent. It also connects as an MCP server at https://www.ui-skills.com/mcp, with the tools list_skills and get_skill.
npx ui-skills list --category motion
npx ui-skills get baseline-ui
Where each tool looks for skills
Skills follow one open format, so the same folder works in several tools. If you install by hand, copy the skill folder (the one with SKILL.md in it) here:
Tool Project folder Use it
Claude Code .claude/skills/, or ~/.claude/skills/ for every project Automatic, or type /skill-name. Docs
Cursor .cursor/skills/ or .agents/skills/; it also loads .claude/skills/ Automatic, or type / in Agent chat. Docs
Codex .agents/skills/, or ~/.agents/skills/ Automatic, or /skills and $skill-name. Docs
Windsurf .windsurf/skills/ (still read; the docs now name .devin/skills/) or .agents/skills/ Automatic, or @skill-name. Docs
Lovable Workspace settings, Skills: import from GitHub or upload a ZIP Automatic, or type / in chat. Docs
When we ran npx skills add anthropics/skills --skill frontend-design -a claude-code -a cursor -a codex, the CLI put one copy in .agents/skills/frontend-design for Cursor and Codex and linked it into .claude/skills/ for Claude Code. Commit the folder and everyone on the project gets the same skills.
How to prompt with a design skill
A skill does not replace a brief. It works best when the prompt gives it a subject, an audience and one job, and asks for the plan before the code, which is how Anthropic's skill is meant to be used.
Before Build a landing page for my climbing gym. Make it modern and clean.
After Use the frontend-design skill. Landing page for a bouldering gym in an old warehouse. Visitors are beginners deciding whether to book a first session. Before you code, write the plan: 4 to 6 named hex colors, the typefaces and their roles, a layout sketch. Change anything in the plan that would fit every other gym site. Then build it.
Then make the result stick. Copy the colors, type and radii the plan settled on into CLAUDE.md, AGENTS.md or your Lovable knowledge, with a short list of things to never do. Our guide Make your AI-built website look less AI has 12 before and after fixes and a design rules file you can start from.
Read before you install
A skill is instructions your agent follows, and some come with scripts or hooks. The skills CLI ends every install with: "Review skills before use; they run with full agent permissions."
Open the SKILL.md on GitHub first. They are plain Markdown and take a few minutes to read.
Install into the project before you install for every project, and try the same prompt with and without the skill.
Impeccable's installer offers to add an edit hook. Say no if you only want the commands.
When the design is done, publish it
Once it looks right, ask the same agent to put it online. DropTheHassle has an MCP server, so Claude Code, Cursor, Codex or Windsurf can publish the built folder for you and hand you a claim link. You get a free yourname.dropthehassle.app link on HTTPS with no account and no card. A .com is €19 / $19 a year, including VAT in the EU, the same every year, with no DNS edit. Your AI can publish. It can never spend your money.
claude mcp add dropthehassle -- npx -y dropthehassle-mcp@latest
Setup for every tool is in Is there an MCP server to publish my site and manage the domain?, with steps for Claude Code, Cursor, Codex and Windsurf.
Publish your site for free
Questions
What is the Anthropic frontend-design skill?
A SKILL.md from Anthropic that makes the agent commit to a distinct visual direction: plan colors, type and layout first, check the plan against generic AI defaults, then build. It is in the anthropics/skills repository and in Claude Code's official plugin marketplace.
How do I install the frontend-design skill in Claude Code?
Run /plugin install frontend-design@claude-plugins-official inside Claude Code, or run npx skills add anthropics/skills --skill frontend-design in your project folder.
Do Claude skills work in Cursor and Codex?
Yes. Skills follow the open Agent Skills format. Cursor reads .cursor/skills/ and .agents/skills/ and also loads .claude/skills/. Codex reads .agents/skills/. The skills CLI writes to the right folder with -a cursor or -a codex.
What is Emil Kowalski's design skill?
emil-design-eng, from the emilkowalski/skills repository. In his words it is mostly animation, with some design advice: easing, duration, when not to animate, and how components should feel. Install it with npx skills add emilkowalski/skills --skill emil-design-eng.
Should I use Impeccable or Taste Skill?
Impeccable is built around critique, audit and a detector you can run without a model, which suits a site you keep improving. Taste Skill pushes visual personality with dials for layout variance, motion and density. Either can sit next to Anthropic's frontend-design.
Do design skills cost money?
The skills on this page are free to install from public GitHub repositories. You pay only for the agent you already use. Read each SKILL.md before you install it, because skills run with your agent's permissions.
Related
Make your AI-built website look less AI
Is there an MCP server to publish my site and manage the domain?
Put your Claude Code website online, then on your own domain
Put your Cursor website online, then on your own domain

---
# https://dropthehassle.com/compare/dropthehassle-vs-netlify-vercel-cloudflare

Netlify vs Vercel vs Cloudflare Pages for a small static site
Buy the .com at DropTheHassle if you want €19 / $19 a year, including VAT in the EU, the same every year, and no DNS edit; use Netlify, Vercel, or Cloudflare Pages when the site needs a team or very high traffic, or when you are fine editing DNS, and check their current .com price because the pages linked below do not publish one.
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: 30 September 2026. Every competitor claim below was checked against the linked page on that date. Where that page has no .com number, the cell says check current price.
Comparison
The table scrolls sideways on a narrow screen. Each competitor cell links to the page the claim came from.
Question
DropTheHassle
Netlify
Vercel
Cloudflare Pages
Free tier with a custom domain
Free name.dropthehassle.app link with HTTPS. Connecting a domain you own is free.
Yes. Free plan lists custom domains with SSL. 300 credits. A production deploy is 15 credits. source
Yes on Hobby. Up to 50 domains per project. HTTPS included. source
Yes. Up to 100 custom domains per project on Free. source
Commercial use on the free tier
The free link is not described as personal-only.
Listed for an individual. No non-commercial ban on the pricing page. source
No. Hobby is personal, non-commercial use only. source
The Free limits page states no personal-only rule. source
Drag and drop, no git
Yes. Drop the folder. No card for the free link.
Yes. Netlify Drop, no account, claim later. source
Not described on the Hobby or pricing pages. Hobby pricing
Yes, after login. Dashboard drag-and-drop or Wrangler. Not anonymous. source
Buy a domain in the product
Yes. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
Yes. Buying it creates the DNS zone. No .com price on the page. source
Yes. Nameservers are set for you. No .com price on the page. source
Yes, Cloudflare Registrar. No .com price on the page. source
.com, first year
€19 / $19 a year, including VAT in the EU, the same every year.
Check current price. source
Check current price. The free first year is Pro only, and .com is not in the eligible list. source
Check current price. At or below registry and ICANN cost. source
.com, renewal
€19 / $19 a year, including VAT in the EU, the same every year.
Check current price. Netlify emails the renewal cost. source
Check current price. After a free first year, renewal is "the standard rate". source
Check current price. Renewal is at or below registry and ICANN cost. source
DNS you edit yourself
None if you buy the name here. One A record if it stays at your registrar.
None if you buy it there. If you bring a name, you edit DNS. buy bring
None if you buy it there. Otherwise you edit DNS at your registrar. source
Apex: point nameservers at Cloudflare. Subdomain: a CNAME you add yourself. source
Email or mailbox
€5 / $5 a month, including VAT in the EU, for the first inbox, €3 / $3 a month per extra inbox.
Not listed on the pricing or domain pages. pricing domains
No mail service for domains bought or transferred there. source
Not listed on the Pages limits or Registrar pages. limits registrar
Agent or MCP deploy
Yes. A first deploy needs no token and returns a claim link, on the remote MCP and on stdio (npx -y dropthehassle-mcp@latest, 0.4.2).
Yes. Agents deploy from netlify.ai, including with no account. Drop
Yes. Vercel documents MCP tools, including purchases. source
Dashboard or Wrangler after login. No agent pay step is described. source
Can the agent spend money?
No. Your AI can publish. It can never spend your money.
The agent page describes deploy. It does not say the agent can pay. source
Yes, after you confirm. The charge hits the team card and is non-refundable. changelog tools
Not stated. The upload docs do not say an agent can pay. source
Netlify Drop
Netlify's own history of Drop says you drag a folder onto netlify.com/drop and get a live URL with no account. Claim the site if you want to keep it. Otherwise it expires. The same post says that this summer Drop can connect a custom domain, you can redeploy a drop, and you can drop a project that needs a build so Netlify builds and deploys it. Agent instructions are at netlify.ai. Source: Thirteen years of Netlify Drop.
Choose DropTheHassle if
The site is already built files (a folder with index.html). You want the renewal price in writing: a .com is €19 / $19 a year, including VAT in the EU, the same every year. You do not want to edit DNS, or you already own the name and one A record is enough. You want a mailbox at that name. You want an agent that can publish and cannot spend.
DropTheHassle doesn't run servers itself: host the server part on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card. For a team deploy pipeline, the others fit better. We publish the folder.
Looking at app builders instead of hosts? Retool, Taskade, Boonful, and my-app.engineer are a different comparison.
Need a host that runs Node? See GoDaddy Node.js Hosting vs DropTheHassle →
Publish your site for free
Choose Netlify if
You want the anonymous drag-and-drop, or you want Netlify to build the project and run functions. The Free plan is $0 and lists custom domains with SSL, with a 300 credit limit (pricing). You are fine editing DNS when the domain stays at your registrar (bring a domain). Check the current .com price before you buy it there. A mailbox is not listed on those pages.
Choose Vercel if
You are shipping a framework app, you want serverless functions, or you are a team. Budget for Pro if the site is commercial: Hobby is personal, non-commercial use only (Hobby). Pro on the pricing page is $20 a month (pricing). A domain bought at Vercel needs no DNS records from you, and Vercel does not provide a mailbox (domains). Their agent can spend: purchase tools charge the card after you confirm (MCP tools).
Choose Cloudflare Pages if
The site fits Pages, you expect a lot of files or traffic inside the Free limits, and you are fine pointing nameservers at Cloudflare for an apex domain (custom domains, limits). Registrar pricing is at cost, and the product page does not list a .com number, so check the current price (registrar). Drag-and-drop is in the dashboard after login, not an anonymous drop (Direct Upload).
Questions
Which is cheapest for a small static site, including renewal?
If you buy the .com here, it is €19 / $19 a year, including VAT in the EU, the same every year, and hosting the built files on the free link costs nothing. If you already own the domain and you will edit DNS, Netlify, Vercel, and Cloudflare Pages can host those files on a free plan, inside the limits linked above. Vercel Hobby cannot be the commercial plan. None of those three publish a .com renewal number on the pages checked here, so check the current price before you treat them as cheaper.
When is Netlify, Vercel, or Cloudflare the better choice?
When you need a framework build, a team, or very high traffic, or when editing DNS does not bother you. DropTheHassle is for the built folder, the name, and the mailbox. Server parts connect in the Backend card.
Does Netlify Drop include a custom domain?
The Drop post says that this summer you can connect a custom domain, redeploy, and drop a project that needs a build. The no-account drag-and-drop is still there. Claim the site if you want to keep it.
Can my AI spend money?
Not here. Your AI can publish. It can never spend your money. On Vercel, the MCP purchase tools can charge the team after you confirm. Netlify's agent page describes deploy and does not say the agent can pay.
What does the .com cost next year?
At DropTheHassle, €19 / $19 a year, including VAT in the EU, the same every year. Elsewhere, check the current price on the registrar page linked in the table.
Related
Put a site you already built online
Put a Lovable app on your own domain
Move your app off Lovable or Replit
Lovable custom domain not working
Connect a custom domain to a Bolt.new site
Put a Cursor site on a custom domain
Deploy a Claude Code website

---
# https://dropthehassle.com/compare/ai-app-builders-with-custom-domains

AI app builders with your own domain, compared
Four tools that build or publish apps, next to DropTheHassle. They solve different problems. DropTheHassle is for one thing: getting the site your AI already built live on your own domain.
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.
Checked 30 September 2026. Prices and features come from each company's own site. Follow the links to confirm.
At a glance
The table scrolls sideways on a narrow screen. Each competitor cell links to the page the claim came from.
What it is
Own domain
Price (from their site)
Agents / MCP
DropTheHassle
Hosting and a domain for sites your AI built
Buy a .com here (no DNS edits) or point yours with one A record
Free dropthehassle.app link. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
npx -y dropthehassle@latest deploy or MCP https://dropthehassle.com/mcp, no account needed
Retool CLI
Build and publish Retool apps from the command line (public beta). changelog
A CNAME for a subdomain. An apex domain works too, with A records. docs
Team: $10/mo per builder billed annually or $12 monthly, plus $5 or $7 per internal user. Business: $50 or $65 per builder, plus $15 or $18 per internal user. pricing
Works "with the help of your chosen code development agent harness, like Claude Code or Codex" (Retool's words). Retool MCP too. docs
Taskade Genesis
Prompt-to-app builder inside Taskade. FAQ
From Business. Buy in Taskade or connect your own. FAQ
Business $25/mo billed annually. billing
Hosted MCP on paid plans. docs
Boonful
Build and sell apps, ebooks, and courses. studio
Not stated on their site
$29.95/mo plus 5% per sale plus Stripe fees. pricing
Connector for Claude and ChatGPT. You publish. studio
my-app.engineer
AI agents build apps and deploy them to Kubernetes under your account. By default an app runs in your own isolated space on their shared cluster. A dedicated cluster is Pro only. site
Point your DNS. The certificate is issued. site
Free (1 app). Pro €19/mo, with the dedicated cluster. site
Built-in agents. External MCP is not stated. site
Pick by what you're building
An internal tool for your company: Retool. The CLI publishes Retool apps, and the changelog says that CLI is on Team, Business, and Enterprise. A custom domain is a CNAME, or A records for an apex domain (docs).
An app that lives inside your team's workspace: Taskade Genesis. Custom domains start at Business (FAQ).
Something you want to sell, with checkout built in: Boonful (studio).
Apps on Kubernetes you hold the keys to: my-app.engineer. By default that is an isolated space on their shared cluster. A dedicated cluster is Pro only (site).
A site Claude Code, Cursor, Codex, or Windsurf already built, on your own domain: DropTheHassle. One command or one MCP call gives you a free HTTPS link with no account. A .com is €19 / $19 a year, including VAT in the EU, the same every year. Your AI can find the name. Only you can pay for it.
What DropTheHassle doesn't do
It does not build the app, and it has no app editor. It does not sign visitors in or take their payment. It hosts the folder your AI already made, and it gives that folder a domain. We publish the files. We do not run Node, Python, or PHP for you: host that part on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card.
Hosts for a static folder, including renewal, are on Netlify vs Vercel vs Cloudflare Pages. Publishing from the agent is on the MCP guide.
Publish your site for free
Questions
Which of these is for a site my AI already built?
DropTheHassle. It hosts the folder and gives it a domain. It does not build the app. Retool publishes Retool apps, Taskade Genesis builds inside Taskade, Boonful is for selling apps, ebooks, and courses, and my-app.engineer deploys to a Kubernetes cluster under your account (a dedicated one only on Pro).
How does a Retool custom domain work?
Retool's custom domain docs use a CNAME to custom-domain.retool.com for a subdomain. An apex domain is also supported, with A records to Retool's static IP addresses. That page does not name a plan. The changelog says the CLI is on Team, Business, and Enterprise.
Does Boonful publish a custom domain?
Not on the studio or pricing pages checked on 30 September 2026. Those pages describe building and selling, a connector, and a price of $29.95 a month plus 5% per sale and Stripe fees.
Can my AI pay for the domain?
Not here. Your AI can publish. It can never spend your money. A .com bought here is €19 / $19 a year, including VAT in the EU, the same every year.
Related
Move your app off Lovable or Replit
Netlify vs Vercel vs Cloudflare Pages, with renewal
GoDaddy Node.js Hosting vs DropTheHassle for AI-built apps
All guides
Publish from your AI

---
# https://dropthehassle.com/compare/dropthehassle-vs-godaddy-nodejs-hosting

GoDaddy Node.js Hosting vs DropTheHassle for AI-built apps
GoDaddy Node.js Hosting (launched 29 September 2026) runs your app as a Node.js server, with a managed MySQL database, and deploys from a zip, GitHub, its API or the gddy CLI. Previews are free (up to two apps), but publishing needs a GoDaddy Web Hosting plan: Economy is $5.99 a month for a 3-year term and includes 1 published app. DropTheHassle hosts built sites (HTML, CSS, JavaScript; single-page apps work), gives a free HTTPS link with no account, and sells a .com for €19 / $19 a year, including VAT in the EU, the same every year. 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. If it's a folder with an index.html, DropTheHassle is free and your AI can't spend your money.
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: 1 October 2026. Every GoDaddy claim below was checked against the linked GoDaddy page on that date. GoDaddy prices are from its US site in US dollars; prices in your country may differ.
The difference in one line
GoDaddy runs your app on its servers. DropTheHassle puts your site online and links the server part you keep elsewhere. Everything else follows from that.
Comparison
The table scrolls sideways on a narrow screen. Each GoDaddy cell links to the page the claim came from.
Question
DropTheHassle
GoDaddy Node.js Hosting
What it runs
Built files: HTML, CSS, JavaScript, images. Unknown paths serve index.html, so single-page apps work. A server of your own (AWS, Google Cloud, DigitalOcean or your own machine) connects in the Backend card.
Node.js 22 apps as persistent processes: Express, Fastify, Nest, plus Next.js, Nuxt, Remix, React and Vue (product page, press release).
Database
None. Your backend stays where it is (Supabase, Lovable Cloud, your own API).
Managed MySQL included with published apps (press release).
Free tier
A free name.dropthehassle.app link with HTTPS, live to the public. No account or card. Claim it with your email to keep it.
Up to two private preview apps, no Web Hosting plan or card needed. Publishing needs a paid plan (press release).
What publishing costs
Free on the dropthehassle.app link. Connecting a domain you own is free.
A GoDaddy Web Hosting plan with a free app slot: Economy 1 published app, Deluxe 10, Ultimate 25 (product page FAQ). Economy $5.99, Deluxe $7.99, Ultimate $12.99 "for first 3-yr term" (web hosting).
After the first term
No hosting fee to renew.
Economy: "You pay $215.64 today. Hosting auto-renews Oct. 2029 at $551.63" (offer page).
.com, first year
€19 / $19 a year, including VAT in the EU.
$0.01 for the first year, "3-year purchase required" (.com page). Hosting plans list a "Free domain*" with conditions (web hosting).
.com, renewal
€19 / $19 a year, including VAT in the EU, the same every year.
"Additional year(s) $22.99" (.com page).
DNS you edit yourself
None if you buy the name here. One A record if it stays at your registrar.
None if the domain is at GoDaddy. Otherwise GoDaddy tells you which records to add (product page).
How you deploy
Drop a folder or .zip on the site, npx -y dropthehassle@latest deploy, or the MCP server at https://dropthehassle.com/mcp. A first deploy needs no account or token.
Zip upload or GitHub in the dashboard, the REST API with a Personal Access Token, or the gddy CLI after gddy auth login (help article, CLI reference).
What the agent skill does
Not needed: the CLI and MCP deploy directly.
The godaddy-nodejs-hosting skill prepares and validates your project for the platform (build and start scripts, port, a small server for static builds). You then deploy with GitHub or a zip in the hosting UI (skill repo). Agents can also run the gddy CLI with your credentials (product page).
Can the agent spend money?
No. Your AI can publish. It can never spend your money: buying a domain is always your own click.
The gddy CLI includes gddy domain purchase, which "charges the account" when run with --confirm (CLI reference).
Upload size
25 MB before you claim the site, 100 MB after.
Zip under 100 MB, without node_modules (skill contract).
Email at your domain
€5 / $5 a month, including VAT in the EU, for the first inbox, €3 / $3 a month per extra inbox.
Hosting plans list "Free email" with conditions (web hosting).
When GoDaddy is the better pick
Your app needs a server. An Express or Fastify API, server-side rendering with next start, background jobs, websockets or anything that keeps data in memory. GoDaddy runs it for you; with us it runs on AWS, Google Cloud, DigitalOcean or your own server, connected in the Backend card.
You need a database next to it. GoDaddy includes managed MySQL. We host no databases.
You want a deploy on every push. GoDaddy can build from GitHub automatically. We don't build from GitHub; you (or your AI) upload a finished folder.
You already pay for GoDaddy Web Hosting and have a free app slot, or your domain is already at GoDaddy and you'd rather keep everything in one account.
A Lovable app made from 13 May 2026 (TanStack Start) or a Replit app with a server needs its server running somewhere: on GoDaddy, or on AWS, Google Cloud, DigitalOcean or your own server, connected in the Backend card. TanStack Start isn't in GoDaddy's published framework list, so check with GoDaddy before you move one there.
Choose DropTheHassle if
Your site is already built files: a folder with an index.html (a dist, build or out folder, or a single HTML file from ChatGPT or Claude).
You want it live now, free, without an account, and decide later whether to keep it.
You want your AI to publish without being able to buy anything. Our CLI and MCP deploy and can check if a name is free, but the checkout is always your click.
You want the renewal price in writing: a .com is €19 / $19 a year, including VAT in the EU, the same every year.
You don't want to edit DNS, or you already own the name and one A record is enough.
DropTheHassle doesn't run the server itself: you host it on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card. We publish the folder.
Publish your site for free
Questions
Does GoDaddy Node.js Hosting have a free plan?
You can create up to two private preview apps for free, with no Web Hosting plan or card. To publish an app to the public, GoDaddy requires a Web Hosting plan; Economy includes 1 published app.
What does GoDaddy Node.js Hosting cost?
On GoDaddy's US site on 1 October 2026: Economy $5.99, Deluxe $7.99 and Ultimate $12.99 a month for the first 3-year term, with 1, 10 and 25 published apps. Their offer page says Economy is $215.64 up front and auto-renews after 3 years at $551.63. GoDaddy says there are no per-request, per-GB or per-build-minute charges.
Can DropTheHassle run my Node.js or Next.js server?
Not on our machines. A Next.js app without server features can be exported as plain files (output: 'export'), and that folder works here. Anything that needs next start or an API route runs on AWS, Google Cloud, DigitalOcean or your own server; connect it in the Backend card and it serves from your domain here.
Can my AI spend money?
On DropTheHassle, no. Your AI can publish. It can never spend your money: buying a domain is always your own click. GoDaddy's CLI, which its Node.js page says agents can run with your credentials, includes a domain purchase command that charges your account when it's confirmed.
What does a .com cost next year?
On DropTheHassle, €19 / $19 a year, including VAT in the EU, the same every year. On GoDaddy's US .com page, $0.01 for the first year with a 3-year purchase required, then $22.99 for each additional year.
I built a simple site with Claude or Cursor. Which one?
If it's HTML, CSS and JavaScript (a single-page app is fine), DropTheHassle is free and needs no setup: drop the folder or run npx -y dropthehassle@latest deploy. If it has its own server, host it on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card.
Related
Netlify vs Vercel vs Cloudflare Pages for a small static site
AI app builders with your own domain, compared
Move your app off Lovable or Replit: where to host it
Deploy with your AI (MCP)
Put your Claude Code website online
Put your Cursor site on your own domain