Website Builders Are Dead. Deploy Your Site as Code in an Hour.

I rebuilt our marketing site last week. Not redesigned — rebuilt from scratch. New layout, new copy, new pages, responsive, dark mode, analytics. It took 47 minutes. It's live at a custom domain with HTTPS, global CDN, DDoS protection, and zero monthly cost.

I didn't open Squarespace. I didn't log into WordPress. I didn't drag a single block into a single column. I wrote HTML, pushed it to GitHub, and Cloudflare did the rest.

And I keep asking myself: what exactly are people paying $16-48/month for?

The Website Builder Tax

Let's do the math that the website builder industry hopes you never do.

Squarespace: $16/month (Personal) to$49/month (Commerce). That's $192-$588/year. For hosting static files. Files that GitHub will host for free. Files that Cloudflare will serve from 310 edge locations for free. Files that load faster from a CDN than from Squarespace's servers anyway.

Wix: $17/month to$159/month. The premium tier — $159/month,$1,908/year — gets you "priority support" and more storage. Storage for what? Your five-page marketing site? The same five pages that fit in a GitHub repo using 0.001% of your free allocation?

Webflow: $14/month to$39/month for hosting. Plus $16-35/month per seat for the designer. A freelancer running three client sites on Webflow is paying$100+/month before they've written a line of copy.

WordPress managed hosting (WP Engine, Kinsta, Flywheel): $20-60/month for a CMS you don't need, running PHP you don't want, with a database for content that changes once a quarter, protected by security patches for vulnerabilities that exist because you're running PHP.

Add it up. A small business running a marketing site on any of these platforms is paying $200-700/year for something that costs exactly$0 to host and $10-15/year to put on a custom domain.

The website builder industry is a $15 billion market built on the assumption that "regular people" can't deploy a website without a visual editor. That assumption was already shaky. In 2026, it's indefensible.

What Actually Changed

Three things converged to make website builders obsolete for the vast majority of use cases.

GitHub Pages became trivially easy. Not "developer easy." Actually easy. Create a repo. Drop in an index.html. Enable Pages in settings. You have a live website. That's it. No CI configuration. No build step. No server. No terminal. You can do the entire thing from GitHub's web interface without installing anything.

Cloudflare's free tier became absurdly generous. Free DNS. Free CDN. Free DDoS protection. Free SSL. Free analytics. Free page rules. Free caching. The performance and security stack that used to cost $200/month from a traditional CDN is now$0. And it's better. Cloudflare's network is larger than most paid CDN providers. Your free-tier site loads faster than your competitor's $49/month Squarespace site because Cloudflare has an edge node in the city your visitor is sitting in.

AI writes the HTML now. This is the part the website builder companies don't want to talk about. The entire value proposition of Squarespace was "you don't need to know code." But in 2026, you don't need to know code to write code. You describe what you want. Claude, GPT, or any capable model writes the HTML, CSS, and JavaScript. You paste it into a file. You push it. It's live. The AI doesn't generate Squarespace-quality output — it generates better output, because it writes clean semantic HTML that loads in 200ms instead of a framework-heavy page that loads in 3 seconds.

The One-Hour Deployment

Here's the complete walkthrough. This isn't a simplified version. This is the whole thing.

Step 1: Create the Repository (5 minutes)

Go to github.com. Create a new repository. Name it yourname.github.io if you want it to be your primary site, or any name if it'll live at a custom domain.

Add an index.html. You can do this directly in GitHub's web editor. Click "Add file" → "Create new file" → name it index.html → paste your content.

If you don't have content yet, ask any LLM: "Write me a complete, responsive, single-page website for [your business]. Include a hero section, about section, services section, and contact form. Use modern CSS with a dark color scheme. No frameworks, no dependencies, just HTML and CSS." You'll get a production-ready page in 30 seconds.

Commit it. That's your source code. That's also your deployment pipeline. They're the same thing.

Step 2: Enable GitHub Pages (2 minutes)

Go to Settings → Pages. Under "Source," select your branch (main). Click Save.

Your site is now live at https://yourname.github.io (or https://yourname.github.io/repo-name).

That's it. That's the deployment. There's no build step. There's no CI/CD to configure. There's no server to provision. GitHub saw your HTML file and started serving it from their CDN. You are now running a website.

Step 3: Get a Domain (10 minutes)

Go to any domain registrar — Cloudflare Registrar, Namecheap, Porkbun, Google Domains. Buy a domain. Most .com domains are $10-15/year. Many TLDs are cheaper.

