Website builder vs web hosting — understanding the editing layer vs runtime substrate
Executive Summary & Core Definition
The critical distinction between where your website is visually designed and where its files physically execute: canvas editors vs. Anycast edge networks.
To non-technical creators and small business owners, "website builder" and "web hosting" often sound like interchangeable terms.
They are not. They are two layers of the same stack: the editing layer, where you design your pages, and the runtime substrate, where the files physically live and execute. Telling them apart is what stops you paying for a layer you never use.
The Two Layers Defined
1. The Website Builder (The Design & Editing Layer)
A website builder is the software application you interact with to create your website visually.
- It provides canvas manipulation, section reordering, text editing, and theme token styling.
- Examples include modern section-based editors, AI prompt generation interfaces, and traditional drag-and-drop tools.
- Its primary job is producing a clean, structured representation of your site (such as Zeso's open JSON SiteSpec).
2. Web Hosting (The Runtime & Delivery Substrate)
Web hosting is the physical or virtual server infrastructure that stores your compiled website files and delivers them to visitors across the internet.
- It handles DNS routing, SSL/TLS certificate handshakes, HTTP request processing, and edge asset caching.
- Legacy web hosting involves renting space on a single physical server running cPanel or Apache in a distant datacenter.
- Modern edge hosting compiles sites to static assets distributed across hundreds of global Anycast points of presence.
The two layers do different jobs, and the difference is what you can swap:
| The website builder | Web hosting | |
|---|---|---|
| What it is | the software you design in | the infrastructure your files live on |
| What you do in it | arrange pages, sections and copy | nothing — you never open it |
| What it decides | the structure of the site | where the site answers from, and how fast |
| What you can swap | the builder, if the site is portable | the host, if the site is static |
On this platform one document carries both: the SiteSpec. The builder writes it, the renderer reads it, and what you can take with you is that document and your content, read out over an open API.
Where the money actually goes
Most people who think they are buying a builder are really buying a bundle, and the bundle renews.
| Platform | Intro rate | Renews at | Multiple |
|---|---|---|---|
| Hostinger · Premium | $2.99/mo, 48 months prepaid | $10.99/mo | 3.68x |
| Hostinger · Business | $3.99/mo, 48 months prepaid | $16.99/mo | 4.26x |
| Zarla · Business | $16.99/mo, 36 months prepaid | $49.00/mo | 2.88x |
| Wix · Core | $14.50/mo | $29.00/mo | 2.0x |
| Wix · Light | $17/mo, no promotion | $17/mo | 1.0x |
| zipwp · Starter | $99/yr | $149/yr | 1.51x |
Every row is from the audited comparison pages, and the prepay terms are part of the number: a "monthly" rate that is really a 48-month total divided by 48 is not a monthly rate. How to read a renewal table is about the disclosure itself, and that is the part worth reading before you sign rather than after.
Most of these renew higher and some do not — the table is here so you can see which is which instead of taking a generalisation. The pattern is not dishonesty. A bundle has one price on the way in and another on the way out, and the way out is the one you keep paying for.
What a bundled builder decides for you
When the editor and the host arrive in one purchase, three decisions have already been made for you:
- The host. You cannot buy the editor without the hosting that comes with it, at the hosting's price.
- The renewal. The year-two number is a property of the bundle, and it is the number you will keep paying.
- The exit. How you take the site with you — or whether you can — is set by the same bundle.
On that third one, this page will not tell you they trap you. Our capture did not reach Wix's and Squarespace's pages on export, and "we did not read it" is not "they do not offer it". The comparison pages say exactly that, in the same words, for the same reason: the exit terms are a property of the plan you are on, they change with the plan, and a page that says "export" today may say something else after the next pricing change.
So read them on the day you sign up, not on the day you want to leave. That is the whole cost of the third question, and it is the one most people never pay.
The Modern Decoupled Approach on Zeso
Zeso carries both layers in one document, and prices them separately:
- Intelligent creation: the AI engine turns your business intent into a structured SiteSpec in seconds.
- Edge-native speed: every site is automatically hosted across 330+ global Anycast edge nodes, achieving a median TTFB of <50ms.
- Complete decoupling: your content is readable over a public API without a key and your site is an open JSON document. There is no export fee and no export tier, and leaving is a build rather than a download.
- A flat renewal: app hosting is $15/mo billed annually at a 1.0x renewal multiple, and a one-page site is free forever with the domain registered here.
How to tell which one you are buying
Three questions, in the order they cost you money:
- What does the second year cost? Not the first year, and not the headline rate — the second-year number, printed on the same page. If it is not printed, that absence is the finding, and it is worth more than the number would have been.
- What am I paying for that I do not use? A bundle's hosting, a seat, a page limit — each one is a line you can see, and therefore a line you can cancel.
- What happens on the day I want to leave? Not the feature list. The terms, read on the day you sign.
The first question is arithmetic and takes a minute. The third is the only one that is expensive to get wrong.
Experience edge-native speed on your domain
Sub-50ms TTFB, Anycast BGP routing, and automatic Let's Encrypt certificates across 330+ locations.
Related guides & connected surfaces
- Documentation
Static sites and App Hosting: what each actually runs, and how to choose
The runtime, decided by what the site has to do.
- Solution Architecture
SaaS startups
Choosing the substrate before choosing the editor.
- Lexicon & Q&A
What is Anycast DNS — how global edge routing eliminates latency
Anycast routing allows multiple physical servers worldwide to share a single IP address, routing website visitors to the nearest datacenter automatically.
- Lexicon & Q&A
What is a SiteSpec — the JSON document a site actually is
A SiteSpec is the declarative JSON a site compiles from: pages, theme, sections, collections, locales. One document, every renderer, and portability that is a compile rather than a rescue.
- Lexicon & Q&A
What is Time to First Byte (TTFB) — the thresholds, and what the number is not
Time to First Byte measures the latency from a browser's initial request to the arrival of the first byte of HTML. Why sub-50ms TTFB is essential for search rankings and AI crawler indexing.