Work together on what your agents create.

Over the same connection it publishes with. Ask it to read the remarks on a version, and it gets every thread with its number, its place on the page and its status. Then it changes the draft and publishes the next version. It does not act on its own: you ask, it applies.

No. A site is one of the things people bring. A deck, a report, a proposal, a guide or a small interactive tool get the same review link, versions and address. A site can hold several pages, with working links between them. Not a web app with sign-ups and logged-in areas. The request form works and what people send is in the panel; taking payment on the page itself is not there yet, so until then put a payment link on it.

Free includes publishing, your own domain, forms and version history. Team adds shared project context, higher limits and the option to remove our branding. Enterprise terms are agreed with your team. Prices and limits are in the plans section above.

No. Publishing, the address, the secure connection, versions, the request form and the stats are ours. How good the site itself is depends on your agent and on how you described the job.

No. Open it in View HTML to see the page, or get a link to it in Publish HTML. Neither needs an account.

Claude and ChatGPT (in the browser, in their desktop apps, in Cowork and in Codex), plus Claude Code and Cursor, all have step-by-step guides. Not on the list? Pick "another tool" on the first screen: you get a request to paste into it, which it reads and then either connects itself or tells you what to open. Some chat plans do not allow connections at all.

You tell your agent in words what you want to collect: a name, an email, a message, a consent. It declares that form and lays it out in the design of your site, so you are not handed someone else's block. Requests arrive in the project panel, and your agent can read them, so a summary is one question away.

Anyone you send the review link to: each version has one of its own, and commenting needs no account. Everyone added to the project comments too, under the email they joined with. The public address stays as it is, and the review link can be closed when the round is done. Threads keep the author, the time and a permanent number, and your agent reads them all.

Add them to the project by email: the requests appear in their panel, with a note to their inbox for each new one. Everyone on a project holds the same full rights.

Each publish is saved with its date and the note your agent left for it. The panel lists your last 10 publishes, the live one included: restore any of them in a click, or download its files.

Ask your agent for the edits and publish again. The address stays the same, so the link you already sent opens the new version, and the earlier ones are still there.

The site is an ordinary set of files and you can download any version of it from the panel at any time, then open or host it elsewhere. Your own domain stays yours and moves with you.

In a builder you assemble the site yourself in its interface and see the result as you go. Here your agent builds it from what you described, and we publish it, keep the versions and give it an address. Which suits you better depends on where you would rather work.

Then describe the job in the message. If your agent has memory switched on, or the right file open, it will use that context too, and nothing has to be moved over to us. What your agent remembers is between you and it.