How to put a website online without knowing how to code

AI can write a website. Ask ChatGPT or Claude for "a one-page site for my bakery with our hours and a photo" and you will get one, in seconds, and it will be decent.

Then you are stuck. You have a folder of files, or a block of code in a chat window, and no idea what to do with it. The AI cannot help much either, because putting a website online has always been a separate problem from building one.

This is about that second half.

What "hosting" actually means

A website is just files — some HTML, maybe an image and a stylesheet. Your browser knows how to display them. The only thing missing is a computer, somewhere on the internet, that is switched on all the time and will hand those files to anyone who asks.

That is hosting. A computer that answers.

It sounds trivial, and conceptually it is. What made it hard was everything bolted around it: you had to rent the computer, install software on it, point a domain name at it, get an HTTPS certificate so browsers would not warn people away, and then keep all of that working. None of that is about your bakery.

Why the usual advice does not help

Search for how to publish a website and you get answers written for people who already know the vocabulary:

• "Just push it to GitHub Pages." Requires a GitHub account, git, and knowing what a repository is.
• "Drag the folder into Netlify." Closer, but assumes you have a folder, know where the AI put it, and can tell the built files from the source.
• "Get a VPS for $5 a month." Now you are a system administrator.

None of these are bad tools. They are just written for developers, and they assume the person doing the publishing is the person who wrote the code. When your AI wrote the code, that assumption breaks.

What changes when the AI does it

The useful shift is not another drag-and-drop box. It is letting the thing that built your site also publish it — because it already has the files, it already knows which ones matter, and it can read an error message and fix it.

That needs three things to be true:

1. The AI needs an account it can act on. Not your password: a separate code that only lets it publish, and that you can revoke.
2. Publishing has to be one step. Not "build, then configure, then upload, then set up a certificate."
3. Failures have to be readable by a machine. If a deploy fails, the error has to say what to change, not just that something went wrong. Otherwise the AI comes back to you with "it didn't work", which helps nobody.

That third one is the part most services get wrong, and it is the difference between an AI that fixes its own mistake and one that hands the problem back.

What it looks like in practice

With BlueDeploy, the whole thing is:

1. Sign up. A code is created with your account — you do not have to make one.
2. Paste one line into your AI. It contains the code and a link to the instructions, which the AI reads itself.
3. Ask for a website.

Your assistant suggests an address, checks it with you, builds the site, and publishes it. You get back a real link — something like sunrise-bakery.bldeploy.run — that works immediately, over HTTPS, and that you can send to anyone.

Want a change? Ask for it. The same address updates in seconds.

What you are not signing up for

Worth being clear, because "free" is doing a lot of work in most hosting marketing:

• No credit card. The free plan needs one only if you want to run server-side code, and that is a fraud check, not a charge.
• No servers to manage. There is nothing to patch or restart.
• No domain required. You get a working web address for free. You can point your own domain at it later on a paid plan, but nothing breaks if you never do.

The free plan covers 3 websites, 100 MB of storage and 100,000 visits a month. For a bakery, a portfolio or a wedding page, that is not a trial — it is enough indefinitely.

The honest limits

Free hosting that never mentions its limits is hiding them. Ours:

• Custom domains are paid. Free sites live on a bldeploy.run address.
• Running code on a server needs a verified account. Static pages — which is most sites — work straight away. Anything that saves data, handles logins or talks to a database needs you to confirm you are a real person first. That is free too; it just is not automatic.
• Very busy sites cost money. Past 100,000 visits a month you will need a paid plan. Most personal sites never get close.

Where to start

If you already use an AI assistant, you are most of the way there. Create an account, copy the line it gives you, and ask for the site you want.

The part that used to be hard is now the part you do not do.