If you buy through Cloudflare Registrar, you pay exactly what Cloudflare pays the registry — no markup. A .com is about $10.11/year.

Step 4: Set Up Cloudflare (15 minutes)

Create a free Cloudflare account if you don't have one. Add your domain. Cloudflare will scan your existing DNS records (there won't be any for a new domain) and give you two nameservers.

Go back to your registrar. Change the nameservers to the ones Cloudflare gave you. This takes 2 minutes to do and up to 24 hours to propagate, though it usually takes 5-15 minutes.

Step 5: Point DNS to GitHub Pages (5 minutes)

In Cloudflare's DNS settings, add these records:

Type: CNAME
Name: www
Target: yourname.github.io
Proxy: On (orange cloud)

Type: CNAME
Name: @
Target: yourname.github.io
Proxy: On (orange cloud)

Or if you prefer A records for the apex domain:

Type: A
Name: @
Target: 185.199.108.153

Type: A
Name: @
Target: 185.199.109.153

Type: A
Name: @
Target: 185.199.110.153

Type: A
Name: @
Target: 185.199.111.153

Type: CNAME
Name: www
Target: yourname.github.io

Step 6: Tell GitHub About Your Domain (2 minutes)

Back in your GitHub repo → Settings → Pages → Custom domain. Type your domain. Save. GitHub will verify it and provision an SSL certificate automatically.

Add a CNAME file to your repository root containing just your domain name:

yourdomain.com

Check "Enforce HTTPS." Done.

Total Time: ~40 minutes

And 15 of those minutes were waiting for DNS propagation while you made coffee.

What You Now Have

