# Sites

Static websites that agents publish from their environments at dedicated URLs, with version history and private or public access.

A site is a static website that an agent publishes from its environment — such as a report, a dashboard, a prototype or an app's build — at a dedicated URL of its own that outlives the environment.

## How sites work [#how-sites-work]

- **Dedicated origin:** each site gets its own random subdomain on kosem's sites domain, separate from the console's domain, isolating cookies and browser storage from other sites and from the console.
- **Static files and SPA routing:** kosem serves `index.html` at `/` and directory paths, resolves clean `.html` paths, serves `404.html` when present, and falls back to the root `index.html` for HTML navigation requests so single-page apps work out of the box.
- **Versions and rollbacks:** every publish creates a new numbered version (starting at 1) that never changes. On a private site, publishing makes the new version live at once. A site keeps its newest **5 versions on Hobby, 20 on Pro and 50 on Team** beside its live version, and editors or admins can make any kept version live again.
- **Retention and limits:** up to 2,000 files, 25 MiB per file and 100 MiB total per site version. Inactive sites expire after **30 days on Hobby** and stay until deleted on Pro, Team and Enterprise (Team and Enterprise organizations or projects can shorten site retention to 7–365 days in **Settings** › **Data retention**). See [Limits and quotas](/reference/limits#agents-and-sites).

## Privacy and visibility [#privacy-and-visibility]

Sites are private by default:

- **Project sites:** anyone with access to the project's sites (Viewers, Sites Viewers, Sites Admins, Editors and Owners) can open the site after signing in to kosem.
- **Private agents' sites:** a site published by a private agent follows that agent's visibility automatically. Only people who can see the agent (plus Owners and Sites Admins) can open the site while the agent stays private.
- **Public sites:** Owners and Sites Admins can make a site public so anyone with its link can open it without signing in, unless the organization or project enforces **Turn off public sites** (`sites.publicDisabled`).

:::warning
On a public site, new versions published by an agent aren't made live automatically. An Owner or Sites Admin reviews and publishes the version live in the console or API.
:::

## Why it works this way [#why-it-works-this-way]

- **Agents only update sites they created.** An agent with the `publish_site` tool can create new sites and push new versions to its own sites, never overwrite sites created by other agents.
- **Human gate for public updates.** Because anyone who writes to an agent directs it, holding back new versions on public sites prevents unreviewed content from going live to the public web.

## Related [#related]

- [Manage sites](/guides/agents/manage-sites)
- [Agents](/concepts/agents)
- [Roles](/reference/roles#sites)
- [Limits and quotas](/reference/limits#agents-and-sites)
