Documentation / Concepts

Your website

Build and publish a real website by chatting with your AI assistant — it runs on an isolated server that is yours, served on your own domain.

How it works

Tell Claude or ChatGPT what you want and it builds the site directly on your server: it writes the files, runs the build and previews the result. There is no separate SSH or FTP app to set up — site_run_command is the terminal and site_write_file / site_read_file are the file transfer. Pages are served statically (no Node process at runtime), so any build must emit static files.

It doesn't spend credits

The website tools are free: creating a site, writing files, running builds and previewing never draw from your monthly credit pool. Your plan credits are for ad and data tools; building your site costs nothing.

Getting a server (from the panel)

Isolated & safe

Every server runs in its own hardened (gVisor) container — your files, your commands, isolated from every other tenant. You can disconnect or delete it at any time from the panel.

Every change is undoable

Before any write, edit, download or shell command touches the site, a snapshot of it is taken automatically. So when a page comes back wrong, you list the snapshots, find the one from before the change and restore it, either the whole site or a single file. Restoring itself takes a snapshot first, which means an unwanted restore is also undoable.

Common questions

Can I upload files over FTP or SSH instead?

No, and there is nothing to set up in exchange. The website tools are the server access: the shell tool is the terminal, and the read and write tools are the file transfer. No separate client exists and none is supported.

My assistant says it created the files, but the site has not changed. Why?

The files were almost certainly written in the assistant's own scratch environment rather than on your server. Nothing syncs between the two: content reaches the live site only when a website tool writes it there. Asking the assistant to list the files on the server settles it in one call.

Can I run WordPress or a Node app on it?

Pages are served statically, with no runtime process, so a framework is fine as long as the build emits static files. If what you want is a self-hosted WordPress site, that is a different product: our WordPress connector manages an existing WordPress installation wherever it already lives.

What happens when the free trial ends?

A trial site removes itself after three days, and there is one per account. If you want to keep what you built, move to a paid server before then; the work is not migrated automatically once the trial has gone.

→ Website tool reference