Birta vs HTML Pub: What Happens After You Publish

The short answer

Both promise a fast route from an AI conversation to a live page, from different starting points. HTML Pub has its own AI built in: describe a page and its generator produces it, spending AI credits. Birta generates nothing, it publishes what an agent you already use has built.

On the one thing this page keeps returning to, HTML Pub has answered for itself. The guidance it publishes for AI assistants lists the jobs it is the wrong tool for, and version-controlling pages is on that list, with anyone who needs it pointed at GitHub Pages, Netlify or Vercel. So the split is not who runs a connector or who writes the HTML. It is what one connection reaches once the page exists: a draft, a version with its own address, a way back to an earlier publish, and the remarks somebody left on the page.

Where Birta's job starts

Birta has no import button, no file picker and no field for pasting a link, because the agent already does that side: Claude Code, Cursor and Codex read your folder, while Claude Desktop, Cowork and ChatGPT turn a document or a public page into HTML. Birta starts one step later, at the part none of them can do alone: a real address, a record of what was published, a way back to it, a lead form, a domain, a visitor count.

HTML Pub covers the input side from the other direction, and covers it well. Its own AI writes the page inside the product, and its connector puts the endpoint at mcp.htmlpub.com/mcp, signs in over OAuth, and is on every plan including free, though the free plan still will not put a page live.

It is bigger than its docs page looks. That page walks through nine tools for pages, sites and assets, then mentions 37 in passing, while its machine-readable reference puts the server at 48 and describes 36. The vendor gives three counts, so treat the number as approximate. Every tool acts on something already in the dashboard, because that is what the connector was wrapped around. A draft does exist: an edit with edit_page or update_page is held back unless its publish flag is set, and publish_page promotes it to the live URL.

What there is not is a record. Its FAQ warns that deleting a page "is immediate and cannot be undone, so make sure you have a backup if needed", nothing lists what was published before, and the draft has no address of its own to send anybody. Checked across the connector documentation, the REST API reference, the plan comparison, the FAQ and both AI-context files: no version list, no restore, no rollback. The backup is your own copy.

Birta is built the other way round. The connection is how the product is used, so it opens a draft from a stored version, writes files into it, publishes, lists earlier versions, rolls one back, and reads a version's remarks.

Send a version out for review

Before a page is public, somebody has to say what is wrong with it. That round trip is where the two products stop resembling each other.

On Birta a version has its own address, handed to the agent when it opens a draft and again when it publishes, and it keeps working after the site goes live. You send that link to whoever signs the work off. They need no account: access defaults to a plain link, the guest gets a nickname, and closing a thread stays with a project member, enforced on the server.

They mark up the page in the browser. Click the heading, button or price that is wrong, type the remark, and it pins to that element, the thread carrying its number, whether it is open, and every message with author and time. Numbers are not recycled, so "fix number three" points at the same pin next week.

Your agent reads the threads with list_version_comments, changes the same draft and publishes. It cannot reply or mark one resolved, and the attempt is refused; Birta's own instruction tells it to make the changes in the same draft and have the reviewer refresh the same page. Everyone with project access gets one email digest roughly 15 minutes after the first remark, minus their own. No plan gates it, and the versions and remarks guide walks the loop. Two limits: the address belongs to the version rather than the live site, and link access is a default a project can be moved off.

Now HTML Pub, checked across its FAQ, forms page, pricing page, connector documentation and both AI-context files. There is nothing for commenting on, annotating or reviewing a page. The draft exists, but it has no address of its own and nothing pins a remark to it.

The nearest equivalent is real and shaped differently: build a feedback or survey form and HTML Pub collects the submissions, so a reviewer types notes into a form. That arrives as a dashboard row instead of a pin on the element it is about, with nothing tying it to the version that was open at the time.

Compare the work after the first publish

Three rows are worth pulling out of the table. HTML Pub POSTs a form submission to any endpoint you name on every paid plan, and Pro and Business add five live connections to Slack, Zapier and ten email platforms including Mailchimp, Kit, Klaviyo and ActiveCampaign. HubSpot and Pipedrive are not among them, since HTML Pub's own reference puts CRM integrations on the Leadpages plans. Birta does none of it: leads reach the panel and one email digest, and no webhook is announced.

Payments are the second. HTML Pub connects Stripe or Shopify and puts a checkout on a published page. Birta cannot take a payment from your visitors today, so this row belongs to them.

The row going the other way is the free tier. HTML Pub's own FAQ calls the free plan "a build-and-preview sandbox: you can design and preview pages as drafts, but publishing them live requires a paid plan". Birta's free tier publishes live.

Stay on HTML Pub when...

Stay when you want the AI generation itself, not just the hosting after it. Doing both in one product is the whole pitch, and it delivers that.

Stay when a webhook matters right now. If a lead has to land in Zapier, Slack or Mailchimp the moment it arrives, HTML Pub does that on a paid plan. Birta's lead delivery is a panel and one email digest.

Stay when the page has to take money, because Birta has no way to charge your visitors yet.

And stay if you are testing the idea and do not mind a preview-only free tier. Publishing live starts at $10 a month.

Birta fits better when...

Birta fits once an agent builds the site and the job left is publishing it, keeping a version history, and handling what happens when someone fills out a form.

Choose it when a bad update needs to be reversible. Every publish becomes a version, the last 10 stay available, any goes live again with the original files, and each downloads as one archive.

Choose it when somebody else approves the page first. You send the version address, they open it without signing up and mark the wrong heading where it is wrong, and your agent fixes it in the same draft. On HTML Pub that conversation happens in chat or a feedback form, away from the page.

Choose it when a real form belongs on the site and you want it live before paying for anything. The free tier publishes the site and the form, capped at 10 leads a month per project.

The honest tradeoffs are the webhook and the checkout. If routing a lead into another tool or charging a visitor is today's requirement, those are real reasons to choose HTML Pub.

Moving from HTML Pub

A short migration, because the two products barely diverge at the file level once a page exists.

1. Step 1Recover the published HTMLSave the live page's HTML, CSS, JavaScript, and assets from the current HTML Pub project.
2. Step 2Rebuild anything webhook-dependentIf a form pushes submissions to a webhook, Zapier or Slack, have your agent recreate that logic separately, since Birta's form delivery is the project panel and an email digest, not a webhook. Do the same for a Stripe or Shopify checkout, which Birta has no equivalent for.
3. Step 3Publish and verifyPublish through Birta, check every page and the form submission, then move an owned domain's DNS once the new site passes review.

If the webhook is doing real work in your process, replace it before you rely on the new site for anything time-sensitive.

The decision

HTML Pub is the right call when you want its own AI to generate the page and you need a webhook-connected form or a checkout immediately. Birta is the better fit when an agent you already use builds the site and you want it published with real version history and a working lead form, including on the free tier.

That last row is the one nobody in this category has closed. Among the hosts Birta gets compared with, not one connection reaches a version list and a rollback. HTML Pub is unusual only in saying so out loud and telling you where to go instead.

Frequently asked questions