A public site is a folder of static files (pages, styles, scripts, pictures and fonts) that the room built and you chose to put online. It has an address of its own, and anyone on the internet can open it without signing in. It suits landing pages, portfolios, documentation and small marketing sites.
It is different from the two things beside it. A published page is one page behind a link only people with the link find. A kept app is a running server on your Cloud Computer, for people you name, signed in. A public site has no server of ours behind it and no lock at all.
Publishing one
Where to find it. In any discussion with a workspace, ask the room: "publish this as a public site called my-product". The lead builds the site, then asks with its publish_site tool, and a card asks you first, showing the address, the folder and how many files go. Nothing is published until you say yes, in every permission mode.
What goes. The built folder (dist, build, out or public) with index.html at its top. Hidden files, node_modules, files that hold secrets by convention and kinds of file a site does not carry are left out, and the room tells you which.
Keys are held back. Every text file is read for anything that looks like a key or a token. If one is found, nothing is published and the room is told which file. Only when you say that value is meant to be public does the room publish it anyway.
The address. The name you choose is the first part: my-product becomes my-product. followed by the sites domain. A name is 3 to 40 lowercase letters, digits and single dashes. Names that would read as ours are kept back.
A new version. Ask the room to publish the same name again. The address stays; the new files replace the old ones together. A change can take up to five minutes to show everywhere.
The Prompt Library has two starting points under Build and Release: A public site, online for anyone and Take payments on a public site, with your own provider.
Where your sites are
On the Artifacts page, under Sites in its filter. Each site's card shows, in view:
| On the card | What it is |
|---|---|
| Address | Opens the site in a new tab |
| State | Public, Paused, Paused until next month or Taken down |
| Version, files and size | What is being served now |
| Visits this month | Against the month's allowance |
| Pause / Bring Back | Pause stops the site answering and keeps its files and name |
| Delete… | Removes the files and frees the name for anyone |
| Discussion | The discussion that built it, where the next version is published from |
Limits
| Limit | Amount |
|---|---|
| Sites per account | 5 |
| Files in a site | 200 |
| One file | 2 MB |
| A whole site | 10 MB |
| Visits a month, each site | 50,000 that reach our servers |
Most visits are answered from a copy kept near the visitor and are not counted. A site that passes its month shows a short notice until the next month begins; nothing is charged for it.
Who can publish
Public sites come with Pro and Team. In a team, an owner or admin can switch them off for everyone: web, Governance → Tools & Connections → Tool families → Publishing set to off, or Governance → Sharing & Retention → Members may publish at a public link switched off.
Payments, forms and sign-ins
A site here is files. It can link to, or load, a service you hold an account with: a payment link or hosted checkout from your own Stripe or Paddle account, a form service, an analytics script. The money and the customers are yours and never pass through us.
Never put a secret key in a site: every file is public. A payment provider's publishable key and a payment link are made to be public; a secret key, a webhook secret and a restricted key are not. Anything that must be checked on a server, such as unlocking a download after payment, needs a server of your own.
Reports, and sites taken down
Every page of a site carries a small Report link we add, which the site cannot remove. A report reaches us with the site's address and what the person wrote. A site used for phishing, malware, spam or anything our terms forbid is taken down: it stops answering at once, cannot be published again, and its card in Artifacts tells its owner why.
What is recorded
Publishing, pausing, bringing back and deleting are in the audit record as public_site.published, public_site.changed and public_site.deleted. Deleting your account deletes your sites and their files.