Features.

Three ideas do most of the work here: the site is printed, not rendered; the data model is the one you already know from WordPress; and an agent can drive the whole thing by prompt. Everything below follows from those.

01Printed, not rendered

Publishing writes every entry out as static HTML and puts it on Cloudflare's edge. There is no server rendering a page when a visitor arrives, and no database query in the request path — which is why the hosting cost of a busy month looks like the hosting cost of a quiet one.

It also means the public site has no JavaScript dependency: the words are in the HTML. That is a correctness property before it is a performance one, and it is the reason the next section works at all.

02Built to be read by machines

AI crawlers generally do not execute JavaScript. A site that assembles itself in the browser is, to them, a blank page. Every publish therefore emits:

• JSON-LD structured data per entry.
• Canonical URLs plus Open Graph and Twitter meta, generated rather than hand-kept.
• A sitemap and an RSS feed.
• A robots.txt that explicitly allows GPTBot, ClaudeBot, PerplexityBot and friends — with one setting to reverse that and turn the whole site noindex instead.
• Image SEO carried through from the media library.

03An agent that can drive it

Writing, editing and publishing can be done by prompt as well as by hand. The agent works against the same API the admin uses, so anything it does is something you could have done yourself — and is visible afterwards in the same revision history.

Agent usage is metered in orchestration credits, and every plan including Free gets a monthly allowance; see pricing for the numbers. On paid plans the agent keeps memory of your site between sessions instead of being re-briefed every time.

04WordPress parity, on purpose

Posts and pages, categories and tags, a media library, menus, custom fields, user roles, permalink structures, revisions, comments. The concepts map one-to-one, which is what makes importing a real WordPress site a migration rather than a rewrite — and what makes the admin navigable on day one if you have run one before.

05Bring an existing site

The importer reads a WordPress database and uploads directory directly — no REST API, no WXR export, no plugin on the source site. Old URLs keep working through generated redirects. See WordPress migration.

06It runs in your account

Each instance is self-contained and lives in your own Cloudflare account with its own database, storage and Workers. Attach your domain, keep your DNS, revoke our access whenever you like — the site keeps serving, because the files are already on the edge and they are yours.

Want the mechanics rather than the summary? Read the docs.