This is the most consequential decision in the whole process, and it's usually made by accident: someone buys hosting because that's the word they heard, then discovers they have an empty folder and no idea what goes in it.

The distinction in one line

Hosting = a place for a website to live. Builder = a place for a website to live, plus the tools to make one, plus somebody else maintaining the machinery.

They're not competitors so much as a component and a finished product.

What each one actually gives you

	Hosting only	Website builder
Place for files	Yes	Yes
Way to build pages	No — you install software or write HTML	Yes, drag and click
Templates	No	Yes, dozens
Security updates	Server only; you handle the app	Included
SSL certificate	Usually, sometimes manual	Included
Cost	$3–$25/mo	$10–$35/mo
Who fixes it when it breaks	You, or support that stops at the server	Them
Can you move it later	Yes, files are yours	Usually no — the site lives in their system

The hidden cost of "more control"

Hosting-only is cheaper per month and more flexible. Both true. What isn't on the price list is the time.

With hosting on its own, you're responsible for: installing WordPress (or writing HTML), choosing and maintaining a theme, updating the software and plugins, taking backups, renewing the certificate if it isn't automatic, and dealing with the afternoon when an update breaks the layout.

That's maybe a weekend to set up and an hour a month forever, plus one bad afternoon a year. If you enjoy it, it's a hobby with a website attached. If you don't, it's a subscription to anxiety.

Builders exist to sell that time back to you. The premium — often $10–$20 a month over raw hosting — is usually the best-value line item in a small business's web budget.

When hosting on its own is the right call

• You're running an online store with specific needs and the builder's checkout doesn't fit.
• You already know WordPress and have a reason to keep it — a plugin you depend on, a developer who works in it.
• You need something a builder can't do — a custom application, unusual integrations, very high traffic.
• Someone else maintains it and you're paying them, not learning it.

"I want to own my files" is a legitimate reason too, but be honest about whether you'll ever move them.

When the builder is obviously right

• One to five pages of information about a local business.
• You want to change the hours yourself without calling anyone.
• The site is a sign, not a system. It doesn't need to be clever.
• You have no interest in learning what a plugin is.

And if one page is genuinely all you need, the free tier of this category — a service that builds the page from a form — is the cheapest version of the same decision. See free website vs paid website.

The wrong path, in full

It looks like this: someone buys a $3.95 hosting plan, an empty control panel appears, they search "how to make a website," install WordPress because a video says so, pick a free theme, spend two weekends on a page, then leave it half-finished for a year because updating plugins is nobody's idea of a Saturday.

There's now a live WordPress site with default content, no security updates, and a certificate that expired in March. That's worse than a free one-page site, and it costs more.

The decision test

Ask one question: do I want a website, or do I want to run a website?

The first answer points at a builder or a free service. The second points at hosting, and you should go in with your eyes open about the maintenance — see what WordPress involves.