• A website at your custom domain
• HTTPS everywhere (GitHub's cert + Cloudflare's edge encryption)
• Global CDN (Cloudflare's 310+ edge locations)
• DDoS protection (Cloudflare's free tier handles volumetric attacks)
• Analytics (Cloudflare's free web analytics — no JavaScript tracker needed)
• Version control (every change is a git commit)
• Rollbacks (revert any commit, site rolls back instantly)
• Collaboration (anyone can submit a pull request to suggest changes)
• Uptime that exceeds what you'd get from a $49/month hosting plan

What You Pay

• Domain: ~$10-15/year
• Everything else: $0

"But I Need a CMS"

No, you probably don't.

A CMS exists to let non-technical people edit content without touching code. But "touching code" in 2026 means opening a file on GitHub's web interface and editing text. If you can edit a Google Doc, you can edit an HTML file. The structure is already there. You're just changing the words between the tags.

For blogs, use a static site generator. Hugo, Astro, Eleventy, or even Jekyll (which GitHub Pages supports natively with zero configuration). Write your posts in Markdown. Push. The site rebuilds automatically. Your "CMS" is a text file and a git push.

If you truly need non-technical people to edit content without seeing any code at all, use a headless CMS like Decap (formerly Netlify CMS) — it's free, open source, and adds a visual editor on top of your GitHub repo. Your content still lives in git. Your hosting is still free. You just get a nice editing UI.

The WordPress value proposition — "you need a database-backed CMS to manage content" — only makes sense if your content changes hourly and your editors can't handle a text file. For 95% of business websites, the content changes quarterly and the "editor" is the business owner copying text they already wrote in a Google Doc.

"But I Need E-Commerce"

This is the one case where the website builder pitch has some legitimacy, and it's shrinking fast.

If you're selling physical products with inventory management, shipping calculations, and tax compliance, you need a platform: Shopify, WooCommerce, or similar. The commerce logic — payment processing, inventory, fulfillment — justifies platform costs.

But if you're selling services, digital products, subscriptions, or anything that's ultimately "pay me and I'll give you access to a thing" — you don't need a commerce platform. Stripe has a hosted checkout page. Lemon Squeezy handles digital product delivery. Gumroad handles everything from ebooks to memberships. These are tools, not platforms. You link to them from your static site. They handle the money. Your website handles the marketing. Nobody needs to pay Squarespace $33/month for the privilege of adding a "Buy" button.

"But I'm Not Technical"

This is the core objection, and it deserves a direct answer.

You're reading this on a device that you configured with a WiFi password, an email account, app-specific settings, notification preferences, and probably a VPN. You manage cloud storage, shared documents, calendars, video calls, and a dozen SaaS tools with various permission models. You are technical. You just don't think of yourself that way because the word "technical" has been gatekept by people who benefit from you believing that HTML is hard.

HTML is not hard. It's the simplest structured format in common use. It's literally just text with angle brackets around it that tell a browser what to do. A paragraph is <p>text</p>. A heading is <h1>text</h1>. A link is <a href="url">text</a>. If you can write an email, you can write HTML. You already use a more complex markup language every time you format a Slack message or a Notion page.

And you don't even have to write it. Copy your existing Squarespace site into Claude. Say "convert this to clean, standalone HTML and CSS." Deploy the output to GitHub Pages. You just replicated your $500/year website in a free repository.

The website builder industry's moat was never technology. It was the belief that technology is scary. That belief is dissolving faster than their subscriber counts.

The Performance Gap

Here's something that doesn't get talked about enough: website builder sites are slow.

Not slow by the standards of 2015. Slow by the standards of what's possible when you serve static files from a CDN.

A typical Squarespace page loads 2-4MB of JavaScript, CSS, and framework overhead before your content renders. That's the price of a drag-and-drop editor — the page has to carry the weight of the builder's rendering engine, analytics, A/B testing framework, font loader, animation library, and whatever else ships in the template.

A hand-written HTML page with inline CSS loads in under 100KB. On Cloudflare's CDN, that's a sub-200ms time-to-first-byte from anywhere on Earth. Your site loads before the user's finger leaves the mouse button.

Google cares about this. Core Web Vitals — LCP, FID, CLS — directly affect search ranking. A static HTML site on a CDN will consistently score 95-100 on Lighthouse. A Squarespace site rarely cracks 70. You're paying $16/month for worse SEO.

The Security Gap

Every WordPress site is an attack surface. Every Wix site is a bet that Wix's security team is better than the attackers targeting their platform. Every Squarespace site trusts that Squarespace's shared infrastructure doesn't have a vulnerability in whatever PHP/Node/Ruby stack they're running.

A static HTML site on GitHub Pages has no server-side code. There's nothing to exploit. No database to inject. No CMS admin panel to brute-force. No PHP plugins with known CVEs. The attack surface is: your DNS (Cloudflare handles that) and your GitHub account (protected by 2FA, hardware keys, and GitHub's security team).

You've eliminated entire categories of vulnerability by removing the server.

Who Still Needs a Website Builder

I'll be fair. There are legitimate use cases:

1. High-frequency content teams where multiple non-technical editors publish daily and need a proper editorial workflow. But even here, you're increasingly better served by a headless CMS + static site than by WordPress.

2. Rapid prototyping agencies that need to spin up 50 client sites a month with visual editors. The time savings of Webflow's designer tools can justify the cost at scale.

3. Enterprise marketing teams locked into compliance frameworks that mandate specific platforms. This isn't a technical requirement — it's a procurement requirement. Different problem.

For everyone else — freelancers, small businesses, startups, personal sites, portfolios, documentation, blogs, landing pages, project sites — you're paying rent on something you could own.

The Endgame

The website builder market won't collapse overnight. Squarespace has $900M in annual revenue and a lot of inertia. Wix has 240 million registered users. WordPress powers 40% of the web (though "powers" is doing a lot of heavy lifting — most of those sites would be better as static HTML).

But the trajectory is clear. The bottom of the market — personal sites, small business sites, portfolios, blogs — is already gone. You can't charge $16/month for file hosting when the alternative is free and better. The middle of the market — more complex marketing sites with some dynamic content — is being eaten by headless CMS tools on top of free hosting. The top of the market — full-featured web applications — was never a website builder use case in the first place.

What's left is the inertia tax. People paying Squarespace because they set it up in 2019 and haven't thought about it since. People paying Wix because they don't know there's an alternative. People paying WordPress hosting because someone told them WordPress was the way to build a website, and that was true in 2012.

The information asymmetry is the entire product. The moment a business owner realizes they can ask an AI to write their site, push it to GitHub, point Cloudflare at it, and never pay a hosting bill again — that's a customer the website builder industry never gets back.

And that moment is happening millions of times a day now.

Get Started in the Next Hour

Here's the action plan:

1. Go to github.com and create a free account (if you don't have one)
2. Create a new repository
3. Ask any AI to generate your website's HTML
4. Paste it into an index.html file in your repo
5. Enable GitHub Pages in Settings → Pages
6. Buy a domain ($10/year)
7. Set up free Cloudflare DNS
8. Point it at GitHub Pages
9. Cancel your website builder subscription

You'll spend 40 minutes now and save $200-700 every year after. Your site will be faster, more secure, and entirely under your control. You can edit it from your phone by opening GitHub's mobile app. You can roll back any change by reverting a commit. You can move it to any other host by copying the files — because they're your files, not locked inside a proprietary builder.

Your website is just files. Serve them for free. Keep the money.