1
0 Comments

I kept generating beautiful HTML with ChatGPT... and then hitting a wall. So I built the fix.

A few months ago I noticed something dumb happening over and over in my own workflow.

I'd open ChatGPT or Claude, ask for a landing page, a bio page, a quick microsite for a campaign and it would nail it. Clean HTML, good copy, done in two minutes.

Then I'd just... sit there. With a beautiful page and no way to actually put it online without either:

  • opening a code editor and remembering how FTP works,
  • setting up a GitHub repo I didn't need,
  • or texting a dev friend "hey can you just upload this real quick" (and then waiting).

The AI did the hard part. I was stuck on the easy part and it was blocking me every single time.

The part that annoyed me most: I'm not really a non-technical person. I know what deploying means. I just didn't want to context-switch out of the AI chat, open five tools, and spend 20 minutes on something that should take 20 seconds.

So I started asking around in marketing groups, no-code communities, freelancer circles and it turned out almost everyone hits this exact wall. Marketers generating campaign pages who have zero interest in learning Git. Freelancers who build fast with AI but waste time on repetitive manual uploads for every small client job. Agencies doing this dozens of times a month with FileZilla open in a tab, terrified of overwriting a client's live site by mistake.

Same story, different people: AI closes the gap on "can I build this," but nobody closed the gap on "can I ship this."

That's what I built HTML Deployer to fix.

What it does, in plain terms:

It's a Chrome extension that sits on top of ChatGPT, Claude, and Gemini. It auto-detects the HTML code block in your conversation (no copy-pasting), lets you preview it across desktop/tablet/mobile, and then deploys it wherever you want: Netlify, Vercel, GitHub Pages, your own FTP hosting, or a self-hosted endpoint if you want zero lock-in. Or just export a clean ZIP if you'd rather upload it yourself. Click deploy, get a live URL and a QR code, in under 10 seconds.

The design principle I kept coming back to: don't lock people into one hosting provider. Every other "AI to website" tool I looked at wanted to own the hosting relationship. I didn't want that, I wanted it to be the bridge, not the destination.

What I'm still figuring out:

  • Whether FTP/self-host is actually used enough to be worth the support burden, or if 90% of people just want Netlify and I should simplify around that.
  • How to message this to agencies specifically — they care way more about "will this overwrite production by accident" than about speed, and I'm not sure my current onboarding addresses that fear early enough.
  • Pricing. Right now it's free to install with no account required, and I genuinely don't know yet where the paywall should sit.

If you've ever built something great with AI and then hit that exact "okay... now what" moment trying to actually publish it, I'd love to hear how you worked around it before something like this existed. And if you try it and it breaks on your workflow, tell me that's more useful to me than a compliment.

Try it here: https://chromewebstore.google.com/detail/html-deployer-1-click-ai/gihmknkabkkghpiocgnoiejagngdegea

on July 9, 2026
Trending on Indie Hackers
5 days post-launch: Top 50 on Product Hunt, zero signups, and why I think that's actually fine User Avatar 118 comments The feature you're most sure about is the one you should question first User Avatar 118 comments I let 3 LLMs argue on the famous AI "Car wash: Walk or Drive" problem to prove a point. User Avatar 50 comments Built a local-first privacy extension. Looking for feedback. User Avatar 38 comments I built an AI fitness coach, then realized AI was only solving half my funnel User Avatar 35 comments I spent months chasing clients who already had a webmaster. So I built something that only finds the ones who don't. User Avatar 34 comments