The short answer
EdgeOne Pages, from Tencent Cloud and also known as EdgeOne Makers, is not really a static-site host anymore. Its own pitch is building web apps and AI agents, with Cloud Functions, Edge Functions, AI agents with built-in models, and Blob and KV storage, all on a free tier the company says will stay free permanently. That's a much bigger product than Birta.
Birta stays narrow on purpose, and the narrow part goes deep. The connection to the agent you already use is how the product is used rather than a console with a connector added to the side of it, so one connection reaches the draft, the published version at its own address, the rollback, the declared lead form and the remarks a reviewer pinned to the page. On EdgeOne those things live in the console, where preview branches get switched on per project.
If the job needs backend functions, a database, or an AI-agent runtime, EdgeOne Pages is doing something Birta doesn't attempt. If the job is a static site with a real form and a round of feedback on it, Birta is the more focused tool.
No Git connection, and no importer
EdgeOne Pages takes your project in through its own front door: a Git repository it builds for you, its Copilot flow, or a deploy from AI output. Birta has none of that. No repository connection, no build step, no importer, nothing that pulls a project out of somewhere else. And none of it is planned.
That reads like a gap until you notice who is standing between you and the files. Claude Code, Cursor, Codex and Claude Cowork already read your working directory, run your build, and fetch a page or a document from a URL when you ask. Duplicating any of that inside a publishing service would add a second way to do something you already have.
So Birta picks up the finished output. Its side of the line is the address, the version history with rollback, remarks a reviewer leaves on a version, a declared lead form, a domain and a daily visitor count. The build stays with your agent, which is also why there is nothing here to configure: no framework detection, no build command, no deploy hooks.
Worth being blunt about the other direction too. Because Birta only serves
stored files, a real single-page app that expects every path to fall back to one
index.html will not work. An ordinary multi-page static site does, so this is
a narrower limit than "routing is broken", but it is a hard one.
Compare scope and the work after publish
| Decision | EdgeOne Pages | Birta |
|---|---|---|
| Best fit | Full-stack web apps and AI agents on Tencent's edge network | A static commercial site an agent already built |
| Building the site | Deploy from Git or AI, build with its own Copilot | An agent produces the site; Birta never generates or edits it |
| Free tier | Functions, AI agents, Blob/KV storage, and no self-serve paid tier yet | 50 projects at 25MB each, a "made with Birta" mark fixed in the corner with no switch to remove it, 10 readable form leads a month per project |
| Custom domain | Free, through the console and a CNAME record | None at all on the free tier; one domain on Solo at $12 a month, five on Pro at $39 |
| Versions and rollback | Not documented as a product feature | Every successful publish is a saved version; the last 10 stay visible, and any of them can go live again |
| Lead form | No native form product found; build one with Functions | The agent declares the form's fields directly; submissions show up in the project's Forms tab, with a dashboard and email digest |
| Reviewing before it goes live | Preview deployments per branch, shared as a URL; no commenting or annotation documented inside the preview | Every version has its own permanent address; whoever holds it marks remarks on the element itself with no account, and the agent reads them back as numbered threads |
| Backend | Cloud Functions, Edge Functions, KV/Blob storage | None. Birta only publishes static files |
| Single-page app with client-side routing | Supported, with functions and routing available | Not supported. Ordinary multi-page static sites are fine |
| Payments from your visitors | Buildable yourself with Functions | Not yet. A planned backend module, not a permanent no |
The domain row goes to EdgeOne Pages. Its custom domain connection is free right now, while Birta's requires a paid plan, and for a project where cost decides it that settles the row. What Birta's free tier carries in full is the agent side: drafts, versions, rollback and the whole review round, with no plan gate on any of it.
Read again on 7 September 2026, and the shape has not changed: the Free plan is still $0 a month, and EdgeOne still answers the question directly with "Yes, our Free plan is here to stay and will be available permanently!" There is still no self-serve paid tier. A Business plan exists by contacting sales, the page says more options for individuals and enterprises are coming soon, and until then "Before the paid version launches, your service will not be interrupted even if you exceed the free tier limits." So the free-tier comparison on this page holds for now, and it is the kind of thing worth checking yourself before a decision rests on it.
If a project's acceleration region includes the Chinese mainland, EdgeOne requires the domain to complete ICP registration, a government process, before it can go live. That doesn't apply everywhere, but it's worth knowing if it applies to you.
Sending a version out for review
EdgeOne Pages has the sharing half of this. Turn preview branches on in a project's Git settings and every push to a configured branch builds its own preview, which the docs describe plainly as URLs you share "with team members, designers, or product managers for quick feedback collection." That is a useful thing to have, and Birta has no branch-based equivalent: a Birta version comes from a publish rather than a push.
What EdgeOne's documentation does not describe is anywhere for the feedback to land. We read its preview-deployment material and its deployment docs on 7 September 2026 and found no commenting, annotation or review tool inside the preview itself. That is absence of evidence rather than proof, and EdgeOne's documentation set is large, so treat it as "not documented" rather than "does not exist". In practice it means the remarks come back to you in chat.
Birta puts them on the page instead.
Every version, draft or published, has its own permanent address, handed to the agent when it opens the draft and again when it publishes. You send that address and nothing else. Whoever holds it opens the page without signing in, because version links are open to the link holder by default, and the guest is issued a nickname that signs their remarks. No account, no invitation, no console.
They mark the page itself: click the heading, the price or the broken button, and the remark pins to that element on that version.
Your agent reads them back through the same connection it published with. Each thread comes with its number, the page and element it points at, whether it is still open, and every message with author and time. Thread numbers are permanent, so "number four is still open" names one specific remark next week. The agent makes the change in the same draft, publishes a new version, and the reviewer refreshes the tab they already had open.
One boundary: the agent reads and edits, nothing more. It cannot post a reply into a thread and cannot mark one resolved, and a write to the comments is refused, so closing a thread stays a person's job in the browser. Reading and fixing is the half that decides how fast a round closes, and both happen inside the connection that published the version.
Remarks also arrive by mail. Everyone with access to the project gets one digest roughly 15 minutes after the first remark lands, minus their own. No plan gates any of it, so it works the same on the free tier, and the versions and remarks guide is the walkthrough.
The distinction worth carrying away: a preview URL is a place to look, and a version address is a place to reply, with the reply landing somewhere the agent can read it. If the site only ever needs somewhere to look, EdgeOne's preview does that job well.
Where EdgeOne Pages wins
Win on breadth. Cloud Functions and Edge Functions mean real backend code can run without you configuring servers. Blob and KV storage give a data layer Birta simply doesn't have. AI agents with built-in models are part of the free tier, not an add-on.
Win on price for that breadth. A free tier that includes functions and storage, with a company statement that it stays free permanently, is a genuinely strong offer for a developer who needs more than a static page.
And win on the domain, as stated above. If cost is the deciding factor and a free custom domain matters more than a lead-form product, EdgeOne Pages has the edge here.
Where Birta fits better
Birta fits when the job really is a static commercial site, and what's needed is publishing it, keeping a real version history, and handling leads without writing backend code to do it.
Choose it when a bad update needs to be reversible without rebuilding from memory. Every successful publish becomes a version, the last 10 stay available, and any of them can go live again with the original files intact. EdgeOne Pages doesn't document an equivalent.
Choose it when a real lead form belongs on the site and you want it handled without wiring up a Function yourself. The agent declares the fields, and every submission lands in the project panel with an email digest close behind. EdgeOne Pages has the building blocks to do this through Functions, but not a declared form contract the way Birta does.
The tradeoff is real: no backend functions, no database, no AI-agent runtime, and no way to take a payment from your visitors yet, which is a planned module rather than a permanent no. What the narrower product spends its depth on is the part after the publish, and all of it sits inside one connection: the draft, the version, the rollback, the remarks.
Moving a static site over
This migration only makes sense if the EdgeOne project is genuinely static. If it uses Functions, KV, or Blob storage for anything the page depends on, that logic needs to be rebuilt elsewhere first, since Birta has no equivalent.
- Step 1Confirm the project is staticCheck whether the site depends on Cloud Functions, Edge Functions, or KV/Blob storage. If it does, that logic has to move somewhere else, not to Birta.
- Step 2Recover the static filesPull the HTML, CSS, JavaScript, and assets that make up the actual page.
- 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 answer to the first step is "yes, it depends on Functions," this isn't a Birta migration. It's a different kind of project.
The decision
EdgeOne Pages is the right call for a full-stack web app or an AI agent that needs backend functions, storage, and a free custom domain right now.
Birta is the better fit when the job is a static commercial site and you want it published with real version history and a working lead form, without operating backend infrastructure to get there.
Check your current agent path
Pick the tool you already use and verify the documented connection before moving any files or changing a domain.