How to export your website — what you can take, and what we do not ship

A website should be an asset you own, not a subscription hostage.

A bundled platform can leave you with a site that only runs inside it. The export terms are the part to read, not the part a pricing page advertises — and on the platforms we profiled, just under half of what we could read says nothing at all about export, so the question has to be asked rather than assumed. If a platform says nothing about what happens to your files when you stop paying, the honest expectation is that your site is a rendering on their infrastructure, and a copy of it exists only if you took one.

So here is the honest version for this platform. There is no export button, and there is no CLI. No zeso export command was ever published, because no such command exists. What there is instead is a document, and an API that reads it — and against the price pages we audited, that is a stronger position than a download button rather than a weaker one. The purest "toll on the exit" in that corpus is carrd putting the HTML download behind its $49 plan, and tilda fencing a code export behind six licence clauses. We do not charge for the exit because there is no export to charge for.

What you actually own

Your domain name. A domain registration is a separate legal relationship with an accredited registrar. We are not the registrar, and we do not hold it hostage — point its DNS records anywhere: another host, another builder, your own server.

Your content, as JSON. Every collection on your site is readable over a public API, without a key and without a login. Published rows are public. Drafts are not, and never were.

The site's own document. The site is stored as an open JSON SiteSpec — the builder writes it, the renderer reads it, and the studio's Code panel is a copyable JSON view of it.

A build you made elsewhere. If you already have a static site, you can host it here: drop a zip and the edge serves it verbatim. That is the same plane that makes a static bundle a first-class citizen here instead of an afterthought.

Reading your content out

Every site answers this, and the answer describes itself — the endpoints, the auth model, and where the manifest and the OpenAPI surface live:

bash
$ curl -s https://your-site.zeso.cc/api
{"ok":true,"api":"zeso-tenant","version":1,"site":"your-site","auth":{"public":"GET collections and live rows require no key",...}}

The collections endpoint gives you the shape of the site — names, field definitions, and how many live rows each one holds:

bash
$ curl -s https://your-site.zeso.cc/api/collections
{"ok":true,"collections":[{"name":"services","fields":[...],"liveCount":12,"isExternal":false}]}

And the rows endpoint gives you the copy itself:

bash
$ curl -s https://your-site.zeso.cc/api/collections/services/rows
{"ok":true,"collection":"services","rows":[...],"visibility":"live"}

Your site's own manifest is the same content in markdown — the page directory, the FAQs, the pricing table and the contact details:

bash
$ curl -s https://your-site.zeso.cc/api/llms.txt
# Your Site Name

> The tagline your site carries.

## Pages
- [Home](https://your-site.zeso.cc/): The description the home page carries.

What we do not ship

• No CLI. There is no zeso command to install, and there never was.
• No one-click static bundle. You cannot download a pre-rendered HTML/CSS/JS archive of your site, because we do not build one.
• No export fee and no export tier. There is nothing to unlock — the reads that power the site are the reads you do.

The checklist before you cancel

1. Pull the rows. GET /api/collections, then GET /api/collections/{name}/rows for each collection. That is your copy, in JSON, with the field definitions that go with it.
2. Save the manifest. GET /api/llms.txt is your page directory, your FAQs and your pricing in markdown.
3. Save the document. The studio's Code panel is a copyable JSON view of your site's own document.
4. Copy the assets. Images and uploaded files are served from the edge rather than from the rows, so pull them down while the site is still up.
5. Move the DNS. Your domain was never ours; point it wherever you are going.

The part that is a decision, not a feature

Leaving is a build, not a download: another host wants the content in the shape it expects, and the design work has to be reproduced. What this platform removes is the proprietary part of that work — the format is open JSON, the content is a documented API, and no fee stands between you and the exit. What happens to my website if I cancel sets out the three models builders use and which one this is; the comparison pages record, platform by platform, what each one publishes about export — and where its own pages did not say, they say so.