Hey PH, Michael here, CEO of Leadpages.
I've been building with Claude every day for the last few months. Not just landing pages. Full sites, blogs, e-commerce stores, interactive tools, games. Last week I went from an idea to a live, functioning site in a single conversation. No designer, no developer, no hosting config. Just a description of what I wanted and a URL at the end.
That's what HTMLPub does. Your AI builds it, HTMLPub puts it on the internet, and when you want to change something tomorrow, you pick up the same conversation. The AI manages the whole thing. Pages, content updates, new sections, new pages. It's not a deploy step. It's an ongoing relationship between your AI and your live site.
We built an MCP server that works with Claude, ChatGPT, n8n, Make, and anything that supports MCP. There's also an API for automation workflows and direct upload at htmlpub.com.
What people are building today:
Full sites with blogs and content pages
E-commerce stores and product catalogs
Landing pages and campaign microsites
Interactive tools, games, and dashboards
Portfolios and project showcases
Every plan includes the MCP connector, AI credits, analytics, form collection with a submissions dashboard, and asset management. Paid plans add custom domains, custom slugs, CSV exports, and pages that stay live permanently. Pro gets you heatmaps, API access, and 5 custom domains.
Free: 5 pages, no credit card, pages expire after 7 days. Starter: $10/mo, 50 pages, 1 custom domain. Pro: $25/mo, 250 pages, 5 domains, heatmaps, API access.
We've been in the landing page business for 12 years. HTMLPub is our bet on what comes next. It's early. I'd rather ship and hear what you need than sit on it for three more months.
What are you building with AI right now? Hit me in the comments.
why don't just connect the Vercel MCP ? actually I just watch until the end your video :) amazing product !!!
@cristian_prodius love that the video did the talking. Vercel is great if you’re already in a dev workflow, but most people generating pages with AI aren’t deploying to a git repo. We wanted the path from “AI made this” to “it’s live at a URL” to be as short as possible. Glad it clicked!
@cristian_prodius Haha! Glad you watched to the end! Fair question though. Vercel MCP still assumes you have a repo, a framework, a build step. It's built for apps. HTML Pub is purpose-built for AI-generated HTML - no repo, no config, just a string of HTML in and a live URL out. Plus forms, analytics, and heatmaps are all baked in so you're not stitching together three other tools on top.
HTML Pub
@cristian_prodius Glad it resonated! Yes it's far more than just publishing HTML, our fault for calling it just "HTMLPub" - it's a tongue and cheek approach, so we're having fun with it :)
HTML Pub
Hey PH, Michael here, CEO of Leadpages.
I've been building with Claude every day for the last few months. Not just landing pages. Full sites, blogs, e-commerce stores, interactive tools, games. Last week I went from an idea to a live, functioning site in a single conversation. No designer, no developer, no hosting config. Just a description of what I wanted and a URL at the end.
That's what HTMLPub does. Your AI builds it, HTMLPub puts it on the internet, and when you want to change something tomorrow, you pick up the same conversation. The AI manages the whole thing. Pages, content updates, new sections, new pages. It's not a deploy step. It's an ongoing relationship between your AI and your live site.
We built an MCP server that works with Claude, ChatGPT, n8n, Make, and anything that supports MCP. There's also an API for automation workflows and direct upload at htmlpub.com.
What people are building today:
→ Full sites with blogs and content pages
→ E-commerce stores and product catalogs
→ Landing pages and campaign microsites
→ Interactive tools, games, and dashboards
→ Portfolios and project showcases
Every plan includes the MCP connector, AI credits, analytics, form collection with a submissions dashboard, and asset management. Paid plans add custom domains, custom slugs, CSV exports, and pages that stay live permanently. Pro gets you heatmaps, API access, and 5 custom domains.
Free: 5 pages, no credit card, pages expire after 7 days. Starter: $10/mo, 50 pages, 1 custom domain. Pro: $25/mo, 250 pages, 5 domains, heatmaps, API access.
We've been in the landing page business for 12 years. HTMLPub is our bet on what comes next. It's early. I'd rather ship and hear what you need than sit on it for three more months.
What are you building with AI right now? Hit me in the comments.
@michaelsacca I'm a long time leadpages customers. I've been building the sales pages in Claude and then transferring them to my leadpages account. Claude was extremely helpful with the copy/design layout. Can we automatically publish to our leadpages account from HTML?
HTML Pub
@destinic it’s coming soon but for now if you’d like to use HTML Pub as an LP subscriber I’d be happy to give you access.
@michaelsacca that would be great! Can't wait to use this and I agree with you...this IS the future of building landing pages and websites.
Product Hunt
HTML Pub
@curiouskitty This was a real problem for us early on. We originally ran on Railway and had to do a full migration to GCP after dealing with crypto miners and phishing pages abusing the platform. So the guardrails came from lived experience, not a checklist.
Here's what's in place:
Structural constraints: Free pages expire after 7 days and cap at 5. Paid tiers cap at 50/250 pages. Scaling abuse requires paying for multiple accounts, which creates both a cost barrier and an identity trail.
Scanning: We have a robust AI scan in place for published pages for known phishing patterns, malware signatures, and spam indicators. We've been training the model for several months with seed data from our 13 years of experience in the field.
Rate limiting: Yes, at both the account and publish level.
Isolation: Published pages are isolated from each other and from HTMLPub's core infrastructure.
Reporting: There's a flag/report mechanism for takedowns.
On the friction balance: we deliberately lean toward keeping the publish flow fast for legitimate users. The 7-day auto-expiry on free pages does a lot of the heavy lifting since most abuse content has a short useful lifespan. And having run Leadpages, hosting millions of pages over 12+ years, abuse prevention isn't new territory for us - we're applying patterns we've battle-tested at much larger scale.
HTML Pub
@curiouskitty Great question. It's a layered system:
Every page is scanned on publish — heuristic pattern matching, Google Safe Browsing for known-bad URLs, IP reputation checks, and an LLM classifier that factors in account age, publishing velocity, and prior violations. High-confidence abuse triggers automatic removal + account suspension. Medium-confidence gets queued for manual review. Pages are periodically re-scanned to catch post-publish changes.
Domain isolation — published pages serve on a separate origin with a strict route allowlist, no access to app APIs. Security headers block eval(), disable device APIs, prevent embedding outside our origins, and serve noindex/nofollow so we can't be used for SEO spam.
Rate limiting across all endpoints, built-in abuse reporting on every page, DMCA workflow, admin review tooling.
All scanning is async — legitimate users publish instantly, never see the machinery. The AI classifier with behavioral signals is what lets us be aggressive on abuse without adding friction for normal use.
Assembly
Congratulations to the Leadpages team! This is an incredible product just in time for a great market need.
@tobyns thank you for the support and encouragement!
@tobyns Thanks so much! Timing felt right for us too. Curious what you're working on right now - is there a specific use case you're thinking about?
I showed this to my wife and it instantly resonated with her. This directly solves a problem she had last week, where she needed to share a website/presentation she made for her MBA. It was created with AI (Claude) which is a little frowned upon in this academic circle and she doesn't have the technical skill to publish it herself. Being able to showcase that page from a custom domain she owns would have been HUGE. Instantly worth whatever you are asking for that one page alone.
@evanmcneely this made my day. Your wife’s use case is exactly the kind of thing we built this for - she has a finished page, she just needs it live, without needing to learn hosting or bother someone technical. Custom domains are available on our Starter plan ($10/month) so yes - absolutely publish from her domain. Tell her we said good luck with her MBA!
HTML Pub
@evanmcneely @yvonnechow Absolutely love hearing this! We heard similar stories over and over throughout our beta period. Can't wait to see what else she builds on it!
@evanmcneely Evan this is such a real story and honestly one of the best use cases we've heard today. The gap between "Claude built me something great" and "I can actually share this professionally" is exactly what HTML Pub closes. A custom domain makes it look like you built it yourself - nobody needs to know the stack. Tell her to sign up and publish that MBA project. Would love to see it.
bugstack
This hits the right pain point for so many vibe coders today! Congrats on the launch, your demo video was fantastic, impressive to see a new product with so many features. What does the workflow look like to assign custom url's?
Blitzit
@masebuilds Thanks Mason, really appreciate the kind words. And yeah, the vibe coding crowd is exactly who we had in mind.
Custom domains are straightforward: go to your page settings, connect your domain, and we handle DNS configuration + SSL automatically. The whole flow takes about 2 minutes. You can point a domain to a single page, a multi-page site, or a blog - your call. Take it for a spin!
MacQuit
The MCP approach is smart — having deployment baked directly into the AI conversation removes so much friction. The gap between "it works in the chat" and "it's live on a URL" has always been annoying, and this makes it disappear. Curious about custom domain support and how versioning/rollback works. Congrats on the launch!
@lzhgus Thanks! That gap between “works in chat” and “live on a URL” was exactly what kept bugging us too.
Custom domains - yes. Paid plans include custom domains with one-click setup (1 on Starter, up to 5 on Pro). Point your domain at any published page.
On versioning: every page is updatable through the MCP connector or API, so your AI can push changes to a live page without creating a new URL. Full version history with rollback is on our radar but not shipped yet - right now the workflow is conversational (your AI manages the current live version). Flagging that as something we’re hearing demand for.
Appreciate the thoughtful question - what’s your use case? That helps us prioritize